Dev Interviews
2 points| haho4 | 4 years ago
I'm a developer with 12+ years of experience, working across multiple languages and a variety of technologies throughout my career.
I've not had to formally interview in a very long time, so now it's shell shock for me.
It's literally insane what these interviews are.
I feel like I'm taking a test, but I have no idea what the subject is.
One interviewer asked me leetcode questions. But he didn't care about the thought process, he just wanted me to code the optimal solution as quickly as possible. When I got stuck for a minute, and I was trying to think it through, he just told me to code it. I don't understand why I would want to work with someone like this?
Another interview, I went in thinking it would be leetcode questions, but the interviewer proceeded to ask me questions specifically pertaining to the language. He started asking me questions on syntax, how do I filter or group data sets using the language, how would I create threads, etc. Of course, he also wanted this all on Notepad. I was taken aback, as all of my focus was on studying algorithms.
On and on. There is no set format, I'm not told beforehand what I'd be asked about.
I've asked the recruiters what I'd be asked beforehand, and obviously not so helpful on that end.
How does one handle the variety of questions that you could possibly be expected to answer? I'm at the point where I just want to go do something else with my life.
twright|4 years ago
- In the phone screen try to clarify that the tech-screen questions are in the domain of the role you're interviewing for. Good recruiters will be open with that information and should be up to date on their hiring procedures. Pressure them more if they remain vague, consider it a red flag if they don't budge.
- Get comfy with writing {B,D}FS algorithms, --not just that you know them-- write them out. Same with writing a tree/graph data structure. For some reason cycle-detection is a common question, be familiar with tortoise and hare algorithm as well as coding it up.
- Search on glassdoor to see if anyone drops any interview questions
- Search github to see if anyone uploaded a take-home if there is one
The hardest part about tech interviews is the rejection and moving on mentally.
Where I am now we have a pretty non-technical process but the caveat that compensation is a little lower (remote, US only), you can figure out how to DM me through my profile if you need something sooner than later.