If you are a Medium Member, please read there https://levelup.gitconnected.com/frontend-interview-preparation-for-2025-1-manager-round-89821ca55b4f
It’s not just about how you code!
Interviewing is a skill in- and by itself, which thus must be honed and perfected for a high success rate. I can already hear the fingers typing comments about how
they’ve never prepared for interviews but got hired for SpaceX and NASA at the same time.
As with most skills, some people have high affinity and some aren’t that lucky, spread on a curve of normal distribution.
The most efficient way to improve this skill (aside from reading my posts) is the combination of practice and learning.
you can master hammering nails with the handle of the hammer, but little learning helps tremendously
you can watch people doing a snowboard backflip, but hardly can reproduce it at first try
So what can you prepare for?
Common questions of the manager and recruiter rounds! Without claiming completeness:
Especially for junior full stack engineers: “what are you aspirations?” meaning, what do you want to be more? Frontend or backend engineer?
what methodologies have you been working with most recently? It's probably the easiest, they’re just curious if you used similar to theirs, as it makes onboarding faster.
probing questions about teamwork. Watch out for these, as few companies want to hire bad team players. No need to lie, obviously, but. don’t focus too much on other people’s mistakes. Remember, the interviewers know only as much context about situations as you give them, and short versions of professional disputes can portray an unappealing picture if not painted with care. And they might ask specifically to describe how you solve disputes.
riddles/logic exercises like the chicken the corn and the fox crossing the river are not that common, but again, not that uncommon either. Google some examples, most interviewers won’t be creative enough to come up with a unique one.
There are questions like how many manholes are there in New York.
Don’t get flustered by such bull💩. Depending on your situation you might try to play along or just quit the interview. There are levels of feedback (telling them to their face, leaving a GlassDoor review, filling out the recruitment feedback survey etc.) utilize them well when facing such predicaments.
Soft skills
There are common questions and then there’s soft skill. Part of it is the ability to describe work situations in short, but including all necessary info for the full understanding.
I will write an article on this topic as it’s a bit bigger than what fits in this general description if there is demand. Let me know in the comments.
Maybe the most basic thing many people get surprised by on the first rounds and greatly affects your next few years if hired:
Have a clear salary range in mind.
When you’ve prepared sufficiently for these rounds (btw about 2 hours of Googling and some interviews for practice) then your foot is in the door, but then comes the crème de la crème of the interviews: the technical round!
There you have to prove they are looking for you, and you have to find out you are looking for a place like them in terms of tech stack, development practices, used tools, architecture (like they might work on a monolith, they won’t advertise it necessarily) and so on. All that in a very short interview.
Follow for more!
Comments