kevin. logo

kevin. Software Engineer Interview Questions
& Process

Real candidates share what happened, how many rounds they had,
and how the experience turned out.

Based on 9 interview experiences · FREE TO READ

2.7 Rounds average
Average Typical difficulty
44.4% Positive experience

Candidate interview experiences

First-hand accounts from people who interviewed at kevin..

Showing 3 of 9
kevin. logo
kevin.

Software Engineer

Engineering · more than a year ago

Mid Difficult Positive experience Accept offer 3 rounds
Interview process
Recruiter call Take home Technical screen Onsite
Interview formats
Technical Coding Behavioral

I applied via LinkedIn. First, I had a video call with a Recruiter. At the end of that call, they gave me a Java Spring project. I had to analyze it and write down improvements, implement them if possible, or add comments in the code. Then, I had a 2-hour video call with a tech lead for a code interview. It focused on the Java Spring project. In the first 15 minutes, I talked about the improvements I planned and made. The rest of the interview involved adding more features to the project live. For live coding, make sure your IDE is ready before the call, and explain your thoughts before coding. If a solution is long, add comments explaining your steps and then write the code. This way, the recruiter can confirm if you're on the right track. Comments are also good if you're short on time. Lastly, there was a cultural fit interview with the hiring manager where I was asked about past projects, challenges, and similar things.

Confirmed questions0 questions

No confirmed questions were included in this interview report.

kevin. logo
kevin.

Senior Software Engineer

Engineering

Senior Difficult Positive experience Accept offer 5 rounds
Interview process
Recruiter call Take home Technical screen Onsite Background check Offer
Interview formats
Technical Coding Behavioral Presentation

The hiring journey kicked off with a brief 15-minute chat. Right after, they sent over a technical challenge. I got to work on it at my own speed, and when I felt ready, I scheduled the technical interview. This interview was pretty much a two-hour code review of my submitted solution, with a small bit of live coding thrown in. Passing that meant I moved on to a cultural chat with the team lead. During this chat, the lead gave me the lowdown on the role, the team dynamics, and the kind of challenges I'd encounter if I got the job. They also asked me to share a bit about my background and posed a lot of questions like, 'Tell me about a time in your career when you had to deal with a specific issue...'. Honestly, I really enjoyed the whole experience. I especially liked that they gave me the technical challenge to work on for a few days, which felt like a realistic work task, unlike those timed algorithm tests some places use. Plus, they were super quick with their responses and moving things along. I only had to wait a day after the technical interview and two days for an offer after my final interview. All in all, a fantastic process.

Confirmed questions3 questions
  • Can you explain how you would improve the performance of this specific SQL query?
  • Describe a time you encountered a team problem and the steps you took to resolve it.
  • Could you share an example from your career of confronting a particular challenge and how you managed it?
kevin. logo
kevin.

Software Engineer

Engineering

Senior Average Negative experience Decline offer 2 rounds
Interview process
Recruiter call Technical screen
Interview formats
Technical Coding

I had a good chat with HR, they were very nice. Then I had two code review interviews with engineers who were extremely arrogant. They were very dismissive and acted like they were on a power trip. For example, after I admitted I hadn't thought of a certain idea, one interviewer said it wasn't just a good idea, but a 'brilliant' one, and continued to make similar comments. It felt like there was no real discussion, just them trying to assert dominance. Surprisingly, HR said the feedback was positive and wanted to discuss compensation, but I decided not to proceed because I didn't want to work with those engineers.

Confirmed questions1 question
  • Why wasn't a script created to launch both the frontend and backend simultaneously?

kevin. Software Engineer Interview Questions

Quoted word for word from kevin. interview reports.

Given that a rope takes 1 hour to burn, how can you measure exactly 45 minutes? Note that you cannot burn half of the rope.

Read reports

Why wasn't a script created to launch both the frontend and backend simultaneously?

Read reports

Can you explain how you would improve the performance of this specific SQL query?

Read reports

What approaches would you take to solve challenging LeetCode problems?

Read report

Can you explain the call to review the take-home challenge?

Read report

Can you describe the intricacies of various data structures?

Read report

Formats, difficulty and experience

Across all 9 kevin. interview reports.

Interview formats

Technical 38.1%
Coding 28.6%
Behavioral 28.6%
Presentation 4.8%

Interview difficulty

Easy 22.2%
Average 44.4%
Difficult 33.3%

Candidate experience

Positive 44.4%
Negative 55.6%