Tech Resume and Portfolio Guide for 2026

Your resume has 7.4 seconds to make an impression. Make every line count.

How AI Resume Screening Works in 2026

Before a human recruiter ever sees your resume, it passes through an Applicant Tracking System. In 2026, these systems are far more sophisticated than the keyword-matching tools of five years ago. Modern ATS platforms like Greenhouse, Lever, Workday, and iCIMS use AI-powered semantic analysis to parse, rank, and filter candidates.

The numbers are stark: 75% of resumes are filtered out before a human ever reads them. At large companies like Amazon, Google, and Microsoft, a single job posting can attract 1,000+ applications. The ATS is the gatekeeper, and understanding how it works is not optional.

What the ATS Actually Does

1. Parsing - The system extracts text from your resume file and maps it into structured fields: name, contact info, work history, education, skills. Fancy formatting, tables, multi-column layouts, and embedded images break this step.
2. Keyword matching - The ATS compares your resume content against the job description. In 2026, this goes beyond exact matches. Semantic analysis understands that "Kubernetes" and "K8s" are the same thing, and that "CI/CD pipelines" relates to "continuous integration."
3. Scoring and ranking - Each resume gets a relevance score. Recruiters typically only review the top 20-30 candidates. If your score is below the threshold, your resume goes into a database and is never seen.
4. AI screening layer - Many companies now add an AI layer on top of the ATS that evaluates career progression, job tenure patterns, and skills depth. Some use large language models to summarize candidate profiles for recruiters.

File Format Matters

Submit your resume as a PDF unless the job posting specifically requests DOCX. PDF preserves formatting across systems and is universally parseable by modern ATS platforms. Avoid image-based PDFs (scanned documents) since the ATS cannot extract text from them. If you built your resume in a design tool like Canva or Figma, export it as a text-based PDF, not a flattened image.

Resume Format - One Page vs Two Pages

The one-page resume rule is one of the most persistent myths in tech hiring. Here is the actual guidance based on experience level:

Recruiters spend an average of 7.4 seconds on an initial resume scan. That is not enough time to read two pages. It is barely enough to scan one. Your resume's job is not to tell your life story. It is to get you an interview.

Layout and Typography

• Single column layout - Two-column resumes look nice but confuse ATS parsers. Stick with a single column.
• Standard section headers - Use "Experience," "Education," "Skills," and "Projects." Creative headers like "Where I've Made Impact" confuse both ATS and humans.
• 10-12pt font - Anything smaller is hard to read. Anything larger wastes space.
• 0.5-1 inch margins - Do not shrink margins below 0.5 inches to cram more content. It looks desperate and prints poorly.
• Consistent formatting - If you bold one job title, bold all of them. If you use bullet points in one role, use them everywhere.

What Goes on Page One

If your resume is two pages, page one must stand alone. Many recruiters only read the first page during initial screening. Front-load it with:

• Contact information and professional summary
• Skills matrix (tailored to the job posting)
• Your most recent and most relevant role with your strongest 3-5 bullets

Page two can include earlier roles, education, certifications, and additional projects. Never put your most impressive achievements on page two.

Resume Templates and Tools

You do not need a fancy template. In fact, the simpler the better for ATS compatibility. Here are reliable options:

• Google Docs - Free, clean templates that export to PDF. The "Swiss" and "Spearmint" templates are ATS-friendly.
• LaTeX (with moderncv or altacv) - If you are comfortable with LaTeX, these produce clean, professional resumes. Overleaf has free templates. Be careful with multi-column LaTeX templates though, as some break ATS parsing.
• Reactive Resume - An open-source resume builder (rxresu.me) that produces ATS-friendly output with a clean interface.
• Plain text first - Write your resume content in plain text before adding any formatting. This forces you to focus on the words, not the design. If your resume does not read well as plain text, no amount of formatting will save it.

ATS Optimization Checklist

Think of ATS optimization as translation. You are taking your real experience and expressing it in the language the system expects. This is not about lying or exaggerating. It is about removing friction between your qualifications and the algorithm.

Formatting Rules for ATS

• Use a single-column layout with no tables, text boxes, or graphics
• Use standard section headers: Experience, Education, Skills, Projects, Certifications
• Do not put critical information in headers or footers (many ATS systems skip these)
• Avoid special characters, icons, and emojis in section headers
• Use standard bullet points (round dots), not custom symbols
• Include your full name, email, phone, LinkedIn URL, and city/state at the top
• Save as PDF with selectable text (not a scanned image)
• Name your file FirstName-LastName-Resume.pdf (not "resume_final_v3.pdf")

Keyword Strategy

• Match exact terms - If the posting says "Amazon Web Services (AWS)," include both the full name and the acronym
• Include tool versions - "Python 3.11" is more specific than "Python" and signals current knowledge
• Use both spelled-out and abbreviated forms - "Continuous Integration/Continuous Deployment (CI/CD)"
• Mirror the job level language - If the posting says "architected," use "architected" instead of "built"
• Include certifications by full name - "AWS Certified Solutions Architect - Professional" not just "AWS SA Pro"

The STAR/XYZ Bullet Method

The single biggest difference between a resume that gets interviews and one that does not is the quality of the bullet points. Most engineers write duty-based bullets that describe what they were responsible for. Hiring managers want impact-based bullets that show what you accomplished.

The Framework

STAR stands for Situation, Task, Action, Result. XYZ (used at Google) follows the pattern: "Accomplished [X] as measured by [Y], by doing [Z]." Both frameworks force you to quantify your impact.

The formula for a strong bullet point:

Before and After Examples

Where to Find Your Numbers

Engineers often say "I don't have metrics." You do. You just have not looked for them yet.

• Speed improvements - Build times, deployment frequency, page load times, query response times
• Cost savings - Cloud bills before and after optimization, reduced infrastructure spend
• Scale - Requests per second, daily active users, data volume processed
• Reliability - Uptime percentages, incident reduction, MTTR improvements
• Team impact - Engineers onboarded, PRs reviewed, documentation pages written
• Business outcomes - Revenue impact, customer churn reduction, conversion rate changes

If you genuinely cannot find exact numbers, use reasonable estimates with qualifiers: "Reduced API response time by approximately 60%" is still far better than "Improved API performance."

Technical Resume Sections That Matter

Every technical resume needs these sections, in this order. Deviate from this structure at your own risk.

1. Contact Header

Name, email, phone, city/state (no full address), LinkedIn URL, GitHub URL, and portfolio URL if you have one. That is it. No photo, no "objective statement," no personal pronouns.

2. Professional Summary (Optional but Recommended for Senior+)

Two to three sentences maximum. State your specialty, years of experience, and one or two headline achievements. Skip this section entirely if you are junior. A bad summary is worse than no summary.

Good: "Senior DevOps Engineer with 8 years of experience building and scaling cloud infrastructure on AWS. Led migration of 40+ services to Kubernetes, reducing infrastructure costs by $180K annually. AWS Solutions Architect Professional and CKA certified."

Bad: "Passionate and motivated team player seeking a challenging role where I can leverage my skills and grow professionally."

3. Skills Matrix

Group your technical skills into categories. This section is critical for ATS keyword matching and for recruiters who scan for specific technologies.

Rules for the skills matrix:

• Only list technologies you can discuss in an interview. If you cannot answer basic questions about it, remove it.
• Put the most relevant skills first in each category
• Include cloud service specifics (not just "AWS" but "AWS Lambda, ECS, S3")
• Update this section for every application to match the job posting
• Do not list soft skills here. "Communication" and "teamwork" do not belong in a skills matrix.

4. Professional Experience

List your most recent 2-3 roles with 3-5 STAR/XYZ bullet points each. Include company name, your title, location, and dates (month/year format). For each role, lead with your strongest achievement, not your first responsibility.

5. Projects (Critical for Junior Engineers)

If you have fewer than 3 years of experience, this section can be more important than your work history. List 2-3 significant projects with:

• Project name and one-line description
• Technologies used
• Your specific contribution (not "we built" but "I implemented")
• Link to live demo or GitHub repository
• Quantified outcome if possible (users, performance metrics, downloads)

6. Certifications

List relevant certifications with the full official name and year obtained. Certifications carry real weight in tech hiring. An AWS Solutions Architect or CKA certification can be the tiebreaker between two otherwise equal candidates.

7. Education

Degree, school, graduation year. That is all you need. Do not list GPA unless it is above 3.5 and you graduated within the last 2 years. Do not list coursework unless you are a new graduate applying to your first role.

Resume Strategies by Role

A generic resume sent to every job posting will underperform a targeted resume every time. Here is what hiring managers look for in specific roles.

DevOps Engineer

Hiring managers want to see infrastructure automation, CI/CD pipeline ownership, and incident response experience. Lead with metrics around deployment frequency, MTTR, and infrastructure cost optimization. Mention specific tools: Terraform, Ansible, Docker, Kubernetes, and your CI/CD platform of choice. If you have on-call experience, include it. For a deeper look at the DevOps career path, see our DevOps and SRE career guide.

• Emphasize: IaC, CI/CD, containerization, cloud platforms, monitoring
• Key metrics: deployment frequency, lead time for changes, MTTR, change failure rate (the DORA metrics)
• Differentiator: experience with platform engineering, developer experience (DevEx), or internal tooling

Site Reliability Engineer (SRE)

SRE resumes should emphasize reliability, observability, and incident management. Highlight SLO/SLI definitions, error budget management, and postmortem culture. Include on-call rotation experience and any toil reduction projects.

• Emphasize: SLOs/SLIs, incident response, capacity planning, chaos engineering
• Key metrics: uptime percentages, MTTD, MTTR, incident frequency reduction
• Differentiator: experience with chaos engineering tools (Gremlin, Litmus), SRE book principles in practice

Full-Stack Developer

Show depth in both frontend and backend. Hiring managers are skeptical of "full-stack" claims, so prove it with specific projects that span the entire stack. Include framework experience (React, Next.js, Vue), API design, database work, and deployment.

• Emphasize: end-to-end feature delivery, API design, frontend performance, database optimization
• Key metrics: page load times, Core Web Vitals, API response times, user-facing feature delivery
• Differentiator: accessibility compliance, performance optimization, design system contributions

Data Engineer

Data engineering resumes should highlight pipeline architecture, data quality, and scale. Mention specific tools: Spark, Airflow, dbt, Snowflake, BigQuery, Kafka. Quantify the volume of data you process daily and the business decisions your pipelines enable.

• Emphasize: ETL/ELT pipelines, data modeling, data quality frameworks, streaming vs batch
• Key metrics: data volume processed, pipeline reliability, query performance, cost per TB
• Differentiator: real-time streaming experience, data mesh architecture, ML feature stores

AI/ML Engineer

This is the hottest market in 2026, and resumes need to reflect current skills. Mention specific model architectures, training frameworks (PyTorch, JAX), and deployment patterns (model serving, A/B testing, monitoring for drift). Include any published research, Kaggle rankings, or open-source model contributions.

• Emphasize: model training and fine-tuning, MLOps, experiment tracking, model serving
• Key metrics: model accuracy improvements, inference latency, training cost optimization, A/B test results
• Differentiator: RAG implementation experience, LLM fine-tuning, responsible AI practices, production ML at scale

10 Resume Killers to Avoid

These mistakes will get your resume rejected faster than any missing keyword. Each one is based on patterns recruiters and hiring managers consistently flag.

1. Typos and grammatical errors - A single typo signals carelessness. If you cannot proofread a one-page document, why would anyone trust you with production code? Run your resume through a spell checker, then have a human read it.
2. Duty-based bullet points - "Responsible for managing servers" tells the reader nothing about your impact. Every bullet should answer: "So what? What changed because of my work?" Use the STAR/XYZ method described above.
3. Listing every technology you have ever touched - A skills section with 50+ technologies screams "I copied this from job postings." List only tools you can discuss confidently in an interview. Quality over quantity.
4. No quantified achievements - Numbers are the currency of resumes. "Improved performance" means nothing. "Reduced p95 latency from 800ms to 120ms" means everything. If you have zero numbers on your resume, it will lose to one that does.
5. Using a creative or non-standard format - Infographic resumes, multi-column layouts, and heavy graphics break ATS parsing. They also annoy recruiters who need to scan quickly. Save the creativity for your portfolio site.
6. Including an objective statement - "Seeking a challenging position where I can grow" wastes prime resume real estate. Replace it with a professional summary (senior+) or remove it entirely (junior).
7. Listing irrelevant work experience - Your summer job at a restaurant does not belong on a senior engineer's resume. If a role is not relevant to the position you are applying for, cut it. The exception: if it is your only work experience, reframe the bullets to highlight transferable skills (problem-solving, customer interaction, working under pressure).
8. Inconsistent date formatting - Mixing "Jan 2024" with "2023-06" with "June 2022" looks sloppy. Pick one format and stick with it. "Month Year" (e.g., "Jan 2024") is the standard.
9. Lying or exaggerating - Inflating your title, claiming you "led" a project you contributed to, or listing technologies you used once in a tutorial. Background checks catch title inflation. Technical interviews catch skill exaggeration. The consequences range from rescinded offers to industry reputation damage.
10. Sending the same resume to every job - This is the most common mistake and the easiest to fix. Tailor your skills section and bullet point emphasis to each job posting. You do not need to rewrite the entire resume. Adjust the top third to mirror the posting's priorities.

Portfolio Websites That Get Callbacks

A portfolio website is your chance to show, not just tell. For frontend and full-stack developers, the portfolio itself is a work sample. For backend engineers, DevOps, and data engineers, it is a place to demonstrate communication skills and project depth that a resume cannot capture.

What to Include

• About section - Two to three sentences about who you are and what you specialize in. No life story.
• 3-5 featured projects - Each with a description, your role, technologies used, challenges solved, and a link to the live project or repository. Screenshots or short demo videos add significant value.
• Blog or writing samples - Technical writing demonstrates depth of understanding. Even 3-4 well-written posts about problems you solved can set you apart from candidates who only have a resume.
• Contact information - Make it easy for recruiters to reach you. Email and LinkedIn at minimum.
• Resume download - A PDF download link so recruiters can grab your resume directly.

What to Skip

• Testimonials from friends or classmates (they carry no weight)
• A skills section with progress bars (what does "75% Python" even mean?)
• Animations that delay content loading
• Stock photos or generic placeholder content
• A "services" page unless you are freelancing

Technical Requirements

Your portfolio is a live code sample. Treat it like production code.

• Performance - Lighthouse score above 90. If your portfolio loads slowly, it undermines your credibility as an engineer.
• Accessibility - Semantic HTML, proper heading hierarchy, alt text on images, keyboard navigation. This is not optional.
• Responsive design - It must work on mobile. Recruiters often browse on phones.
• HTTPS - No excuses. Free certificates are available from Let's Encrypt, and every major hosting platform supports them.
• Custom domain - yourname.dev or yourname.com looks more professional than username.github.io

Hosting Options

If you are applying for cloud or DevOps roles, hosting your portfolio on AWS S3 with CloudFront, a custom domain, and infrastructure defined in Terraform or CloudFormation is itself a portfolio project. It demonstrates exactly the skills hiring managers want to see.

GitHub Portfolio Optimization

Your GitHub profile is your second resume. Many hiring managers check it before or after reading your resume. A neglected GitHub with empty repos and no activity sends the wrong signal. Here is how to make it work for you.

Profile Essentials

• Professional photo - Same one you use on LinkedIn. Consistency builds recognition.
• Bio - One line about your specialty. "DevOps Engineer | AWS | Kubernetes | Terraform" is better than blank.
• Profile README - Create a repository named after your username with a README.md. This appears on your profile page. Use it to highlight your top projects, current focus, and how to reach you.
• Pinned repositories - Pin your 6 best repositories. These are the first things visitors see. Choose projects that demonstrate range and depth.

Repository Quality Over Quantity

Six well-documented repositories beat sixty abandoned ones. For each pinned project:

• README - Every pinned repo needs a thorough README with: project description, problem it solves, architecture overview, setup instructions, screenshots or demo GIF, and technologies used.
• Clean commit history - Meaningful commit messages, not "fix stuff" or "asdfgh." Squash messy commits before making repos public.
• Active maintenance - Repos with recent commits signal ongoing engagement. Even small updates (dependency bumps, documentation improvements) keep the contribution graph green.
• Issues and project boards - Using GitHub Issues and Projects on your personal repos shows you understand software development workflows, not just coding.
• CI/CD - Adding GitHub Actions for testing, linting, or deployment to a personal project demonstrates DevOps awareness that most candidates lack.

Contribution Graph

The green squares matter less than people think, but a completely empty graph raises questions. Consistent activity (even a few commits per week) is better than intense bursts followed by months of silence. Contributing to open-source projects is the highest-signal activity on GitHub because it shows you can work with other people's code, follow contribution guidelines, and communicate through pull requests.

Project Ideas That Impress Hiring Managers

If you are not sure what to build for your GitHub portfolio, here are project ideas organized by role that demonstrate real engineering skills rather than tutorial follow-alongs:

DevOps/SRE projects:

• A Terraform module library that provisions a complete AWS environment (VPC, ECS cluster, RDS, monitoring) with documentation and examples
• A Kubernetes operator written in Go that automates a common operational task like certificate rotation, database backups, or canary deployments
• An observability pipeline that collects metrics from a sample application, ships them to Prometheus and Grafana, and includes alerting rules with runbooks
• A CI/CD pipeline template repository with GitHub Actions workflows for multiple languages, including security scanning, testing, and deployment stages

Full-stack projects:

• A real-time collaborative application (document editor, kanban board, or chat) using WebSockets with proper authentication and database persistence
• An API with rate limiting, caching, pagination, authentication, and comprehensive test coverage, deployed with infrastructure as code
• A progressive web app with offline support, push notifications, and accessibility compliance that scores 95+ on Lighthouse

Data engineering projects:

• An end-to-end data pipeline that ingests data from a public API, transforms it with dbt, loads it into a warehouse, and serves a dashboard
• A streaming data processor using Kafka or Kinesis that handles real-time events with exactly-once semantics and dead letter queues
• A data quality framework that validates incoming data against defined schemas and generates automated reports on data freshness and completeness

AI/ML projects:

• A RAG (Retrieval-Augmented Generation) application with a custom knowledge base, vector store, and evaluation metrics for retrieval quality
• A model serving API with A/B testing, monitoring for data drift, and automated retraining triggers
• A fine-tuned LLM for a specific domain task with documented training methodology, evaluation benchmarks, and a comparison against the base model

The key differentiator in all of these is production-readiness. Anyone can build a to-do app. Few candidates build projects with proper error handling, logging, testing, CI/CD, documentation, and deployment automation. That gap is your opportunity.

Cover Letters in 2026

The cover letter is not dead, but it has changed. Most tech companies do not require one, and many recruiters admit they do not read them. However, in specific situations, a well-written cover letter can be the difference between a callback and silence.

When to Write One

• The job posting explicitly asks for one
• You are making a career change and need to explain the transition
• You have a gap in employment that needs context
• You are applying to a small company or startup where the hiring manager reads every application
• You have a personal connection to the company's mission

When to Skip It

• Large company with high-volume hiring (FAANG, large enterprises)
• The application system does not have a field for it
• You would be writing a generic letter you send to every company

The 2026 Cover Letter Format

Three paragraphs, under 250 words total:

1. Hook - Why this specific company and role. Reference something concrete: a recent product launch, a blog post from their engineering team, or a specific technical challenge they face.
2. Value - Your two strongest qualifications mapped directly to the job requirements. Use the same STAR/XYZ format from your resume bullets.
3. Close - Express enthusiasm and availability. No "I look forward to hearing from you" filler. Instead: "I'd welcome the chance to discuss how my experience with [specific skill] could help [specific team goal]."

AI-generated cover letters are obvious to experienced recruiters. Use AI tools to brainstorm or edit, but write the final version in your own voice. A cover letter that sounds like ChatGPT wrote it is worse than no cover letter at all.

LinkedIn Optimization

LinkedIn is where recruiters live. In 2026, over 87% of recruiters use LinkedIn as their primary sourcing tool. Your LinkedIn profile is not a copy of your resume. It is a complementary document that serves a different purpose.

Profile Optimization

• Headline - Do not use your current job title. Use a keyword-rich headline that describes what you do: "Senior DevOps Engineer | AWS | Kubernetes | Terraform | Building Reliable Cloud Infrastructure." LinkedIn search heavily weights the headline field.
• About section - Write in first person. Tell your professional story in 3-5 short paragraphs. Include your specialties, what you are looking for, and how to reach you. This is your elevator pitch, not your resume summary.
• Experience - Mirror your resume bullets but expand them slightly. LinkedIn allows more space, so add context that did not fit on your one-page resume.
• Skills - Add up to 50 skills and get endorsements for your top ones. LinkedIn's algorithm uses skills for search matching.
• Featured section - Pin your portfolio, best blog posts, or notable projects. This section appears prominently on your profile.
• Open to Work - Use the "Open to Work" setting visible only to recruiters (not the green banner). This increases recruiter InMail by 40% according to LinkedIn's own data.

Activity That Gets Noticed

• Share technical insights or lessons learned (not motivational quotes)
• Comment thoughtfully on posts from people at companies you want to work for
• Publish articles about technical topics you are expert in
• Engage with job postings by commenting before applying (this puts your name in front of the hiring manager)

Networking on LinkedIn

Cold connection requests with no message have a low acceptance rate. Always include a personalized note: "Hi [Name], I read your post about [topic] and found it really insightful. I'm also working in [related area] and would love to connect." Keep it under 300 characters and reference something specific.

LinkedIn vs Resume - Key Differences

Getting Recommendations

LinkedIn recommendations are underused and highly effective. A recommendation from a former manager carries more weight than any bullet point you write about yourself. Here is how to get them:

• Write a recommendation for someone first. Most people reciprocate.
• Ask specific people: your direct manager, a tech lead you worked closely with, or a cross-functional partner who saw your impact.
• Make it easy by suggesting what they might mention: "Would you be willing to write a brief recommendation? It would be great if you could mention the [specific project] we worked on together."
• Aim for 3-5 quality recommendations from people in leadership or senior technical roles.

Salary Negotiation

You have optimized your resume, built a portfolio, polished your LinkedIn, and landed an offer. Now comes the part most engineers skip: negotiation. The data is clear and the stakes are high.

55% of candidates accept the first offer without negotiating. Among those who do negotiate, 66% get what they ask for. The average successful negotiation increases total compensation by 10-20%. Over a 30-year career, that single conversation can be worth hundreds of thousands of dollars in compounding salary growth.

Why Engineers Do Not Negotiate

• Fear of losing the offer - This almost never happens. Companies expect negotiation. Rescinding an offer over a reasonable counter is extremely rare and signals a toxic workplace you should avoid anyway.
• Feeling grateful - Gratitude is appropriate. Leaving money on the table is not. The company budgeted a range for this role. The initial offer is rarely the top of that range.
• Not knowing how - Negotiation is a learnable skill, not an innate talent. The framework below works.

The Negotiation Framework

1. Get the offer in writing - Never negotiate verbally. Ask for the complete offer details in writing: base salary, equity/RSUs, signing bonus, annual bonus target, benefits, PTO, and remote work policy.
2. Research the market - Use Levels.fyi, Glassdoor, Blind, and Payscale to understand the compensation range for your role, level, and location. Levels.fyi is the most reliable for tech-specific total compensation data.
3. Ask for time - "Thank you for the offer. I'm very excited about this opportunity. Could I have until [date 3-5 business days out] to review the full package?" This is standard and expected.
4. Counter with data - "Based on my research and conversations with peers in similar roles, the market range for this position is [X-Y]. Given my experience with [specific relevant skill], I'd like to discuss a base salary of [your target]." Always anchor to market data, not personal need.
5. Negotiate the full package - If base salary is firm, negotiate signing bonus, equity, annual bonus, remote work days, professional development budget, or PTO. Companies often have more flexibility on non-salary components.
6. Get the final offer in writing - Once you agree, ask for an updated offer letter reflecting all negotiated terms before you accept.

Compensation Components to Understand

Sample Negotiation Scripts

Having the right words ready makes negotiation less stressful. Here are scripts for common scenarios:

When asked for salary expectations early in the process:

This deflects the question without being evasive. In many states and cities, employers are now legally required to share salary ranges, so this request is reasonable.

When countering a written offer:

When the company says the salary is firm:

Common Negotiation Mistakes

• Negotiating too early - Wait until you have a written offer. Discussing salary before the company has decided they want you weakens your position.
• Giving a number first - Let the company make the first offer whenever possible. The first number anchors the entire negotiation.
• Apologizing for negotiating - Do not say "I hate to ask" or "I know this is awkward." Negotiation is a normal part of the hiring process. Treat it as such.
• Making it personal - "I need more because my rent is high" is not a negotiation argument. "Market data shows this role pays X at comparable companies" is.
• Accepting verbally without written confirmation - Always get the final negotiated terms in an updated offer letter before you resign from your current job.
• Negotiating only base salary - Total compensation includes equity, bonuses, signing bonus, benefits, and perks. A $5K lower base with $20K more in RSUs is a better deal at most public tech companies.

The Compounding Effect

A $10,000 increase in your starting salary does not just affect year one. Future raises, bonuses, and even your next job's offer are often calculated as percentages of your current compensation. Over a 10-year period, that single $10K negotiation can compound into $80,000-$120,000 in additional lifetime earnings. Over a 30-year career, the number exceeds $500,000 when you factor in investment returns on the difference. This is why negotiation is the single highest-ROI activity in your entire job search.

Final Checklist Before You Apply

Before you hit "submit" on any application, run through this checklist:

• ☐ Resume is one page (or two if you have 10+ years of relevant experience)
• ☐ Single-column layout with standard section headers
• ☐ Skills section mirrors the job posting keywords
• ☐ Every bullet point uses the STAR/XYZ format with quantified results
• ☐ No typos, no grammatical errors (have someone else proofread)
• ☐ File saved as FirstName-LastName-Resume.pdf
• ☐ Contact info includes email, phone, LinkedIn, GitHub, and city/state
• ☐ No photos, no graphics, no multi-column layouts
• ☐ Certifications listed with full official names
• ☐ Portfolio website is live, fast, and mobile-friendly
• ☐ GitHub pinned repos have thorough READMEs
• ☐ LinkedIn headline is keyword-optimized (not just your job title)
• ☐ LinkedIn "Open to Work" is enabled for recruiters
• ☐ You have researched the salary range for this role and location
• ☐ You have a negotiation plan ready for when the offer comes