Helping a Software Engineer Get an Offer in Under 90 Days

Business/Execution Summary (“Job Search Playbook”)

A coach advises a laid-off software engineer (2 years experience; ~9 months unemployed) on a practical job-search strategy focused on:

• Getting interviews
• Passing technical rounds under competitive conditions

Core theme: Fix the funnel (resume + recruiter + applications + location signaling), then run an execution sprint on the exact interview skills (especially DSA/LeetCode), and use resume-boosting projects to remove resume-gap risk.

---

Key Problems Identified

• No interview momentum / too few interview loops

  • Roughly ~10 applications/interview attempts across ~3 companies
  • Multiple final-stage salary rejections

• LeetCode/DSA skill gap + low practice volume

  • Candidate doing ~1 LeetCode problem/day
  • Coach believes target should be 3–5/day for faster catch-up
  • Candidate finds it hard to regain progress after pauses (long gaps reduce recall)

• Resume “gap” signaling risk

  • Risk after 9 months unemployed

• Potential recruiter/resume under-optimization

  • Coach step: have a recruiter/experienced reviewer audit LinkedIn + resume
  • Suggested recruiter review cost: ~$100

• Company-fit / interview format mismatch

  • Candidate targeted large tech brands with LeetCode-style screens
  • Coach suggests alternatives that don’t require it (or require less DSA)

---

Framework / Process / Playbook (Action Steps)

1. Get a professional resume/LinkedIn review

   • Pay a recruiter (coach suggests ~$100) to review resume + LinkedIn.

2. Fix LinkedIn location targeting signal

   • Change LinkedIn location to NYC or Bay Area to reduce recruiter friction around relocation.

3. Eliminate resume-gap exposure

   • Use an “experience-through-build” tactic:
     • Build AI tools/projects for specific local audiences (e.g., law firms via your network).
     • Present it as contractor-style real work to avoid “9-month gap” signaling.
     • Include outputs such as:
       • A pinned LinkedIn project/app
       • A named referrer/team member

4. Apply strategically to the right interview style

   • If LeetCode is too hard for your current timeline:
     • Target companies/startups that don’t ask LeetCode (or have fewer DSA rounds).
   • If applying to companies that require DSA (Amazon/Google-like):
     • Increase DSA practice volume.

5. Interview execution sprint

   • Use a “shots-on-goal” mindset: apply + interview repeatedly until the right combination lands.
   • Practice intensity upgrade:
     • Coach says minimum should be 3 problems/day
     • Ideally 5/day, assuming 12 hours/day available while unemployed.

6. (Tactical) Company-specific DSA preparation

   • If time is short (e.g., interview in days), optionally look up company-style problems.
   • Coach calls it a “trick,” but not guaranteed.

---

Concrete Examples / Case Notes

• Walmart

  • Felt strong internally
  • Hiring manager pushed candidate to another role
  • Ultimately no callback/feedback

• Amazon

  • Did an OA
  • Rejected after AI-assisted coding issues (buggy AI)
  • Practiced at least ~6 problems + 6 bug fixes

• Other companies mentioned

  • Freddie Mac
  • Paragon
  • Prior employment at JPMorgan Chase

• Candidate progress plan (in progress)

  • LeetCode: ~1/day
  • Also using algorithm “live sessions” / platforms (including a daily question practice group)
  • System design: candidate reports experience (many times)

• Near-term interviews

  • JP Morgan Chase: interview on August 3
    • Expectation: Lead Code + System Design + Behavioral across ~3 rounds
  • Capital One: similar structure
    • Lead Code + System Design + Behavioral/DS

---

Key Metrics / KPIs Mentioned (and Coach Targets)

• Experience: ~2 years
• Unemployment duration: ~9 months

• Interview/application attempts: ~10 from ~3 companies (approximate scale)

• DSA practice (candidate)

  • Previously solved: ~300 problems (candidate estimate)
  • Current pace: ~1 LeetCode problem/day

• DSA practice targets (coach)

  • Ramp to 3 problems/day minimum
  • Possibly 5/day during unemployment

• Performance outcome references

  • Some final-stage rejections (salary decision)
  • “Offer from one company,” but stalled due to perceived issues in the offer letter / recruiter responsiveness

---

Actionable Recommendations (Condensed)

• Increase DSA output for short-term deadlines

  • If interviews are within days/weeks, switch from 1/day to 3–5/day
  • Use a re-solve previously solved problems strategy to rebuild speed/recall

• Avoid being blocked by the wrong companies

  • If LeetCode is the blocker, target firms/startups that don’t do it

• Convert unemployment into productive proof

  • Build AI tools for real users/organizations
  • This reduces resume-gap penalty and creates strong interview talking points

• Optimize the funnel first

  • Recruiter resume audit + LinkedIn location signal + constant applications (“keep kicking the ball”)

---

Presenters / Sources

• Raymond (referred to as the coach in the video)
  • Mentions a free roadmap at: school.com/raymond
  • Also refers to “Ray’s roadmap”