Over my 10 year career I have worked at a ton of different companies. I have worked at large companies, small companies, I have also worked for myself as a freelance,
or consultant software engineer. I have been in a lot of interviews, and I have given
probably a hundred interviews. I can tell you from my experience that most interviews have the same general pattern.
And if you can study certain things, you’ll ace your next interview.
Here is the general pattern that I’ve seen for most interviews:
There is always at least one “tricky” question: This tests your knowledge of the language of the job you’re applying for. It’s meant to weed out the people who really don’t know what they’re doing.
- Binding this
- Type coercion
- Function Hoisting
- There is usually one algorithm type question: Ah, yes, the bane of all software engineers, algorithm questions. These aren’t necessary about specific algorithms like Dijkstra, or Binary Tree Searching, or anything like that. These are usually lower-level questions that test your knowledge in basic data structures and loops, recursion, etc.. And example: “Tell me if a sentence is a palindrome”
- You’ll have to write a small feature of an app: If the company hiring you is worth their salt, they’ll ask you a relevant question like: Can you code a small feature of an application? This is meant to test your real-world abilities. You’ll want to code lots and lots of stuff in order to get this right. Its super simple. I lost a job because I didn’t practice this one skill enough.
Here is some more information: