Sample report · illustrative candidate
Priya Raman
Backend Engineer, Payments · Finished
78
Overall
- Coding
- 92
- Projects
- 74
- Fundamentals
- 68
Project round
You designed the caching change well and were honest about how it was measured. Testing before release is the gap for this role.
- 88
Caching and service designStrong
You explained why pricing was the hot path and put one read-through cache in front of three services. You raised invalidation on price changes without being asked.
- 76
Performance measurementSolid
You said the cache cut p95 latency by about 40 percent. Asked how you measured it, you compared a week of dashboard p95 before and after, and noted the traffic dip that week yourself. A strong answer would have compared like-for-like traffic or used a load test.
- 58
TestingDeveloping
You described checking the dashboard after release, but no tests before it. A strong answer would cover how stale prices are caught.
For a follow-up interview
- How would you verify the latency gain under the same traffic?
- How would a stale price be caught before a customer saw it?
Coding review
11 of 11 hidden tests passed. Likely O(n) time against an O(n) target, labelled as an estimate.
3 warnings in the monitoring log