Hi! I'm an aspiring computer scientist with interests in quantum computing and distributed systems. In this blog, I write about the useful things I've learned during my programming journey.
Basic mastery of your tech stack (If the job is for embedded systems, maybe don't walk in and say you only know HTML lol)
Basic GIT
Basic algorithms (if you can do fizzbuzz you're gold)
Enthusiasm
A willingness to learn.
It might take 3 months of training to get someone from a hobbyist to professional junior level but they'll also probably spend much more time with the company to learn. If I had a company I would want someone who has attachment to the company, not someone who shows up for a check.
Ability to take a problem as a client would describe it and then translate that to problems that can be coded
some degree of comfort with any programming language (not html or css)
ability to communicate especially code design ideas, problems you're stuck on, and why you did what you did.
A lot boils down to not necessarily having the right answer but communicating how you get to SOME answer and being willing to have constructive conversations about your design and code.
Ability to take a problem as a client would describe it and then translate that to problems that can be coded
This! Also, the inverse of this which is the ability to explain technical concepts to non-technical clients, like informing stakeholders why feature x would take x amount of time.
If I asked a lateral thinking question (how many ping pong balls can fit on a school bus), complaining that it's a waste of time or pointless question.
refusal to listen to help (though I acknowledge this is easily misconstrued during interviews with not wanting to look ignorant)
I think there was one or 2 other examples I had in mind when I posted but they aren't coming to me. I've interviewed a few people who thought their school, internship, or 1 other brief job made them way better than they were. They ended up being close minded, hard to work with in a team, and poor at communicating their ideas.
Zero. They can read, and any good organization should have a workflow document somewhere. Heaven knows, there are only about a hundred possible "standard" workflows possible with Git.
Latest comments (50)
I need a job as a front end developer. There are many founders here, you can hire me Emergency
I went through the comments and learned a lot, these tips will help when I'm hunting for a junior role as I'm currently interning. Thank you.
Wonderful lists so far, awesome comments everywhere...I just came to read and I'm pleased i did...Thanks all!
I recommend this article towardsdatascience.com/soft-skills... about soft skills for developer
Thanks for that! I'm working on marketing myself as a junior dev, and those are the sort of things I had forgotten to emphasise.
Basic mastery of your tech stack (If the job is for embedded systems, maybe don't walk in and say you only know HTML lol)
Basic GIT
Basic algorithms (if you can do fizzbuzz you're gold)
Enthusiasm
A willingness to learn.
It might take 3 months of training to get someone from a hobbyist to professional junior level but they'll also probably spend much more time with the company to learn. If I had a company I would want someone who has attachment to the company, not someone who shows up for a check.
If you're not willing to invest in people I don't see how you can ever expect them to invest in your vision.
A lot boils down to not necessarily having the right answer but communicating how you get to SOME answer and being willing to have constructive conversations about your design and code.
This! Also, the inverse of this which is the ability to explain technical concepts to non-technical clients, like informing stakeholders why feature x would take x amount of time.
Fair call out, I typically see this as senior or above expectation but that could depend on the team and the company.
In what ways can a Junior show Ego?
as a junior developer, it pisses me off to see all "junior developer" or "intership" job postings that require 3+ years of experience
I'm not sure if there is a standard but from searching I think the maximum is 1 year?
But then I think different companies always have an interpretation for what experience really is...
Zero. They can read, and any good organization should have a workflow document somewhere. Heaven knows, there are only about a hundred possible "standard" workflows possible with Git.
Is being comfortable with the general GitHub workflow a good start and then adjusting to meet organization workflow?
guides.github.com/introduction/flow/
Honestly? Being comfortable with any VCS workflow is a good start.
As much you learn, us is good for you, there is basic commands you should learn and master
Best list I've seen yet!