Summary

  • Build a resume machines can read and humans can trust.
  • Ship small products that prove outcomes.
  • Maintain a steady networking cadence.
  • Run a tight prescreen, then go deep on JS/FE fundamentals.
  • Always give the company a clear reason to want you.

Resume strategy (plain text + metrics)

  • Write in plain text structure that parses well in ATS.
  • Use impact bullets with metrics: Action → result (%/time/$) → scope.
  • Sections:
    • Experience
    • Technical skills
    • Achievements
    • Leadership & collaboration
    • Education
    • Continuous learning & certifications
    • Recognition & awards
    • Diverse projects
    • Volunteering & leadership
    • Publications
  • Rule: “Machine reads, human is convinced.” Output must quantify delivered results.

Impact bullet template

  • Improved X by Y% by doing Z for N users/systems.
  • Prefer numbers and verbs. Avoid fluff.

Portfolio/product plan

  • Ship standing products that show you can deliver end-to-end.
  • Prefer full-stack pieces that can run in prod and be read.
  • “Zero-to-one” helps you calibrate direction; mentor someone if useful.
  • Keep proving you can do new work in the EU context.

Networking cadence

  • Contact your network at least 2× every 15 days.
  • Ask “How can I help?”. Offer a like, a forward, a useful intro.
  • Follow the resume sections list above when updating your profile.
  • Find the best day/time to reach each contact.

Conversation style

  • Start like therapy: get people to talk about themselves first.
  • Then position your value with proof and metrics.

Interview funnel

Candidate positioning questions

  • Which roles does this person fit?
  • What experience is required?
  • Any bias in the selection process?

Recruiter screen questions they ask you

  1. What do you do currently?
  2. Recent projects?
  3. What are you looking for next?
  4. Why this company?
  5. Availability for next steps?

Goal: Give a clear reason they should want you.

Questions you ask them (prescreen)

  1. Steps in the process and typical timeline?
  2. Team size?
  3. Which team is hiring?
  4. Culture?
  5. Competitors?
  6. Example projects you would work on?

Reference slides: Prescreen deck

JS/FE prescreen topics

  • const vs let vs var
  • Prototypal inheritance
  • Meaning of this
  • DOM data structure
  • Stack vs Queue; create both in JS
  • Detect if an image loaded
  • call() vs apply()
  • Event delegation and performance trade-offs
  • Web Workers: what/when

ATS and preparation notes

  • Use ATS feedback to refine resume structure and keywords.
  • Research each interviewer/instructor beforehand.
  • Note: HR may use AI signals to gauge engagement and sentiment. Be consistent.
  • Keep a readiness matrix for gaps and practice plans.

Actions this week

  • Convert resume to plain-text ATS-friendly format with metric bullets.
  • Publish one small product that runs end-to-end.
  • Schedule two networking touches; log best day/time per contact.
  • Run a mock interview with a bot to self-assess.
  • Drill the JS/FE list above; write one code sample per topic.

Templates

Plain-text resume skeleton


Name — City, Country | email | linkedIn | github  
SUMMARY: Senior Frontend/Full-stack delivering X for Y users. Focus: React/TS/Node/AWS/GCP.

EXPERIENCE  
Company — Role — Dates  
• Action → Result with metric (%, ms, $, users, reliability).  
• Action → Result with metric.  
• Action → Result with metric.

PROJECTS  
• Name — 1 line of outcome and tech.

SKILLS  
• Languages, Frameworks, Cloud, Tools.

EDUCATION  
• Degree or relevant coursework.

CERTIFICATIONS  
• Name — Year

AWARDS / PUBLICATIONS / VOLUNTEERING  
• Item — brief impact + metric.

Prescreen one-pager (you → them)

  • Role fit + why you care.
  • Top 3 outcomes you can deliver.
  • 2 proof bullets with numbers.
  • Availability for next steps.

Outreach cadence checklist

  • Help first: ask a specific way to help.
  • Engage: like/share/comment meaningfully.
  • Follow-up: log responses and schedule the next touch.

Final reminders

  • Measure everything. Speak in outcomes.
  • Keep it ordered. Remove anything that does not prove value.