Amazon Kuiper Commercial Services Software Engineer interview: debugging a full-stack repository

Amazon Kuiper Commercial Services·Software Engineer·Reported Jul 2026
Hard

Much of my process involved coding and debugging at home. I started with a HackerRank/LeetCode-style question with about 40 minutes to work on it, followed by a debugging assignment that took around an hour. The repository was a full-stack application, and one API call wasn't behaving as expected. I had to trace the problem and fix it so all the tests passed. Understanding how the existing pieces fit together and finding the failing path took real effort.

In a later programming round, the first question was fairly trivial math. The second was interactive: I had to work out what the interviewer wanted and implement several functions to meet that goal. These tasks felt practical, and the difficulty was turning incomplete requirements into working code. It felt like an assessment of how I'd execute when the requirements were ambiguous.

I didn't receive an offer. For me, the combination of debugging at home and the interactive implementation was the toughest part of the process.

Location: Jerusalem, Jerusalem. Overall feedback: neutral. Offer status: no offer.

Published

Curated and edited by PracHub

Discussion

Sign in to join the discussion. The author is notified of every comment.

Loading comments…

Interview at a glance

Company
Amazon (Project Kuiper)
Role
Software Engineer
Difficulty
Hard
Date
Reported Jul 2026

Real Amazon Kuiper Commercial Services interview experiences

First-hand reports from Amazon Kuiper Commercial Services candidates — the rounds, the questions they were asked, and how it went.

All 27 Amazon Kuiper Commercial Services interview experiences