#Novice or Intermediate Categorization
1 messages ยท Page 1 of 1 (latest)
<@&987246964494204979> please have a look, thanks.
Here is an AI assisted attempt to answer your question ๐ค. Maybe it helps! In any case, a human is on the way ๐. To continue talking to the AI, you can use </chatgpt:1108714622413963314>.
If you have less than 1 week of experience with Java and less than 4 years of experience with programming in general, it would be best to choose the novice role on the Java Q&A discord server. This will help you find resources and support tailored to your current level of experience. As a novice, you can ask questions, seek guidance, and learn from more experienced members in a beginner-friendly environment. Once you gain more experience and confidence with Java, you can always switch to the intermediate role. Remember that it's okay to start as a novice and gradually work your way up as you learn and grow in your programming journey.
For a Java role? Novice.
If it's a generic development role you can go for novice.
So like with many things: it depends.
Are you 'comfortable' with Java? Or are you still in the 'learning the language' stage?
A good gauge would be the curriculum of the Helsinki MOOC. If you understand all of the topic headings in the first 12 sections you've made it from beginner to the foothills of junior.
If you've moved on and are now comfortable with some problem solving outside the tutorials and learnt at least the basics of some of the common tools/frameworks (a little logging, unit testing, some fundamentals of spring) you could be approaching the point where some consider you* intermediate*.
However, the junior and intermediate definitions vary a lot by region and context...
would an ap computer science course cover most of the data structures and concepts for "intermediate"
but still keep the software development process in "novice"
No.
it would probably take a week for me to transfer my js dev process to java just by learning the java equivalent of most things i use
It's also about having practical experience.
That's more of a 'maybe ready for a junior role' point.
That intermediate definition tends to also mean that there's a dramatic fall-off in the need for supervision.
And also, that your self-awareness is good enough to reach for assistance appropriately - that is, you're more self-aware of where you sit on the so-called Dunning-Kruger curve (though that's not strictly a correct interpretation of the concept).
Imo reaching an intermediate role takes at least 1-2 years of actively working with a language, regardless of how many courses or classes you take, you need to at least have built a few things on your own to be able to "increase" your experience level.
the typical definition and how it often goes is:
- junior: ~3 years of experience with private projects and studying, no work experience yet
- intermediate: 2-3 years actual work experience, so about 5-6 years programming in total
- senior: 5-7 years actual work experience, so about 8-10 years programming in total
things can be a bit more tricky to classify when u started programming with 12 and already did some freelancing with 16 while studying and then perhaps had a long internships during studies where u also coded a lot etc
then u might be intermediate already when u apply for ur first "real job". but those are rare cases overall
Also don't focus only on technology skills, even if you know a language back to front and are unable to work without direction and can't handle feedback I'll still consider you a junior profile.
Navigating senior, tech lead, staff and principal positions at tech companies and startups.
that seems like a sensible definition for experience
yeah i also find criticism of the upmost importance when trying to improve skills
and working with people in a team
Novice or Intermediate Categorization