Resume & LinkedIn

The reality:
  1. ATS parses your resume → filters for keywords, format, years of experience
  2. Recruiter scans (6 sec) → "is there a relevant signal?"
  3. Hiring Manager reviews → "can I picture this person doing the job?"
  4. Loop → are the signals specific and impressive?

┌─────────────────────────────────────────────────────────────────┐
│  FULL NAME                                                       │
│  email@gmail.com · +91 XXXXX XXXXX · github.com/username        │
│  linkedin.com/in/username · Portfolio: yoursite.com             │
├─────────────────────────────────────────────────────────────────┤
│  EDUCATION                                                       │
│  Degree, Major — University Name              YYYY – YYYY        │
│  GPA: X.X/10 (include if >7.5/10 or >3.5/4.0)                  │
├─────────────────────────────────────────────────────────────────┤
│  EXPERIENCE                                                      │
│  Job Title · Company Name                    Month YYYY – Present│
│  • Bullet 1 (impact-first formula — see below)                   │
│  • Bullet 2                                                      │
│  • Bullet 3                                                      │
├─────────────────────────────────────────────────────────────────┤
│  PROJECTS (only if adding value over experience)                 │
│  Project Name | Tech Stack Used              [GitHub] [Live]     │
│  • Impact bullet                                                 │
├─────────────────────────────────────────────────────────────────┤
│  SKILLS                                                          │
│  Languages: Python, Java, JavaScript, TypeScript, C++            │
│  Frameworks: React, Next.js, Spring Boot, Node.js, FastAPI       │
│  Databases: PostgreSQL, MongoDB, Redis                           │
│  Tools: Docker, Kubernetes, AWS, Git, CI/CD (GitHub Actions)    │
└─────────────────────────────────────────────────────────────────┘

Formula: Accomplished [X] as measured by [Y] by doing [Z]

Or: [Strong Verb] + [What you built/did] + [Impact/Result] + [Scale/Context]

❌ Weak: "Worked on backend APIs for the e-commerce platform"
✅ Strong: "Designed and deployed 12 RESTful APIs serving 2M daily requests,
            reducing average response time by 40% via Redis caching"

❌ Weak: "Improved database performance"
✅ Strong: "Optimized 8 critical PostgreSQL queries with composite indexes,
            reducing P99 latency from 2.3s to 180ms for the checkout flow"

❌ Weak: "Built a microservices architecture"
✅ Strong: "Decomposed monolithic Python service into 6 microservices using
            Docker + Kubernetes; cut deployment time from 45 min to 8 min"

❌ Weak: "Developed frontend features"
✅ Strong: "Rebuilt product listing page in React, reducing Largest Contentful
            Paint by 58% (3.2s → 1.3s) and lifting conversion rate 12%"

Engineered, Architected, Designed, Built, Developed, Implemented,
Optimized, Refactored, Reduced, Improved, Increased, Accelerated,
Led, Mentored, Drove, Collaborated, Delivered, Shipped, Launched,
Automated, Deployed, Migrated, Scaled, Integrated, Debugged

✅ Use standard section headings: EXPERIENCE, EDUCATION, SKILLS, PROJECTS
✅ Use a simple, single-column layout (ATS struggles with tables/columns)
✅ Save as PDF (preserves formatting) or plain text DOCX if required
✅ Mirror keywords from the job description (not keyword stuffing — genuine use)
✅ Spell out abbreviations once: "Kubernetes (K8s)"
✅ Use standard date formats: "Jan 2023 – Present" or "2023 – Present"

❌ No graphics, logos, or icons in the header
❌ No tables for layout (ATS reads them incorrectly)
❌ No headers/footers (ATS often skips these)
❌ No text boxes or text in shapes

❌ Weak: "Software Engineer at TCS"
✅ Strong: "Software Engineer | Full-Stack (React · Node.js · AWS) | Open to SDE-2 roles"
✅ Strong: "Backend Engineer | Java · Spring Boot · Microservices | Prev: Razorpay · BITS Pilani"

Hook (visible without "see more"):
  "I build backend systems that handle millions of requests. Currently at XYZ,
   where I led migration to microservices cutting infrastructure cost by 35%."

Then expand:
  - What you're good at (specific technologies and domains)
  - What you're looking for (optional, if actively searching)
  - 2-3 highlight achievements
  - Close with: "Feel free to reach out: email@gmail.com"

Resume success funnel:
  Applied 100 →
  ATS pass ~40 →
  Recruiter screen ~15 →
  Hiring manager review ~8 →
  Phone screen ~5 →
  Onsite ~3 →
  Offer ~1

The funnel is brutal. Short-circuit it:

1. Employee Referral — the single most powerful lever
   → Connect with engineers at target companies on LinkedIn
   → Ask for a coffee chat (not a referral directly — build the relationship first)
   → After the conversation, ask: "Would you be comfortable referring me?"
   → Referred candidates skip the ATS and go straight to recruiter review

2. Cold outreach to recruiters
   → "Hi [Name], I applied for [Role ID] at [Company].
     I'm a backend engineer with 3 years in fintech (Node.js, PostgreSQL).
     Happy to share more context if helpful. Thanks!"

3. Apply on the company careers page (not LinkedIn Easy Apply)
   → Less competition, more fields to stand out