How I Cracked Multiple Technical Interviews

Main ideas / concepts conveyed

• Goal: Take control of the interview using a “technique” so that the interviewer ends up asking (mostly) the questions you want.
• Interviewer mindset: described as low-stakes and routine:
  • Interviewers do many interviews; it’s part of their job.
  • They typically have a pre-chosen set of topics/questions they rotate through (e.g., ~25–30 topics).
  • They often interview for about one hour, then move on; they don’t want to spend 1.5–2 hours.
• High-stakes vs low-stakes mismatch:
  • The candidate fears rejection and wants to “crack it.”
  • The interviewer doesn’t experience the same urgency; selection/rejection doesn’t significantly affect their life.

Central “method” described (step-by-step)

1. Identify the first “known” question

   • The video claims the first technical question is almost always something like:
     • “Tell me about your project”
     • “What was your project?”
     • “Explain your project”

2. Treat that question as the “control point”

   • Because this question is predictable, use it to set the interviewer’s mental agenda.
   • Aim to stuff and highlight key technical concepts you prepared so the interviewer is more likely to ask follow-ups on them.

3. Reframe your answer into “concept delivery,” not business-story delivery

   • Instead of focusing on business use-cases and background, you should:
     • Mention the major technical topics you used
     • Name them one by one with brief linking/context
     • Ensure the interviewer “hears” the concepts you want tested

4. Include “major system parts” where follow-ups naturally occur

   • Examples from the video (Node/backend-style project):
     • Authentication / JWT
     • Authorization / role-based access control
     • Microservices architecture
     • API Gateway
     • Rate limiting (and discussing algorithms for it)
     • Database scaling / partitioning or changing behavior when data grows
     • AWS services (e.g., S3 storage, EC2 compute)
     • Jenkins CI/CD pipeline
     • Linting/quality checks and related tooling
   • These are presented as places to inject technical concepts the interviewer might follow up on.

5. Understand the two possible interviewer behaviors

   • After you name topics, the interviewer may:
     1. Ask follow-up questions based on the topics you mentioned, or
     2. Ask deeper questions on a concept you listed (e.g., “What is rate limiting?” “Which algorithms?”)

6. Leverage “reactivity” to cause topic-driven questioning

   • The video claims that once you successfully introduce topics:
     • the interviewer’s subconscious perception shifts from “zero perception” to positive confidence that you know things.
   • Even if the interviewer doesn’t ask everything, you increase the chance follow-ups will come from your prepared set.

7. Maximize coverage inside a short window

   • Because the interviewer has limited time (about one hour total), the emphasis is on:
     • “spending” some of that time to get concept coverage early
     • keeping the conversation anchored so the interviewer spends less time on unrelated topics

Additional example for AI engineer roles (concept “stuffing” adapted to AI)

• The same technique is described for AI/LLM interviews:
  • When asked “tell me about your project,” you intentionally include prerequisite/adjacent concepts so the interviewer can’t avoid them.
• Example structure:
  • Mention machine learning even if the project is primarily LLM-based
  • Mention algorithm comparisons and selection rationale
  • Explain how outputs are evaluated and how you add guardrails
  • Mention observability/tracking
  • Discuss cost optimization across multiple LLMs (e.g., low-cost then high-cost routing)
• Core idea: force the interviewer’s question space toward the concepts you prepared.

What the video claims you can achieve

• You can take control of roughly 50% of the interviewer’s time (as claimed).
• The interviewer becomes more likely to:
  • ask questions from your listed topics,
  • accept that you are competent (“this guy knows it”),
  • or at least ask follow-ups that you’re ready to answer.

Practice guidance (as given)

• Practice this technique for your next interviews.
• The video compares repeated practice to magic card tricks:
  • repeated rehearsal makes the process smoother,
  • and improves your ability to control the interview flow.

Speakers / sources featured

• No specific named speakers are provided in the subtitles.
• Content is delivered by an unnamed YouTube narrator/host (“Hello guys… I will tell you…”).