> For the complete documentation index, see [llms.txt](https://jamiewen00.gitbook.io/tech-lead-handbook/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://jamiewen00.gitbook.io/tech-lead-handbook/hiring/case-study.md).

# Case Study

## The What

After the Code Challenge, some senior roles need to pass a case study to prove their soft skills. It is needed for senior roles, like Lead Developer, Tech Lead, Project Manager, Senior Analyst, Product Manager, etc.

## The How

### A case study for a technical role

* Overview: debrief the position description and the purpose of this case study
* Background: bring some context
* Hypothesis: self-explanatory
* Task: the problem you give them
* Deliverable: the outcome you want them to deliver

### A case study for a lead role

* Background: The team setup: an engineering team, a cross-functional team, or a product-led team
* Situation: the current situation, and what is the problem? 
* Goal: the expectation of this role, or
* Deliverable: how do you want them to present back to you

They will probably be given a case study. They are required to present a response with a short slide show or simply draw on a whiteboard.

## :white\_check\_mark: Exceptions

* A case study is a must for a leader's role

## :red\_circle: Red Flags

* Lack of a big picture
* Failed to verify assumptions

## :scroll: Tips

* You can just use the problem you currently have
* No harm to use the real-world samples

## :hole: Pitfalls

* Overpolished presentation than the content