Yahoo News interview (April), Round 1.
Question 1: Talk about your background and one of your projects in detail — they dug deep into one particular project.
Key points for the answer (aim for a total of 3–6 minutes) and my own suggestions:
- Quick background (20–30s): one sentence on the role, your responsibilities on the team, and list 1–2 projects.
- Deep-dive framework (3–4 minutes, using STAR):
- Situation: project goal, why it was done (1 sentence)
- Task: what you were responsible for, the success metric (1 sentence)
- Action: the main points (2–3 points, walk through the technical decisions)
- system architecture and key components (language, DB, queue, cache)
- key trade-offs and alternatives (why you picked A over B)
- one concrete difficulty and how you solved it (debugging/optimization/experiments)
- Result: quantified outcome (%, latency, traffic) plus a timeline (1 sentence)
- Closing: sum up two things you learned and what you'd improve next time (15–20s)
Question 2: How would your manager describe you? (short version)
Structure and suggestion: give two strengths, each backed by one example (30–60s total). Example phrasing:
- "They'd say I'm a reliable owner." (example: I independently owned feature X and shipped it early, cutting regression bugs by Y%)
- "They'd say I'm a practical problem-solver." (example: found the latency bottleneck and cut P95 from A down to
The interview lasted about an hour. The conversation felt really good and the interviewer gave positive feedback. Later, through a follow-up, I found out the position had been paused. Nothing came of it.
Discussion
Loading comments…