# What to expect?

# **Blueprint Recruitment: What to Expect**

We’re excited that you’re interested in joining <span class="s1">Blueprint**.**</span> This guide walks you through our <span class="s1">entire recruitment process</span>, what we’re looking for at each stage, and how to prepare.

There are <span class="s1">three stages</span>. Each one is designed to evaluate different skills, technical ability, problem-solving, and collaboration.

<table id="bkmrk-stage-focus-dates-st" style="height: 144px; width: 99.7531%;"><thead><tr><th style="width: 33.2921%;">**Stage**

</th><th style="width: 33.2921%;">**Focus**

</th><th style="width: 33.2921%;">**Dates**

</th></tr></thead><tbody><tr><td style="width: 33.2921%;">**Stage 1**

</td><td style="width: 33.2921%;">Application &amp; Resume Review

</td><td style="width: 33.2921%;">Feb 5 – Feb 17

</td></tr><tr><td style="width: 33.2921%;">**Stage 2**

</td><td style="width: 33.2921%;">Technical Challenge

</td><td style="width: 33.2921%;">Feb 17 – Mar 5

</td></tr><tr><td style="width: 33.2921%;">**Stage 3**

</td><td style="width: 33.2921%;">Blueprint Games + Interview

</td><td style="width: 33.2921%;">Mar 9 – Mar 23

</td></tr></tbody></table>

#### **Stage 1: Application &amp; Resume Review**

##### **What you’ll do?**

- <span class="s1">Fill out a short </span>Google Form application
- Submit your <span class="s1">resume</span>
- Answer a few questions about your interests and experience

##### **What we’re looking for?**

We do <span class="s2">**not**</span> expect you to know everything. We’re evaluating:

- Genuine interest in building technology for impact
- Willingness to learn and collaborate
- Technical foundations (relative to your experience level)

##### **What happens after you apply?**

You’ll receive a <span class="s1">confirmation email</span> with:

- The full recruitment timeline
- Resources to help you prepare
- Examples of previous technical challenges

##### **Outcomes**

- **If you advance:**
    
    You’ll receive the <span class="s1">technical challenge</span>, clear deadlines, and prep resources.
- **If not:**
    
    You’ll receive an email with learning resources, and an invitation to stay involved with Blueprint in other ways.

#### **Stage 2: Technical Challenge**

##### **What the challenge looks like?**

- <span class="s1">A </span>small full-stack project
- Tech stack:
    
    
    - **Frontend:**<span class="s1"> React</span>
    - **Backend:**<span class="s1"> FastAPI</span>
- Focused on <span class="s1">CRUD functionality</span>, not visual polish

##### **What we’re evaluating**

This is not a trick question or a speed test. We care about:

- Clear thinking and problem decomposition
- Code organization and readability
- Correctness over complexity
- Ability to explain your decisions

#### **Support during the challenge**

- Clear written instructions
- Starter resources
- Reminder emails before the deadline
- Automated submission via <span class="s1">**GitHub Classroom**</span>

##### **Outcomes**

- **If you advance:**
    
    <span class="s1">You’ll move on to </span>**Blueprint Games + Interviews**<span class="s1">.</span>
- **If not:**
    
    You’ll receive feedback, resources, and an invitation to apply again or join internal teams.

#### **Blueprint Games (Case Study)**

<span class="s2">You’ll work in a </span>**small team**<span class="s2"> on a </span>**realistic nonprofit case study**<span class="s2">.</span>

##### **What you’ll do**

- Break down a real product problem
- Define goals, features, and tradeoffs
- Discuss:
    
    
    - User needs
    - System design at a high level
    - Feasibility within a semester timeline

#### **Technical Interview**

##### **What we’re evaluating**

- Communication and collaboration
- Problem-solving approach
- Ability to justify decisions
- Comfort asking questions and iterating

<span class="s1">The interview is </span>technical but conversational<span class="s1">.</span>

It may include:

- Walking through your technical challenge
- Discussing a past project
- A small system design or architecture question

We’re looking for:

- Clear explanations
- Honest reasoning
- Ability to think through tradeoffs