
Namely Software Engineer Interview Questions
& Process
Real candidates share what happened, how many rounds they had,
and how the experience turned out.
Based on 11 interview experiences · FREE TO READ
Candidate interview experiences
First-hand accounts from people who interviewed at Namely.
Software Engineer
So the interviews were actually pretty decent, even fun. But man, the communication was just awful. They hit me up for a third interview even though they said the first two would be it. Then it was weeks of just 'we're working on it' with hardly any updates. The person I was dealing with went on PTO, so I talked to different people from the hiring team, but it seemed like they barely talked to each other. When my original contact got back, they told me they'd offered the job to someone else based on experience. Then they asked if I was still available if that offer fell through by a certain date. A few days after that deadline, they told me the other person didn't accept, but they weren't offering me the job anyway because the other guy apparently showed them exactly what they needed. Seriously, why is this only discovered so late? And why couldn't they communicate clearly with each other or me? Different people involved, hardly any info shared, and they were missing deadlines themselves. The actual interviews were fine, enjoyable even. But the rest of it was super unprofessional and it felt like they kept changing their minds. If your interview process is still a work in progress, fine, but don't leave candidates hanging and be so uncommunicative that it messes up the whole hiring thing.
- Can you share your experience collaborating with different teams on cross-functional projects?
- Tell me about your experience with programming questions in JavaScript and design/implementation tasks in React.
Software Engineer
The algorithm part was mostly done, but I struggled a bit with populating an array. The interviewer stepped in and fixed it. The function worked fine with all test cases. However, he gave negative feedback to HR about my basic loop structure skills, which felt unfair. The system design interviewer, unfamiliar with IoT, asked a question about it. He seemed receptive to my ideas and didn't object, yet told HR my solution was vague. Honestly, he wasn't equipped for a technical interview. He could have just said there were better candidates, which would have been more straightforward.
- Can you solve a basic algorithm problem?
- Let's discuss a system design scenario.
Senior Software Engineer
Started with a recruiter call, then a code pairing session. The on-site was pretty intense, more rounds and people than usual. It had 2 coding challenges, a system design question that changed as we went, and some 1-on-1s for introductions and to check cultural and professional fit. Despite being a lot, the on-site let me really connect with the interviewers. The offer was okay compared to others, but I took it because I believe in the product and company, everyone was great and energetic, and I connected with some people professionally. The recruiter was key throughout and really made Namely stand out.
- A few problems about manipulating arrays, where the complexity grew as we went along.
Namely Software Engineer Interview Questions
Quoted word for word from Namely interview reports.
“How about Trapping rain water?”
Read reports →“What is BFS?”
Read reports →“Can you explain Graph traversal algorithms?”
Read reports →“What is DFS?”
Read reports →“Could you solve Reverse Polish Notation?”
Read report →“Can you write a program that can evaluate expressions in a custom DSL format, like the example provided: (+ 1 3 2 (* 8 6) 7 (- 1 8 (+ 5 2 43) 9) 81)?”
Read report →“How do Queues work?”
Read report →“How do Stacks work?”
Read report →“Do you understand Tree traversal questions?”
Read report →Formats, difficulty and experience
Across all 11 Namely interview reports.