I enjoyed the interview process up until the technical interview. I was honest with my skillset, and was told the lack of knowledge about particular subjects was not a problem. It turned out to be a problem however.
Call with recruiting, they were late and had their camera off the whole time. Completely uninspiring with (close) to zero knowledge of the core business. Sad really, they didn’t seem excited or motivated and generally very spacey. They missed several self-imposed deadlines and I eventually gave up.
Interview questions [1]
Question 1
Tell me about your background, sorry I didn’t have time to review your resume
I applied online. The process took 2 weeks. I interviewed at Lambda in Apr 2025
Interview
Direct and to the point, Lambda ask technical questions which will synthesize your understand of the domain which you're interviewing for. I interviewed for a backend SW position and was given a fair, but thorough test in Linux and object oriented programming. No Leetcode.
The interview process consisted of:
* Recruited screener
* Hiring Manager interview - resume review, and off hand technical jabs.
* Linux technical interview -- this one was weird. I SSH'd into an EC2 instance and just answered random questions that the interviewer thought of, thorough and difficult.
*Behavioral & OOP design interview
* solve an OOP problem using python or golang, make sure to display 100% competency in the interview, I was declined since I was nervous and mixed up python & go syntax. This is a relatively easy problem, so you need to do it right.
* Behavioral interview -- the recruiter gives you a number scenarios to consider before this interview, and then discuss this in the actual interview, things like "A time you had a technical failure.