it only takes 90 days to get a job offer

Main Ideas / Concepts

• Getting a job offer has “three steps,” and most people get stuck before they even reach interviews.
• The biggest bottleneck isn’t spending time “learning.” It’s not building the right kind of experience and packaging it correctly (resume/LinkedIn), so recruiters and interviewers take you seriously.
• Real project experience can be built quickly (the speaker argues 1–2 weeks, not months) by doing practical work for someone else and using AI to accelerate development.
• A strong job search funnel requires iteration:
  • experience → resume/LinkedIn → interview pipeline → recruiter screens → on-site rounds
• College-style “study” and random project planning are inefficient for interview readiness. The speaker contrasts:
  • “reading the internet” for months
  • vs. building for another person (freelance-style work) to create credible experience for recruiters.
• AI can speed up project creation, but you still must practice coding by hand and be able to design/test systems. AI-only knowledge is not sufficient for interviews.
• The speaker emphasizes urgency: delays cost time and money, and doing “nothing” while waiting is the core problem.

Methodology / Step-by-Step Instructions

1) Get interviews by building the right skills + evidence

• Track interviews (implied operational step: keep a record of recruiter/interview progress).
• Learn skills that are not taught in college and that specifically help you attract interviews.
• Build “actual experience”:
  • Not just personal projects or coursework
  • Instead: build something for another person or organization (e.g., a website, server, AI automation)
• How to generate project experience quickly
  • Find someone (friend/family/small business) with an idea/need.
  • Ask what they want built.
  • Use AI tooling to help you figure out how to build it.
  • Implement the project, then deploy and test it to confirm it works.
  • Target timeframe claimed by the speaker: about 1 week, sometimes 1–2 weeks (not months).

2) Convert recruiter screens into progression

• Recruiters screen for baseline competence.
• Don’t sound “junior/intern” to the recruiter (speaker implies: be confident and demonstrate credible experience).
• Your resume/LinkedIn and background must support that.

3) Convert on-site interviews into an offer

On-site typically includes multiple types of rounds. Common ones highlighted by the speaker:

• Engineer interaction round
  • You must impress another actual engineer, not just the recruiter.
• Live coding round
  • You may be asked to code in front of them.
  • Performing well here is presented as a key path to the offer.
• System design and/or other formats
  • Possible rounds include:
    • system design
    • take-home project followed by discussion

Packaging: Resume / LinkedIn + Feedback Options

• Once you have experience, you should build/upgrade your resume and LinkedIn using that experience.
• Ways to improve them:
  • Ask recruiters to review your resume/LinkedIn
  • Ask friends for review (speaker notes friends may not know what matters)
  • Use expert help or watch many YouTube videos (framed as a faster route)
• Claimed time cost:
  • About a week (or 2) to get a “good resume,” not months.

Job Search Funnel / Expectations (As Stated)

• Based on the speaker’s rough funnel:
  • 100 job applications → about 1 interview (typical)
  • Worst-case if you do it poorly: apply to ~400 → ~1 interview
• The steps are interconnected:
  • Experience improves resume/LinkedIn → which improves interviews → which enables recruiter screens → which enables on-site performance.

Role of AI (and Required Limitations)

• AI can help build projects quickly and can be used throughout the process.
• But interview success still requires:
  • coding by hand
  • system design knowledge
  • operating/testing understanding
• Purpose of AI on the resume:
  • You can truthfully claim you built using AI tools,
  • but you must also be able to perform without relying on AI during interviews.

Coaching / Program Claims (Speaker’s Offer)

• The speaker offers help to software engineers aiming for jobs under 90 days.
• Example outcomes cited:
  • Helped Andrew pass interviews and get a $255,000 job in under 22 days
  • Helped M pass a Google on-site (details referenced)
  • Helped another person get two job offers totaling $160,000
• Claimed system structure:
  • Fix resume
  • Fix coding abilities / get interview-ready
  • Fix behavioral interviews
  • Provide a “core roadmap/framework”

Speakers / Sources Featured

• Raymond (the main speaker; referenced by name multiple times)
• AI tools mentioned as examples: “GBT” (likely ChatGPT / generic GPT) and “AI” (no specific brand/source beyond that)
• YouTube (referenced as a source of free information)
• Recruiters (as part of the hiring process)