Answer why SWE and why Optiver

### What interviewers are looking for - **Motivation that matches the job**: real-time systems, performance, correctness, rapid iteration, ownership. - **Signals of learning speed and resilience**: the environment is intense; they want people who seek feedback. - **Evidence over claims**: concrete examples, measurable outcomes, and clear reflection. - **Team fit**: calm under pressure, direct communication, accountability. --- ## 1) “Why software engineering?” Use a 3-part structure: 1. **What you enjoy** (building, debugging, optimizing, shipping). 2. **What you’re good at** (systems thinking, data structures, performance profiling, etc.). 3. **Proof** (1–2 short projects with outcomes). **Template** - “I like SWE because I enjoy turning ambiguous problems into reliable systems.” - “I’m especially drawn to performance/correctness problems.” - “For example, in ___ I ___, which improved ___ by ___% / reduced latency by ___ms.” **Pitfall to avoid:** only saying “I like coding.” Add impact + evidence. --- ## 2) “Why this trading firm?” A strong answer ties **your skills** to **their environment**. **Good pillars for a market-making firm** - **Engineering as a differentiator**: latency, reliability, and execution quality matter. - **Fast feedback loops**: deploy/measure/iterate. - **Deep technical problems**: networking, CPU/cache, concurrency, observability. - **Culture**: ownership, rigorous postmortems, meritocracy (only claim this if you can explain what you mean). **Template** - “I’m interested in environments where engineering quality directly drives results.” - “I’m excited by low-latency distributed systems and careful optimization.” - “I’ve done ___ (profiling, multithreading, network programming), and I want to apply that in a setting with real-time constraints.” **Pitfall:** talking about money only, or being vague (“great culture”). --- ## 3) “What are your interests?” Aim for **1 technical + 1 domain** interest: - Technical: performance engineering, networking, distributed systems, C++/Rust, Linux internals, observability. - Domain: market microstructure basics, auctions/order books (keep it humble if you’re not experienced). **Template** - “Technically, I’m into ___; recently I learned ___ and applied it to ___.” - “Domain-wise, I’m curious about ___; I’ve been reading ___ / building a small simulator to understand ___.” --- ## 4) “What’s your biggest weakness?” Choose a real weakness that is: - **Not a core disqualifier** (e.g., “I’m careless with details” is risky for trading). - **Actionable and improving**. - Demonstrated with a **specific example + mitigation**. **Strong format: Weakness → Impact → Fix → Evidence** - Weakness: “I can over-invest in optimizing early.” - Impact: “It delayed delivery on ___.” - Fix: “Now I timebox profiling; first make it correct, then measure; I set explicit performance budgets.” - Evidence: “On the next project, I shipped baseline in 2 days, then improved performance by 30% with measured hotspots.” Avoid “I’m a perfectionist” unless you make it concrete and credible. --- ## 5) “How would teammates describe you?” Pick **3 traits** and back each with one line of evidence: - **Reliable / high ownership**: closes loops, communicates status early. - **Calm and methodical**: good incident response/debugging. - **Direct and collaborative**: asks clarifying questions, writes clear docs/tests. **Template** - “They’d say I’m (1) reliable, (2) structured in debugging, and (3) easy to work with.” - Quick proof points: “In ___, I ___; in code reviews, I ___; during incidents, I ___.” --- ## General delivery tips - Keep most answers **60–90 seconds**. - Always include **one concrete example** (project, internship, class, contest). - If you lack finance background, position it as **curiosity + ability to learn quickly**, not as expertise. - End with a forward-looking link: “That’s why I’m excited about building low-latency, correct systems here.”