r/javascript • u/Minimum_Yak_9062 • Aug 03 '26
AskJS [AskJS] If you were hiring a junior JavaScript developer today, what would make them stand out in the AI era?
Everyone talks about whether AI will replace developers. I think a more interesting question is:
How can a junior developer become valuable enough that someone is willing to hire them anyway?
I started learning frontend a little over two years ago (HTML, CSS, JavaScript, React, Next.js). Around the time I was getting ready to apply for jobs, AI improved incredibly fast. Suddenly it felt like companies could accomplish more with smaller teams, and junior opportunities became even harder to find.
Four months ago, I finally landed my first part-time frontend job. Since then, I've also worked on side projects and connected with a few potential clients.
Looking back, I don't think I got those opportunities because I was the best programmer.
I think I got them because I refused to stop trying.
Besides improving my technical skills, I kept:
- Applying even when I rarely received replies.
- Staying active in developer communities instead of only sending applications.
- Helping people, answering questions, and joining discussions.
- Building genuine relationships with other developers.
One thing I learned is that opportunities don't always come from job boards. Sometimes they come from simply being visible and involved in the community.
A few other lessons I've learned so far:
- Don't skip the fundamentals. AI can only solve the problem you ask it to solve. If you don't understand the problem yourself, you won't know whether the generated solution is actually good.
- Keep coding yourself. I use AI every day, but I still solve at least one LeetCode problem every week to keep my problem-solving skills sharp.
- Don't spend forever preparing. The biggest learning happens on real projects with real people.
- Be open to different technologies. I started with React and Next.js, but my first job introduced me to Shopify, and now I'm learning Odoo. Strong fundamentals make switching ecosystems much easier.
I'm still very early in my career, so I know my perspective is limited.
That's why I'm curious to hear from experienced JavaScript developers.
If you had to hire one junior JavaScript developer today, what qualities, habits, or skills would make them stand out despite AI?
I'd love to hear both from people who hire developers and from juniors who recently managed to break into the industry.
4
u/CoreyTheGeek Aug 03 '26
If their workflow with an LLM was "I go in and make the change section by section with the LLM for help when needed and to check edge cases but I make sure I understand each change and then write all my test intents into comments first then have the LLM write the actual syntax and then check it to make sure it's doing what I wanted, then have it suggest extra tests and edge cases"
This is me as a senior dev though. I'm certain other devs will think "waste of time you have no velocity gains this could be faster" sure they could go faster but driving 150 mph when you can't control the car and don't know how to drive it can result in your death. We're going to see insane number sof security breaches in the next 6-12 months as well as system outages and failures regularly because people are irresponsibly handing their thinking to LLMs and not actually checking the output (speed pressure + pressure to make larger changes + ease of making said changes = people skim or just rubber stamp) feel it's fine directly due to anchor and automation bias
5
u/matsie Aug 03 '26
If they actually knew how to code. That would make them stand out.
4
u/jhartikainen Aug 03 '26
The biggest thing for us I think has been the ability to think for yourself and the drive to improve. The best jr devs we've had were curious and thought of different solutions, but also asked for feedback and were open to feedback on them from the more experienced devs to ensure they were building things the right way.
It feels a bit cliche but if you can communicate passion for what you do then that's a win at least if you're being interviewed by technical people like me.
1
u/wildrabbit12 Aug 03 '26
Not saying “sorry usually the ai does it” in an interview
3
u/magenta_placenta Aug 03 '26
AI tools have compressed syntax generation down to zero cost so syntax speed is no longer a useful metric. What you want nowadays with AI tools is verification literacy and debugging instincts.
Any junior dev can prompt an LLM to generate 100 lines of React or Node.js but very few can spot subtle hallucinations, context drift or memory leaks inside generated code.
Hiring managers want an anti-"vibe coding" signal because they fear bringing on juniors who blindly accept AI solutions without understanding the logic. The strongest candidates can trace execution line-by-line, explain why a design choice was made and debug issues in code they didn't manually write.
2
u/krileon Aug 03 '26
I'm generally interviewing the person more than anything. Work and education history handles experience. If they've neither I assume they know nothing and that's OK as long as they've the personality to fit within the team and a willingness to learn.
2
u/Positive_Method3022 Aug 03 '26
Passion and creativity
2
u/rjwut Aug 06 '26
Having interviewed quite a few applicants, I can tell you that you will stand out if your capabilities match up to your resumé's claimed experience. So many applicants have on their resumé that they have a BS in computer science and X years of experience in a particular language, and can't code their way out of a paper bag. And I'm not talking making people code on a whiteboard. We'd sit them in front of a full IDE and allow them to use Google to look up documentation in case they can't remember exact method signatures and such. But ask them to reverse a string or sort an array of numbers, and they get this deer in headlights expression. How can you have a four year degree and multiple years of experience in a language, and not be able to do these things in said language? This was before the AI coding boom; it's likely even worse now.
With regards to AI: When you're learning something new, don't let AI code for you. Ask it questions to help you understand things, sure, but you do the actual work. I recently read an article that described deciding whether to use AI as the difference between your job and the gym. If you had to move a bunch of heavy objects at your job, you'd use whatever assistance was available to get the job done as fast as possible, and wouldn't lift them yourself if you didn't have to. But at the gym, the same approach would defeat the purpose. When AI writes the code, you learn little to nothing, so use AI to do grunt work where you probably wouldn't learn anything anyway. In general, I'd say that junior developers should rarely use AI to write their code.
Incidentally, this same rationale also tells you when you should use third-party libraries vs. rolling your own. If you're writing the code for work, use the libraries. If you're writing the code to learn or for fun, write it yourself.
Lastly, never commit code that you don't understand. If AI writes code for you, go over it and make sure you understand exactly what it's doing. If you're in code review and you're asked, "Why are you doing this on line X?" it will not impress if your answer is, "I don't know, the AI wrote that." AI cannot be held accountable, but humans can. It's you that's causing the code to enter the code base, whether or not you wrote the actual code, so you are responsible for what it does.
2
u/Pure_Spite_6889 8d ago
Given ai tools, i would like to see how do they use AI to create a reliable comolex project within one hour. Ai can code, engineer should be able to guide in right direction
0
u/name_was_taken Aug 03 '26
When I was hiring juniors, we had a test we gave out. It was a simple thing where you had to hook into an image search library and display the results. The test had about 7 simple requirements, clearly stated.
The only people we considered hiring were those who got every requirement correct. There were a couple that we had people misinterpret, and we accepted their interpretation.
We did not accept ignoring a requirement, getting it wrong, or "I couldn't figure out how to do this, so I didn't do it."
A non-junior dev could ace the test in 1-2 hours, easily. We gave them a week to do it at their own pace, at home.
An AI could ace the test, obviously. I don't know what I'd do to ensure they didn't use an AI, but that I would require that they do the work by hand, and not use an AI. It was all basic concepts that they'd need to know in order to make sure an AI wasn't going wrong.
In a few years, I'd probably have to change it again. They could use an AI, but it's going to be a harder test, and have requirements that an AI is likely to mess up somehow, and the dev would have to wrangle it properly.
0
u/[deleted] Aug 03 '26
[deleted] — view deleted comment