
Gett Software Engineer Interview Questions
& Process
Real candidates share what happened, how many rounds they had,
and how the experience turned out.
Based on 15 interview experiences · FREE TO READ
Candidate interview experiences
First-hand accounts from people who interviewed at Gett.
Software Development Engineer
The interview process began with a quick phone call where they talked about the company and asked some general questions. After that, I had to do an online take-home test with two questions. Then, I had an in-person interview with a team lead who was really nice and asked both personal and technical questions. The next step was another in-person interview with a different team lead, who just asked one technical question, which felt more like a 'get to know you' chat. After that, there was an HR interview, and if I passed that, I had a final interview with the VP of R&D.
- How would you sort an array containing only '0's and '1's, ensuring O(n) time complexity and O(1) memory complexity, without using an extra array?
Software Engineer
The hiring process for this role was supposed to follow the 'Who: The A Method for Hiring' book structure but it took nearly a month and was quite a ride. The initial interviews were rescheduled three times due to issues with the interviewer, so it took about 1.5 weeks for the first one. The first interviewer was great, explained the company's vision and goals, asked about my background, and gave three technical questions. The second interview was scheduled two days later. The interviewer was more senior, gave a lot of company info, and asked similar personal questions as the first. No technical questions this time, but I suspect they usually give a 'Codility' task. Instead, I got a small home task. Since I wasn't familiar with the required tech, it took me a day to learn and complete it. I got feedback the next day and the third interview, with HR, was scheduled two days after that. Some rescheduling happened again. On the HR interview day, I had another, fourth, interview. The HR questions were very similar to the second interviewer's. I wasn't surprised to be asked questions I'd already answered in the final interview. It might have been okay if the last interviewer wasn't so indifferent and dry. Two days later, they sent a non-constructive rejection saying they chose a candidate with more coding experience (I have 6 years, they needed more). I asked for more details but got none that would help my job search. It's hard to say if it was a negative experience, but definitely not positive, especially the way the final feedback was delivered.
- Can you devise an algorithm to sort an array of integers in O(n) time complexity, given that memory usage is not a constraint?
Software Developer
So the interview process is like, we'll do live coding to see how you code, then probably 2-3 technical interviews with the team. They'll be asking you stuff about how you solve problems, your technical knowledge, and we'll have design sessions to see if you can build and scale systems.
- Can you walk me through some of your past projects?
- Tell me about your soft skills.
- What is your motivation for this role?
Gett Software Engineer Interview Questions
Quoted word for word from Gett interview reports.
“What's the method to determine the number of nodes in a tree?”
Read reports →“What is the second shortest path problem?”
Read reports →“How would you sort an array containing only '0's and '1's, ensuring O(n) time complexity and O(1) memory complexity, without using an extra array?”
Read reports →“How does Spark MapReduce work?”
Read reports →“Can you devise an algorithm to sort an array of integers in O(n) time complexity, given that memory usage is not a constraint?”
Read report →“Explain the binary tree algorithm.”
Read report →“Could you create a binary search program for a tree?”
Read report →“Is your singleton implementation thread-safe?”
Read report →“Can you explain the BFS algorithm?”
Read report →Formats, difficulty and experience
Across all 15 Gett interview reports.