Describe a Complex Project You Worked On and Why It Was Challenging
WaymoSoftware Engineer · OnsiteLast updated
Behavioral hiring-manager question: describe a complex project you worked on and explain why it was challenging, often after a resume walk-through. Tests choosing a project that fits the level, naming the real difficulty, personal ownership and outcomes.
In a hiring-manager round, the core behavioral question is: "Tell me about a complex project you worked on. Why was it challenging?" A closely related version appears in onsite loops as a brief walk-through of your resume followed by "describe a challenge in your previous work."
Hiring-manager rounds of this kind can be short, and candidates have reported receiving a decision within minutes of the call ending, so your first answer carries most of the weight. Prepare the answer you would give.
Clarifying Questions
- How much technical depth does the interviewer want versus team and stakeholder detail?
- How long should the first answer be before the interviewer starts asking follow-ups?
- Should the project be recent, or is the most relevant project acceptable even if it is older?
Hints
Hint 1
Choose the project for its scope: Pick the project whose scope and ownership best match the level you are interviewing for, not simply the one you remember best.
Hint 2
Name the hard part precisely: "It was complex" is not an answer. Decide which one or two specific difficulties made it hard and what you personally did about them.
Follow-up questions
- What would you do differently if you started the project again today?
- What was the hardest technical decision, and how did you validate it?
- Tell me about a disagreement during this project and how it was resolved.
- How did you measure whether the project succeeded?
Solution walkthrough is for members
Get the full walkthrough with reference code and complexity analysis, plus Kitty Coach at 300 messages a day. Hints, the code runner and community answers stay free.