The 30 second answer
Pick a project with real stakes where you made the key decisions. Use STAR, but spend most of the time on the actions: the options you weighed, why you chose one, and what went wrong. Close with a measured result and what you would change. Keep it under two minutes on a recruiter call and offer to go deeper with the engineers.
Reported. "Describe a project" appears in a May 2026 Glassdoor snippet; the 2023 post mentions career accomplishments; How We Hire recommends STAR.
Template.
- Situation (one sentence): the system and why it mattered.
- Task (one sentence): what you owned.
- Action (most of the answer): two or three decisions and the trade-off behind each, including one thing that did not work.
- Result: a measured outcome, such as latency, error rate, cost or time saved, and what it enabled.
- Reflection: what you would do differently.
Choose well. Prefer a project close to the role, for a search team something with indexing, query latency, ingestion or relevance. Prefer one where you can name the trade-offs. Avoid stories where the result depends on numbers you cannot explain in detail.
Link to the Founding Mindset. If it fits naturally, connect the story to one quality, for example "Speed" through shipping an imperfect version fast, or "Act like an owner" through fixing something nobody had asked you to fix.