Prep Guides

Resume and Portfolio Prep Guide for Tech Roles

By Editorial Team — reviewed for accuracy Published
Last reviewed:

Resumes and portfolios are the typical first signal employers see. Strong resumes get past initial screening; portfolios provide evidence of work for roles where it matters (engineering, design, AI/ML, technical writing). This guide covers resume-and-portfolio preparation for tech roles, grounded in the broader AIEH skills-based-hiring framework.

Who this guide is for

  • Candidates preparing for technical job searches at any seniority level.
  • Career-transition candidates translating prior experience into tech-role-relevant framing.
  • Working engineers updating their resume between job searches.

What resumes actually do

Three functions:

  • Pass automated screening. Many employers use ATS systems with keyword filters. Resumes that don’t match the job posting’s keywords get filtered before human review.
  • Pass initial human screening. Recruiters often spend 10-30 seconds per resume on first pass. The resume needs to communicate fit at scan-speed.
  • Provide context for interviewers. Once you’re scheduled for interviews, the resume informs interviewer expectations and behavioral-interview question selection.

The first function favors keyword-rich resumes; the second favors clear-structure resumes; the third favors specific-evidence resumes. The discipline is producing one resume that serves all three.

Strong resume patterns

Six patterns:

  • Lead with impact, not responsibility. “Reduced page-load p99 from 800ms to 120ms by replacing X with Y” is stronger than “Worked on frontend performance optimization.”
  • Quantify outcomes when honest. Specific metrics signal measurable impact; round numbers are usually fine. Don’t fabricate numbers — they get caught in interviews.
  • Match the job posting’s language. If the posting says “TypeScript” and you’ve used TypeScript, write “TypeScript” not “TS” or “JavaScript with type annotations.” ATS keyword matching is real.
  • Order by relevance, not chronology. Most-relevant experience near the top, even if it’s not your most recent role. Senior candidates with diverse backgrounds often need this.
  • Keep it scannable. Bullet points, consistent formatting, white space. One or two pages depending on seniority — three pages is rarely warranted.
  • Tailor per application or category. A frontend role resume should weight frontend experience differently than a backend resume; a research-leaning company should see research-leaning framing.

Common resume mistakes

Five patterns:

  • Vague accomplishment language. “Helped improve performance” is weaker than specific outcome claims.
  • Listing technologies without depth. A resume listing 30 technologies signals weak depth in any of them.
  • Inconsistent tense. Past roles use past tense; current role uses present tense. Mixing is jarring.
  • Including irrelevant experience. Senior candidates don’t need to include their early-career roles in detail.
  • Spelling or formatting errors. Resumes are pre- filtered; even small errors signal lack of care.

Portfolio considerations

Portfolios serve different purposes for different roles:

  • Engineers. GitHub portfolio with shipped projects; contributions to open-source signal community engagement; README quality of personal projects signals professional habits.
  • Designers. Figma or Behance portfolio with case studies; the case-study writeups matter as much as the visual outputs.
  • AI/ML practitioners. Kaggle competitions, published research, blog posts about projects, GitHub implementations.
  • Technical writers. Published documentation, blog posts, written work samples.

Strong portfolios are curated, not exhaustive. 3-5 strong case studies are stronger than 30 minor projects.

When AI assistance helps resume prep

Three patterns where AI is valuable:

  • Resume editing for clarity. AI is reliable at suggesting cuts and rephrases.
  • Bullet-point restructuring. Translating responsibility-language to impact-language.
  • Cover letter drafting. AI produces reasonable cover letter starting points; the writer refines.

Three patterns where AI is less valuable:

  • Genuine accomplishment claims. Specific outcomes have to come from real experience. AI can fabricate plausible-sounding accomplishments that don’t hold up in interviews.
  • Strategic framing. What experience to emphasize for a specific role requires understanding the role and your career narrative.
  • Cultural-fit calibration. Specific employers have cultural preferences; AI defaults often miss these.

How this maps to AIEH and the skills-based framework

Skills-based hiring (covered in the skills-based hiring evidence overview) is reducing reliance on resumes as primary signal, particularly with portable-credential approaches like AIEH’s Skills Passport. Resumes still matter for initial screening and human-review context, but their relative weight is declining as more direct skill signals become available. Three specific patterns:

  • Portable credentials supplement rather than replace the resume. A candidate with strong portable credentials still benefits from a clean resume that contextualizes the credentials within career narrative.
  • Skills-based language helps ATS matching. ATS systems increasingly parse skills explicitly; resumes that surface skills with canonical-taxonomy-friendly language match better.
  • Cross-employer credential portability reduces resume-pressure. When candidates carry validated capability signals across employers, the resume bears less of the screening load. This produces some flexibility in resume style — focus on narrative arc rather than exhaustive detail.

Resources for deeper study

  • The Tech Resume Inside Out by Gergely Orosz. Practitioner-oriented book on tech-resume writing.
  • Career Cup, levels.fyi resume reviews for community-sourced resume feedback.
  • Specific employer resume guides when available (Google has published resume guidance, e.g.).

LinkedIn profile considerations

Beyond the resume, modern tech hiring substantially uses LinkedIn for sourcing and screening. Strong LinkedIn profiles complement the resume:

  • Headline beyond job title. “Software Engineer at Acme” is the default; “Full-Stack Engineer building developer tools at Acme” provides more searchable context for recruiter sourcing.
  • About section that reads like a story. The About section is more flexible than resume bullets; use it for the narrative arc that bullet-format resume can’t capture.
  • Featured items. LinkedIn allows pinning specific items (articles, posts, project links) to the profile top. Use this for the strongest portfolio pieces.
  • Engagement and activity. LinkedIn algorithm surfaces profiles with recent engagement; profiles that go silent for years drop in recruiter search rankings. Modest sustained engagement (weekly posts or comments) maintains visibility without becoming a full-time activity.
  • Recommendations and endorsements. Recommendations from former managers or peers carry meaningful weight; endorsements have less weight but contribute to skill-search matching.

Cover letter considerations

Cover letters have decreased in importance for tech hiring but remain relevant in specific contexts:

  • Senior roles where context matters. Senior candidates can use cover letters to articulate career narrative and specific role-fit reasoning that resume-bullet-format obscures.
  • Career-transition contexts. Candidates transitioning between specialties or industries benefit from cover letters that bridge the gap explicitly.
  • Mission-driven employers. Some employers ( particularly nonprofits, mission-driven startups, organizations with strong cultural identity) value cover letters as signal that candidates have thought about specific fit.
  • When the prompt asks for one. Some application systems require cover letters; strong candidates treat the requirement as opportunity rather than burden.

For most established tech roles, the cover letter is optional and often not read; the resume and portfolio do most of the screening work. The exceptions above warrant the additional effort.

Common portfolio pitfalls

Five patterns recurring across portfolio-driven roles:

  • Including incomplete or broken projects. Portfolio pieces should work; broken demos signal incomplete follow-through. Reviewers can tell when portfolio items aren’t tested.
  • Outdated projects. Last-updated-three-years-ago projects signal weaker recent activity. Strong candidates curate portfolios to emphasize recent work; older work appears only where it’s exceptional enough to remain relevant.
  • No README or documentation. Strong projects include setup instructions, design decisions, and context about why the project matters. Code-only portfolio items lose context that reviewers need.
  • Quantity over quality. Some candidates include every project they’ve ever shipped; the volume obscures the strongest pieces. Strong portfolios are curated rather than exhaustive.
  • No clear case-study narrative. Visual designers particularly benefit from case-study writeups that explain the problem, approach, and outcome. Portfolios with images-only can be ambiguous about what the candidate actually contributed.

Takeaway

Resumes and portfolios serve multiple functions (ATS keyword screening, human-recruiter screening, interviewer context for behavioral and judgment evaluation). Strong resumes lead with impact rather than responsibility, quantify outcomes honestly with specific metrics where available, match job-posting language for ATS keyword matching, order experience by relevance rather than chronology when appropriate, stay scannable with consistent formatting, and tailor per application or application category. Portfolios are curated case studies for roles where work-product evidence matters (engineering, design, AI/ML, technical writing); strong portfolios are 3-5 deep case studies rather than 30 minor projects. LinkedIn profile and (sometimes) cover letter complement the resume in modern hiring contexts. AI assistance helps with editing for clarity and bullet-restructuring but doesn’t substitute for genuine accomplishment claims, strategic framing, or cultural-fit calibration specific to target employers.

For broader treatment of skills-based hiring and how portable credentials change the resume-and-portfolio landscape, see skills-based hiring evidence, skills vs credentials, hiring-loop design, salary negotiation prep for the post-screen hiring stages, and the scoring methodology for the AIEH portable- credential approach.

Sources

More in Prep Guides

AI Product Manager Interview Prep Guide Algorithms and Data Structures Prep Guide for Technical Interviews and AIEH Assessments Backend Engineering Interview Prep Guide Behavioral Interview Prep Guide

View all Prep Guides articles →

About This Article

Researched and written by the AIEH editorial team using official sources. This article is for informational purposes only and does not constitute professional advice.

Last reviewed: · Editorial policy · Report an error