Behavioral questions
GitHub
How do you go about starting a new project?
BehavioralLast seen Nov 6, 2026 · Software engineer
LeadershipAmbiguity
What they're looking for
This checks how you turn a new and often vague idea into a plan people can build. The interviewer wants to see whether you clarify the problem and the users first, find the biggest risks early, and get the right people aligned before much code is written. A strong answer walks through a real project start, the order of your steps and why, and how that early work paid off later.
What works
- Use one real project you started and walk through your first few weeks in order.
- Show how you defined the problem and what success meant before choosing a design.
- Mention how you found the biggest risk early, for example with a small prototype or an early talk with another team.
- Explain how you got agreement, such as a short design doc reviewed by the key people.
What hurts
- Jumping straight to the tech stack you picked.
- Describing a process with no real project behind it.
- Ignoring the people and teams the project depends on.
Sample answer
Think of your own story first, then compare.