Video summary

SWE looking to become a quant trader gets honest advice | Call In 6

Main summary

Key takeaways

Educational

Main ideas, concepts, and lessons conveyed

  • The advice is aimed at a CS student (with a software engineering internship lined up) who wants to transition into quantitative trading (Quant) and likely pursue a quant internship/program (e.g., a discovery/sophomore track) at a top US university or a relevant trading firm.
  • Quant readiness isn’t only about “knowing coding.” It’s about building relevant technical foundations and being able to perform on the types of questions used in quant interviews/screening.
  • Communication and interview presentation matter significantly—e.g., cadence, filler words, and how you signal confidence—which can determine whether you pass early screens even if you know the material.
  • Expected value, probability, combinatorics, and statistics are recurring technical themes in quant phone interviews.
  • You should prepare a trading project aligned with recruiter themes/keywords (e.g., risk modeling, big data, working under pressure), even if your resume lacks direct trading experience.

Methodology / preparation steps mentioned

1) Build technical foundations relevant to quant roles

Use relevant programming languages/skills

  • Avoid assuming language transferability. Instead, use languages relevant to the target role.
  • Potentially relevant examples mentioned:
    • Lower/mid-level / performance-oriented work: C (possibly C++)
    • Python (already used in school) and possibly higher-level Python for ML/data tooling

Develop knowledge in “secondary/adjacent” systems concepts

These are used to signal you can operate in quant-relevant environments:

  • Networking
  • Computer architecture
  • Middleware / communication technologies
    • Example mentioned: gRPC
    • Note: “CFA” is mentioned, but appears unclear in the subtitles
  • Databases
    • Examples: SQL, NoSQL
  • Visualization / monitoring tools
    • Example mentioned: Grafana
  • Network traffic / packet-level analysis
    • Examples: pcap files, Wireshark
  • Distributed systems
    • Asynchronous client/server communication
    • Sending/receiving data across systems
    • Microservices and multi-threaded/distributed architecture, including communication across many servers/hosts

Get clarity on what you’ll code in

  • Ask the team early about tools/resources and what the intern will actually use.
  • Don’t guess blindly.

2) Get aligned with the exact interview/job expectations by asking early

  • Contact the hiring team ASAP (or the appropriate contacts).
    • Ask for expected tech stack/tools.
    • Prepare a list of questions for engineers/team members.
  • Confirm your Python/C++/other language positioning
    • Example guidance: don’t only say “I use Python”—know the versions and key language concepts.

3) Upgrade Python knowledge to be interview-ready

  • Learn what’s changed across Python versions
    • Guidance mentions reading the change set, specifically referencing 3.11 / 3.12 (subtitles also show some uncertainty about later versions).
  • Know important Python fundamentals
    • Example: Global Interpreter Lock (GIL) and how Python concurrency behaves.
  • Be ready for “Python feature” style questions
    • The advice is to answer more specifically than “packages are easy.”
    • Examples mentioned:
      • List comprehensions
      • Whitespace/structure enforcement differences (noted as interview-style specificity)

4) Start C++ fundamentals if you’re not strong yet

  • A suggested consistent self-study plan is mentioned (subtitles suggest something like “read a chapter a week,” and ideally complete a longer plan).
  • Resource mentioned: cpp.com

5) Prepare a quant-specific trading project (don’t wait for “trading experience” to appear)

  • You likely need a trading project.
  • Align it with what recruiters screen for
    • Recruiters may not go very deep; they check for keyword/theme alignment.
    • Example themes/keywords mentioned:
      • Can work under pressure
      • Can work with big data
      • Experience modeling risk
  • Use a firm’s website as a map
    • Look at key themes they list for candidates, and make sure your project/resume hits them.

6) Quant phone interview preparation: probability + combinatorics + basic stats

Expected value (EV)

  • Practice questions where EV is the same but variance differs.
  • Core lesson: you may be asked which bet you prefer when outcomes differ in spread—discussion centers on variance vs expected value.

Probability basics and coin-style question patterns

  • Single coin: probability of heads.
  • Multiple independent coins:
    • Probability of heads on either coin
    • Probability of both heads
    • Etc.

Combinatorics / sequences / patterns

  • Sequence continuation problems (example given: “1 2 4 8 16 32 … next number = 64”).

Distribution knowledge

  • Poisson distribution is discussed as a model for expected occurrences over time with a rate (the explanation is described as approximate, but the intended idea is event counts over time).

7) Improve interview communication style (pass the “vibe check”)

Eliminate filler words

  • Remove “um/uh”.
  • The speaker treats filler words as a sign of underconfidence and notes they can lead to failing screens.

Adjust cadence quickly

  • Guidance suggests you can reduce common filler words within a week with effort.

Screen question focus

  • For non-technical screens: story/behavioral questions such as
    • “Tell me about yourself”
    • “Why Quant?”
    • “Why that firm?”
  • For quant screens: emphasis on probability/statistics, sequences, and related concepts.

8) Guidance on how to respond when you don’t know answers

  • It’s framed as better to not know on a mock stream/screen than to fail in a real interview.
  • Specific advice when stuck:
    • Don’t panic
    • Ask/answer carefully
    • Use practice to normalize gaps and prepare for them

What the conversation emphasizes about “rudeness” / tone

  • The speaker anticipates accusations of being “rude/toxic,” but argues the intent is direct, helpful, and to-the-point.
  • The closing includes meta-commentary about expected YouTube criticism, reframing it as coming from people with “mental issues.”
  • Regardless, the core message for the viewer is that high candor is meant to improve candidate outcomes.

Speakers / sources featured

  • Main advisor / host (unnamed): gives interview and preparation guidance (primary speaker)
  • CS major student / caller (unnamed): asks about preparing for a Quant internship and discovery program
  • IMC: referenced as a firm the student might interview with (e.g., “Why do you want to work at IMC…”)
  • Seer: referenced as another firm in the same question pattern
  • “Top 20 University in the US” / “SIG sophomore Discovery Day program”: referenced as the student context/program
  • YouTube audience/commenters (unnamed): referenced in closing remarks

Original video