> 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 --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://jamiewen00.gitbook.io/tech-lead-handbook/hiring/case-study.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.