Later Senior Software Developer interview questions

A recruiter reached out to me via LinkedIn. We scheduled a call to go over experience, salary requirements. Next step was to speak with someone on the engineering team. There was not a lot of information provided on what to expect. I found the interview to be more contentious in a way that felt like the interviewer was not considering me in good faith. I wouldn’t call it a resume/technical deep dive because I didn’t get to introduce myself and explain my goals on a high level without being called out for being generic. As someone who hadn’t heard about the company until I was approached that was a big red flag in regards to culture. The rest of the interview continued in that vein as I didn’t get to go in depth about my experience without the interviewer interrupting with questions about basic processes. It caught me off guard and I felt I didn’t get a chance to give an accurate representation of my career or my goals.

- Initial call with an in-house recruiter - Take home assignment - 2 follow up technical interviews The recruiter was very friendly and the take home assignment was an appropriate length. However, some of the people that conducted the interviews didn't understand the technical topics they were interviewing about. It's expected to challenge and prod at answers given by a candidate to gauge their level of knowledge, but when the people conducting the interview don't understand the topic then they should move onto one they do know. When other senior developers and future coworkers don't understand the subjects they are hiring for it becomes a bit of a red flag.