← Citi Interview Insights

Citi·Software Engineer·Technical Phone Screen·Intermediate

Intermediate
May 2026

Summary

Citi software engineer interview that was basically one long resume deep-dive. They wanted everything: context, your specific role, decisions, numbers, trade-offs, and what you'd redo. More structured than I expected for what felt like a casual walkthrough.

Questions Asked (1)

Q1

Walk me through your resume, and for your most recent project cover: the problem you were solving, what you personally owned, the key technical decisions and your reasoning, concrete measurable outcomes, the hardest trade-off you navigated, and what you'd change if you did it over.

Technical Trade-offsSystem DesignProduct Analytics & Metrics
Author's notes

This is a lot to hold in your head at once and I didn't pace it well.

Create a free account to read the full note

AI HintsAI Generated

Suggested Approach

Start with a 30-second high-level resume summary, then dive into your most recent project using a structured narrative that covers problem, ownership, decisions, outcomes, trade-offs, and lessons. Keep it concise, quantify impact, and explicitly connect your choices to business and technical goals relevant to Citi.

Pro tip: Use a 'STAR-T' format (Situation, Task, Action, Result, Trade-off) and explicitly quantify outcomes with metrics like latency reduction, cost savings, or revenue impact—Citi values measurable business results.

1. Brief Resume Overview

Give a 30-second summary of your career progression, highlighting roles and skills that align with the job. End by signaling the most recent project you'll detail.

2. Problem & Ownership

Describe the business problem and its impact, then clarify your specific role and responsibilities. Use 'I' statements to show personal ownership.

3. Technical Decisions & Reasoning

Explain 2-3 key technical choices, the alternatives considered, and why you chose your approach. Tie decisions to constraints like scalability, security, or compliance.

4. Outcomes & Trade-offs

Present concrete metrics (e.g., 30% latency reduction, $X cost savings) and discuss the hardest trade-off you made, including how you mitigated risks.

5. Reflection & Improvement

Share what you'd do differently and why, showing self-awareness and growth mindset. Connect it to how you'd apply lessons at Citi.

Key Points to Mention

  • Quantifiable outcomes (e.g., performance improvements, cost savings, user growth)
  • Specific technical decisions and alternatives considered (e.g., microservices vs. monolith, SQL vs. NoSQL)
  • Personal ownership and leadership (e.g., led design, mentored junior engineers)
  • Trade-offs navigated (e.g., speed vs. quality, consistency vs. availability)
  • Alignment with Citi's priorities (e.g., regulatory compliance, security, scalability)
  • Lessons learned and how you'd apply them to future projects

AI-generated suggestions, not part of the candidate's original notes. May be inaccurate — verify before relying on them.