Software Engineer applicants have rated the interview process at Ladders with 3.1 out of 5 (where 5 is the highest level of difficulty) and assessed their interview experience as 64% positive. To compare, the company-average is 58.8% positive. This is according to Glassdoor user ratings.
Candidates applying for Software Engineer roles take an average of 9 days to get hired, when considering 12 user submitted interviews for this role. To compare, the hiring process at Ladders overall takes an average of 14 days.
Common stages of the interview process at Ladders as a Software Engineer according to 12 Glassdoor interviews include:
One on one interview: 28%
Phone interview: 22%
Skills test: 16%
Presentation: 9%
Group panel interview: 9%
Background check: 9%
IQ intelligence test: 3%
Drug test: 3%
Here are the most commonly searched roles for interview reports -
I applied online. The process took 2 weeks. I interviewed at Ladders (New York, NY) in Apr 2017
Interview
Several call interviews, followed by a long day of interviews onsite.
The onsite was long and stressful given the amount of context switching and questions. Be prepared for a long day, don't be afraid to ask for a short break! Everyone was personable and there were many interesting conversations, most of my one on ones went over their allotted time.
I applied online. I interviewed at Ladders in Sep 2020
Interview
After a call with the VP, i was immediately scheduled with a bunch of engineers. Mostly behavioral, all very pleasant. 2 pretty easy technical questions. Final call was with CEO.
Got an offer but got a weird feeling from the company at how rushed they seem once they extended the offer.
At the end, wasn't feeling the product enough/looking for more diversity.
Interview questions [1]
Question 1
Unit testing experience, "name a time when..." type questions. Can't remember the technical ones but I remember they were very easy.
I applied through a recruiter. I interviewed at Ladders (New York, NY) in Jul 2017
Interview
Recruiter found me on LinkedIn. Had a quick phone call to scope out interest and skills (and probed for salary range). Second phone call for actual phone screen; asked basic questions about algorithms/data structures, backend, Linux, and other dev tool knowledge. 3.5 hour on-site visit included two coding questions on paper; OO modeling and one more algorithm question on whiteboard; and talk with HR director. Follow-up on-site was a 1/2 hour discussion with an engineer from a different team than in the first round.
Technical portions definitely require prep but were well executed on their part. Each meeting wasn't a lecture, but a conversation, and the interviewers were polite.
Ultimately, they decided I was a good cultural fit, but lacking enough experience for Level 2.