76
/ 100
76
/ 100
A clear pass for a mid-level backend role: correct, tested code and strong ownership stories. Two fixes would lift it to a strong hire: present complexity unprompted and keep manager-round answers short.
Rubric
Solid on APIs, caching and the data layer; the frequency-count solution was correct and idiomatic. Hazy on how a consumer group rebalances.
Clarified the input before coding and tested an edge case unprompted. Took the hint on the heap only after being asked for the complexity.
Clear structure in the behavioural round; two long answers in the manager round lost the question. Fillers under control.
Owned the failed launch story without blaming the team. Asked good questions about on-call and growth at the close.
Round by round
Round 1
A crisp introduction with a clear reason for the move; salary expectations stated with a range and a rationale.
Strengths
Improve
Round 2
Good product sense on the checkout funnel; the prioritisation answer ran long and the trade-off never landed.
Strengths
Improve
Round 3
Coding round: correct solution to top-k frequent elements with a dictionary and a sort; identified O(n log n) and sketched the heap alternative when prompted. Caching discussion was strong, consumer-group rebalancing weak.
Strengths
Improve
Round 4
The failed-launch story followed situation, action, result and owned the mistake; the conflict story stayed vague on what you actually said.
Strengths
Improve
Round 5
Thoughtful questions about on-call rotation and the first ninety days; closed warmly.
Strengths
Coding round
Each submission was reviewed live and counts towards role knowledge and problem solving.
Submission 1 · Python
def top_k(nums, k):
counts = {}
for n in nums:
counts[n] = counts.get(n, 0) + 1
return sorted(counts, key=counts.get, reverse=True)[:k]
print(top_k([1, 1, 2, 3, 3, 3], 2))[3, 1]
Key moments
Your words, the panel's read, and a stronger version.
You said
“We cut checkout drop-off from eleven to seven percent by removing the address re-entry step.”
Assessment
Exactly what a hiring manager wants: a number, a cause and your part in it.
Better answer
Add the baseline period and how you measured it: "over six weeks, A/B tested against the old flow".
You said
“I would sort the counts and take the first k.”
Assessment
Correct and readable. The panel was listening for the complexity and the alternative.
Better answer
"That is O(n log n) from the sort; with a min-heap of size k it becomes O(n log k), which matters when k is small."
You said
“There was some friction with the designer but we sorted it out.”
Assessment
Too vague to score. Conflict questions test what you actually said and did.
Better answer
Name the disagreement, quote the sentence you said, and give the outcome in one line.
Next steps
Picked for the gaps this panel found.