
Culture Amp Software Engineer Interview Questions
& Process
Real candidates share what happened, how many rounds they had,
and how the experience turned out.
Based on 27 interview experiences · FREE TO READ
Candidate interview experiences
First-hand accounts from people who interviewed at Culture Amp.
Software Engineer
after applying, the first step was a recruiter call where they asked about eligibility, what I wanted from the internship, a new skill I'm working on, and how I take initiative and set goals. then there was a campus visit, a behavioral interview, and a technical interview.
- Are you eligible?
- What are your internship goals?
- What's a new skill you're developing?
Software Engineer
The interview process was pretty straightforward. It started with a recruiter call, then a behavioral interview with people and leaders. The interviews felt professional and nice. I felt that the company's way of operating aligned with my values. Then, after two weeks of no news, I was told that due to internal requirement changes, the role was no longer available. They said they liked me and had other roles coming up that I'd be a good fit for, in the same business area with the same people I interviewed with. They said they'd reach out when those requirements were finalized. I never heard from them again, even after following up a few weeks later. I get that requirements change and things fall apart, but they need to be more professional. Given the recent layoffs, people put a lot of hope in interviews. If you're interviewing with multiple places, I wouldn't rely on CultureAmp's feedback or wait for anything to happen. They don't pay competitively, but I'd always choose culture over salary. Based on my experience, CultureAmp offers neither.
- Tell me about how you collaborate with your colleagues.
- Can you describe a time you had to work with a difficult person?
- How do you approach communication with stakeholders?
Software Engineer
So for the technical interview part, they gave me the test requirements beforehand, and I had two days to get ready. The test wasn't super hard, but it was clear that you really need to stick to their exact instructions and communicate well. They seem to really care about pair programming and want you to follow their specific way of doing things. Like, they're big on Test-Driven Development (TDD) and expect you to plan your solutions around that. If you change anything from what they asked for, even if you think it's better, they don't like it and you might fail. It's kind of confusing why the technical interview is so strict. It felt less about my actual skills and more about following a rulebook. Any small mistake in their process, even if you meant well, can mess things up. While I get their point, this kind of interview might not work for everyone.
- Can you go over the rules for the interview process?
Culture Amp Software Engineer Interview Questions
Quoted word for word from Culture Amp interview reports.
“What were the results of the project?”
Read reports →“What is the perception of you by others?”
Read reports →“Can you solve a Leetcode-style design question using Typescript?”
Read reports →“How do you take initiative and set goals?”
Read reports →“How would you guide a junior team member?”
Read report →“Can you go over the rules for the interview process?”
Read report →“Can you tell me what you know about Culture Amp?”
Read report →“Could you share an instance of a failure you encountered?”
Read report →“Can you share an instance where you showed perseverance in overcoming challenges?”
Read report →Formats, difficulty and experience
Across all 27 Culture Amp interview reports.