Describe a Difficult Project
Company: Riotgames
Role: Software Engineer
Category: Behavioral & Leadership
Difficulty: easy
Interview Round: Technical Screen
# Describe a Difficult Project
Describe a difficult project you worked on recently. Explain what made it difficult, your specific responsibility, the decisions you made, how you handled uncertainty or setbacks, and the measurable or observable outcome.
### Constraints & Assumptions
- Keep private organizations, customers, and colleagues anonymous.
- Choose difficulty arising from real technical or coordination constraints, not merely long hours.
- Distinguish your contribution from the team's work.
### Clarifying Questions to Ask
- Is the interviewer looking primarily for technical depth, leadership, or delivery under ambiguity?
- How recent and how large should the example be?
```hint Center one hard decision
Depth comes from explaining the trade-off, evidence, and consequence of a decision rather than listing every task.
```
### What a Strong Answer Covers
- Context, stakes, ownership, and a concrete difficulty.
- Alternatives considered and evidence behind the decision.
- Collaboration, recovery from setbacks, and verification.
- Outcome with honest limitations and a lesson applied later.
### Follow-up Questions
- What would you change if you started the project again?
- Which risk did you underestimate?
Overview: Describe a recently completed difficult project, including the obstacle, decisions, and outcome.