The Big Three Question

Tell me about yourself (TMAY)

• Many interviewers have not reviewed your resume nor the position
• Strong TMAY guide the interview toward topics that showcase the best of your career
• Express passion for the opportunity

Keep TMAY Short: 30s - 2 minutes is ideal we need to save time to deliver the signal

Structure

Personal summary (2-3 sentences)

Condensed linkedin about section. Mention your role, Backend/Full-stack, YoE and title.

Example: I'm a Senior Engineer, focused on backend with five years of experience building scalable systems and solving tough performance challenges. I'm passionate about crafting solutions that are not only efficient but also highly maintainable without documentation.

Accomplishment (1-2 sentences)

Showcase core skills and business impact. Align with the current roles and expandable to later questions

Example: At TechNova, I led a project to optimize our Redis-based caching strategy, which reduced page load times by 40% and improved customer retention.

Do not use STAR/CARL, keep high level and intriguing. Our goal is to spark some interest

Forward looking statement (1-2 sentences)

Link your past work to the future role to show hat you're the ideal next step

Example: I'm excited to bring my experience in distributed systems to a team tackling large-scale challenges and I'm looking to become a TL because I really enjoy the mentoring and technical vision parts of my job.

Example

Mid-Level Engineer

I'm a software engineer with four years of experience, specializing in frontend development and creating intuitive user interfaces. I'm really passionate about making experiences users love.

At Acme Co, I led the implementation of a design system that reduced UI development time by 30% and ensured consistency across the product. Before that, I worked on a customer feedback platform where I integrated a machine-learning model into the frontend to provide real-time insights.

For my next role I've been looking for a space in healthcare where I can solve tough problems with a user-centric lens and Synertech seemed like a perfect fit.

Notice the personal summary establishes who they are and what they care about. The accomplishments are specific with quantified impact. And the forward-looking statement connects their experience to this specific opportunity.

Senior Engineer

I'm a senior software engineer with over 10 years of experience building distributed systems and scaling complex applications. My expertise lies in designing architectures that work across a large array of teams and use cases.

At Flux, I spearheaded the migration of our monolithic application to a microservices architecture, reducing downtime by 50% and improving team productivity. Previously, I built a real-time analytics platform handling millions of daily transactions, using a combination of Kafka and Elasticsearch. I also enjoy mentoring junior engineers, helping them grow into confident contributors.

To continue using and grow my experience with large scale systems is the goal with my next role. I enjoyed chatting with the engineer I met at the conference last week, so excited to be here.

What determine senior here is:

1. Scope increase cross team
2. Mentoring juniors

[!note]
Don't say negative things about previous employed, describe the motivation for something new, be positive what you're headed toward

Mistake

1. Dont say I work at X and move to Y, now at Z
   • We dont need a walk through here, this makes your older experience as euqal important as your most recent one.
2. I love programming since i was 6
   • No need a biography, starts with who you are professionally now
3. I'm a swe at ABC with X YoE (full stop)
   • Not enough info
4. My current company has problem X,Y,Z
   • Make listener wonder if you're the problem
   • Expose lack of ability to change technical and cultural in your role
   • Say something like this instead

   As I've grown technically, I've become increasingly interested in working on developer tools and infrastructure that can impact how entire engineering teams work. That's what draws me to this role: the opportunity to build in a culture that knows how to ship and is known for technical excellence.

Tell me about your favorite project

Detail description of your daily work over a long period of time. This answer alone has already determine the majority of the behavior

These are the same questions:

1. Tell me about your favorite project
2. Tell me about your most impactful project
3. Tell me about a time when you solved an ambiguous problem

Doesn't matter just reply with the same story. They dont really care which one is your "favorite".

Choosing your "favorite" project

Impact: Choose work that moved meaningful business metrics — could be revenue growth, performance gains, cost savings. Anything with quantifiable specific numbers

Scope:

• Project with substantial breadth or duration that gave you opportunities to demonstrate multiple signal areas.
• Projects that spans weeks, months, involving cross-functional collaboration, both technical and non-technical problem solving

Personal contribution

• You have to be a primary driver, not just a participant
• Being part of high-impact team is not enough, you need clear ownership of significant actions

Sweet spot is to find a project where all three intersect. If we can't find one that has all three, prioritise personal contribution

• A smaller project where you led everything is better than a massive initiative where your role is replaceble

Questions that always comeup

1. Were there any conflicts you encountered?
2. What was the hardest part?
3. What would you do differently?

Tell me about a time you resolved conflict

[!important]
If there is a red flag here, you likely not get hired, they dont want to hire jerks

Conflict resolution

• Be assertive: if you think you're right, you speak up
• Go directly to the source: you do not triagulate around the source or hide behind management
• Remain emotionally control: if other anger, you stay calm
• Stay focus on the out come: prioritise the product, not personal game
• Make data-driven, rational decisions

Common conflict stories

1. Technical disagreements
2. Prioritisation
3. Timeline pushback
4. Resource allocation
5. Process change

Choose the right conflict story

1. Stake are high: conflict over formatting a codebase versus conflict over long-lived system design matters
2. You were deeply involved: Being a central player in a conflict
3. You ended up being right: less risky to tell a story where you were right

If your company ask about a time where you were wrong:

• Choose a story where you not wrong in advance — initial position was reasonable given the information at the time
• This way you demonstrate humility and growth mindset without looking like someone with poor judgement

Common element of successful conflict stories

1. Be prooactive in raising concerns
2. Only start constructive conflicts — raise disagreement when they help the product/user not because you prefer a different approach
3. Seek to understand from their side
4. Choose the right communication channels — Comments on PR or shared document are rarely effective conflict resolution mediums
5. Demonstrate empathy — understand from their side
6. Demonstrate maturity — even face of emotional circumstances, maintain your composure and act in a professional laudable way
7. Use data to make decisions
8. Involve the right coworkers at the right time: If people are needed, you pull them in when needed, not before to create drama and not after the project has suffered a stall
9. Don't take too long – dont let the conflict delay the project
10. Preserve relationships —still maintain friendly relationship if they didnt get the preferred outcome

Result includes the relationship

In the learning we should includes the relationship