Three-Slide Project Deep Dive: Defend Trade-offs, Mentoring and Using AI on the Project
Company: Rippling
Role: Software Engineer
Category: Behavioral & Leadership
Difficulty: medium
Interview Round: Onsite
Prepare a presentation of at most three slides about a project you worked on, and present it to the interviewer. A project with large scope is preferred, ideally one you built from zero to one. During the talk the interviewer interrupts to ask why you implemented things the way you did and what trade-offs ruled out other approaches. The round ends with behavioral questions about the same project: did you mentor newer engineers on it, and how did you use AI tools over the course of the project? The role is a senior engineering position, so scope, ownership and judgment are what the interviewer listens for.
### Clarifying Questions
- How long is the presentation part, and how much of the round is reserved for questions?
- Are the slides shared ahead of time, or presented live over screen share?
- How much domain background can I assume the interviewer has?
- Should I focus on my own contribution, or also describe the rest of the team's work?
### Part 1 — Build and deliver the three slides
Choose the project and structure it into no more than three slides.
```hint One slide per question
Decide which three questions the interviewer must be able to answer at the end, and give each its own slide.
```
#### What This Part Should Cover
- Why this project shows senior-level scope, and what was built from scratch
- The problem, the constraints and the measurable outcome
- The architecture, and your personal ownership as distinct from the team's
### Part 2 — Defend the implementation under interruption
Answer the interviewer's "why did you build it this way?" and "why not another approach?" questions as they come.
```hint Keep the rejected option ready
For every major decision on your slides, prepare the alternative you rejected and the specific constraint or measurement that ruled it out.
```
#### What This Part Should Cover
- The alternatives considered for the key decisions and why each was rejected
- Evidence behind decisions (data, benchmarks, hard constraints) rather than preference
- Candor about what you would do differently now
### Part 3 — Mentoring on the project
Answer: did you mentor newer engineers on this project?
```hint Show the change in the person
Pick an example where you can say what the engineer could not do at the start and could do by the end, and what you did to get them there.
```
#### What This Part Should Cover
- A concrete mentoring relationship tied to the project's work
- Specific actions (scoped ownership, reviews, pairing) and the outcome
- How mentoring was balanced with delivery
### Part 4 — Using AI during the project
Answer: how did you use AI tools over the course of the project?
```hint Where it helped and where it did not
Prepare one task where an AI tool clearly sped you up and one place where you did not trust it, and how you checked its output.
```
#### What This Part Should Cover
- Concrete uses across the project (design exploration, code, tests, documentation, debugging)
- How output was verified, and the guardrails you or the team adopted
- Observed impact and the limits you ran into
### What a Strong Answer Covers
- A project with genuine senior scope, told as a clear story within three slides
- Decisions explained with alternatives, trade-offs and evidence, with composure under interruption
- A clear line between personal contribution and team effort
- Mentoring and AI-usage answers anchored in the same project, with concrete examples and outcomes
- Honest reflection on mistakes and what changed as a result
### Follow-up Questions
- If you had to deliver the project in half the time, what would you cut first?
- Which decision on your slides turned out to be wrong, and how did you find out?
- How did you know your mentee had actually grown, rather than just finished tasks?
- What rule would you set for reviewing AI-generated code on a team, and why?
Overview: A senior engineer project presentation round: present a large-scope project in at most three slides, defend implementation choices and rejected alternatives under interruption, then answer behavioral questions about mentoring newer engineers and using AI tools during the project.
Read the full Rippling Software Engineer interview experience this question came from