DEV Community: Larbi Sahli

How to Write a Career Change Resume That Actually Gets Interviews

Larbi Sahli — Mon, 27 Jul 2026 21:57:12 +0000

A lot of people reading dev.to didn't start in software. Bootcamp grads, teachers, nurses, retail managers, marketers who taught themselves SQL. And plenty of devs are pivoting the other way, into product, data, or DevRel. I built Roleframe around per-job resume tailoring, and career switchers are the group I see struggle most, because their job titles actively work against them in every screening system.

I wrote this guide because the standard advice for switchers is mostly wrong. The "functional resume that hides your dates" trick gets you flagged by recruiters. The clever objective line gets skimmed past. What actually works is more mechanical and more honest: lead with the destination, prove relevance with real results, and match the exact vocabulary the new field's screening software is scoring against.

Here's the full playbook, section by section, with the specific moves that get switchers interviews instead of silence.

The core problem with career change resumes

Your resume gets judged twice, and both judges are skeptical of switchers. First an applicant tracking system (ATS), the software companies use to store and search applications, scores you against the job's keywords. Then a human recruiter spends a few seconds deciding whether you look like a fit.

A career changer fails both by default. The ATS ranks you low because your resume is full of the previous industry's vocabulary, not the new one's. The recruiter reads a title that doesn't match the role and assumes you're a stretch. Neither one is trying to be unfair. They're both filtering for obvious relevance, and a raw chronological resume from your old field doesn't signal it.

So the whole task comes down to one thing: manufacturing obvious relevance. You do that by reframing what you've done in the language of where you're going, and by putting the most relevant proof at the top where both judges will actually see it.

Why the wrong format quietly sinks you

Many switchers reach for a "functional" resume that hides dates and job titles behind a wall of skills. Recruiters distrust it instantly, because it reads like you're concealing something. It also confuses the ATS, which expects dated work history it can parse. Think of it like a file the parser can't deserialize: the content might be great, but nothing downstream ever sees it.

The format that works is the combination (hybrid) format: a targeted summary and a skills section up top, then a normal reverse-chronological work history underneath, reframed for relevance. The top third sells your fit for the new field. The bottom keeps the structure recruiters and software trust.

Why you need role workspaces, not one all-purpose resume

Career changers rarely target a single job title. You might be weighing frontend developer against data analyst against product manager, or moving from teaching into instructional design, developer education, and QA at once. Each of those needs a genuinely different resume, because each field prizes different keywords and different proof.

The common mistake is keeping one master resume and rewriting it over and over for each direction. Every rewrite risks breaking the version that was working, and you lose track of which draft went where. It's the resume equivalent of editing production directly with no version control.

A cleaner system is to keep a separate base resume per target role, then spin off a tailored version for each specific job. That's exactly what Roleframe is built around: role workspaces hold one master resume per direction you're exploring, and each application gets its own tailored copy without touching the master.

Identifying and highlighting transferable skills

Transferable skills are the abilities that carry across industries: managing stakeholders, analyzing data, running projects, coaching people, writing clearly. They're the backbone of any career change resume, because they let you claim relevance you can't get from your job titles.

Start by pulling apart your old roles into skills, not duties. A teacher doesn't just "teach." She manages a room of thirty, builds curriculum on a deadline, tracks performance data, and communicates with difficult stakeholders (parents). Each of those maps onto a corporate job. The reframing work is naming the underlying skill instead of the industry-specific task.

How to find which skills actually matter

Don't guess at what the new field values. Pull up three to five real job postings for your target role and read them side by side. Note the skills, tools, and phrases that repeat. The U.S. Department of Labor's O*NET occupation database is another good source for the core competencies of a specific job. The words that show up again and again are the skills your resume needs to prove.

Then match your history to that list. For each recurring skill, find one concrete thing you've done that demonstrates it. That pairing, target skill plus your proof, becomes the raw material for your skills section and your bullets.

Group skills the way the new industry does

Recruiters and ATS searches are increasingly skills-driven, so a labeled skills section earns its place at the top. Organize it into categories the target field uses, not generic buckets. A data analyst pivot might use headers like "Data & Analytics," "SQL & Reporting," and "Stakeholder Communication." Name real tools where you've genuinely used them: SQL, Figma, Salesforce, Asana, Excel.

Where you can, add a short evidence line under a skill rather than listing it bare. "Stakeholder Management: aligned five department heads on a shared reporting standard" beats the word "communication" sitting alone. Evidence turns a keyword into a claim you've backed up.

Structuring your experience section for a pivot

Your experience section has to do double duty: satisfy the ATS with real dated roles, and convince a human that the work is relevant. The trick is reframing each bullet around outcomes that matter in the new field, not tasks that mattered in the old one.

Lead every bullet with a measurable result, then add brief context. This is a STAR-style approach compressed into one line: the achievement first, the situation second. "Cut support ticket volume 18% by redesigning the onboarding flow" reads as a business outcome any industry understands. "Responsible for handling customer inquiries" reads as a task nobody remembers.

Reframe the work, don't invent it

Reframing means changing the language and emphasis, never the facts. If you managed a retail team and you're targeting operations, describe it as scheduling, inventory forecasting, and shrinkage reduction, because those are operations skills. Same job, different lens. You're translating your experience into the vocabulary of the reader.

Quantify wherever you honestly can. Percentages, dollar amounts, headcounts, time saved, volume handled. Numbers are industry-neutral proof, and they pull a recruiter's eye toward substance instead of your unfamiliar job title.

Use a "relevant experience" section to move recent proof up

If your most relevant work isn't your most recent paid job, create a section that surfaces it. Many switchers add a Relevant Experience or Relevant Projects block above their standard work history. Put your bootcamp project, freelance gig, open-source contributions, volunteer role, or side work there, so the first thing a reader sees is recent, concrete practice in the new field.

This directly answers the "no experience" version of the pivot. You almost always have more relevant experience than you think, it's just scattered across unpaid or informal work. If you're switching into software, this is exactly where a well-documented portfolio project carries the most weight.

Feature training and credentials near the top

Recent learning signals you're serious about the switch, so don't bury it at the bottom. If you've finished a Google Career Certificate, a Coursera or edX program, an industry micro-cert, or tool-specific training, place it high enough to be seen in the first pass. For a career changer, a fresh, relevant credential often carries more weight than a decade-old degree in the old field.

Writing a summary that bridges the gap

The professional summary is where you win or lose the pivot, because it's the first thing read and it sets the frame for everything below. Name your target role directly. Write "Data Analyst" or "Frontend Developer," not "marketing professional seeking to transition into tech." You want to read as someone who already operates in the new space, not someone hoping to be let in.

Cut the words "aspiring" and "transitioning." They plant doubt. Present-tense confidence backed by transferable achievements does the opposite.

The three-part summary formula

A strong career transition summary makes three moves in three to four sentences:

Who you are in the target role, stated plainly with your relevant strengths.
Two or three transferable proof points, ideally quantified, that show you've already done the work in a different setting.
What you're ready to deliver next, tied to the kind of role you're applying for.

Here's the pattern in action for a teacher moving into corporate training: "Learning and development specialist with seven years designing and delivering instruction to groups of 30+. Built a curriculum adopted district-wide and raised assessment scores 22% in one year. Now focused on scaling employee onboarding and skills programs for a growing team." No apology, no "aspiring," just a claim with evidence.

Add one line of bridge content

Recruiters do wonder why you're switching, so answer it briefly instead of leaving them to guess. One sentence is enough on the resume: what draws you to the field, which transferable strength proves your fit, and any training you've completed. Save the fuller story for your cover letter, where a short paragraph can explain the move without cluttering the resume. Roleframe generates a job-specific cover letter to pair with each tailored resume, which is the natural place to carry that narrative.

Tailoring to the new industry's ATS keywords

This is where career changers lose the most interviews without ever knowing it. Modern ATS and AI screeners score your resume on how closely its language matches the job description. When you're switching fields, your resume is written in your old industry's terms, so it scores low on the exact keywords the new role searches for. You never hear back, and it looks like rejection when it's really a language mismatch.

Exact-match matters more than people expect. If the posting says "stakeholder management" and your resume says "working with clients," a keyword-based screen may not connect them. If it asks for "SQL" and you wrote "database querying," you can miss the filter. The screen does string matching, not semantic search. For switchers with no title match to fall back on, mirroring the posting's precise terminology is the thing that gets you seen.

How to match keywords without stuffing

Work from the same three to five postings you used to map your skills. Extract the recurring hard skills, tools, and phrases, then place them where they belong: in your summary, your skills section, and inside real achievement bullets. The goal is genuine coverage, not a keyword dump. A skill that appears in a real accomplishment reads as true; a skill stuffed into a list at the bottom reads as filler and a recruiter sees through it.

Doing this by hand for every application is slow, and speed matters for switchers. This is the part I automated with Roleframe: paste a job posting and it tailors your keywords, section order, and bullets for that specific job in seconds, so each application matches the language the screener is scoring against.

Keep the layout ATS-safe

All the keyword work fails if the software can't parse your file. Use a clean single-column layout, standard fonts like Calibri or Helvetica, and no text boxes, graphics, or multi-column tricks that scramble parsing. Keep it to one page for an early-career pivot, up to two for a senior professional with a long, reframed history.

Save and submit as a PDF. It preserves your formatting across every device and is what recruiters expect. Only send a .docx if a specific employer or ATS explicitly asks for it, and even then, PDF is your default. Roleframe exports a clean, ATS-friendly PDF that matches the editor exactly, so what you approve on screen is what the recruiter opens.

Apply fast, before the pipeline fills

Timing decides more outcomes than people admit. Many roles collect most of their strong applicants in the first few days, and recruiters often start reviewing before the posting closes. Apply late and you're competing for attention that's already spoken for, no matter how good your resume is.

This is the hidden tax on career changers. Because your resume needs more tailoring than a straightforward applicant's, the honest tailoring work can push your application past the window where it matters most. The answer isn't to skip tailoring and send something generic; a generic resume from a switcher gets filtered fast. The answer is to make tailoring fast enough that you're both relevant and early.

A quick reference: the resume rules people ask about

A few shorthand "rules" circulate in resume advice. Here's what they mean and how they apply to a career change specifically.

Rule	What it means	Why it matters for a switcher
7-second rule	Recruiters give a resume roughly a few seconds on first scan	Your target role and best proof must sit in the top third, or the pivot is missed
3 C's	Clear, concise, compelling	A switcher's story fails if it's cluttered; clarity is what makes an unfamiliar path believable
5 P's	Positioning, presentation, proof, personalization, polish	Positioning and personalization carry the most weight when you're changing fields

Career change resume checklist

Use a combination format: targeted summary and skills up top, dated work history below.
Name your target role directly in the summary; drop "aspiring" and "transitioning."
Mine three to five real job postings and O*NET for the exact skills and terms the field uses.
Reframe each bullet as a quantified outcome, not an old-industry task.
Add a Relevant Experience or Projects section to surface recent, aligned work.
Feature recent credentials and training near the top for credibility.
Match the posting's exact keywords in your summary, skills, and bullets.
Keep the layout ATS-safe and export as a PDF.
Tailor per job and apply while the posting is fresh.

The short version: a career change resume isn't about hiding where you came from. It's about translating what you did into the language of where you're going, backing it with numbers, and getting it in front of the recruiter before the pipeline fills. Do those three things and the mismatched job title stops being a dealbreaker.

Originally published at roleframe.ai.

Why Your AI Resume Sounds Generic (And How to Fix It)

Larbi Sahli — Mon, 27 Jul 2026 21:44:10 +0000

I'm Larbi, and I build Roleframe, an AI tool that tailors resumes to specific jobs. I spend a lot of time looking at what large language models (LLMs) produce when you ask them to "improve" a resume, and the output is almost always the same: results-driven professional, leveraged cross-functional teams, orchestrated end-to-end solutions. If you've used ChatGPT on your own resume, you've seen it too.

I wanted to write this for a developer audience because you already understand the machinery underneath the problem. This isn't magic or a mystery. It's next-token prediction, model routing, and prompt design. Once you see the resume through that lens, the fix becomes obvious and mechanical.

What you'll get here: why cheap models default to generic phrasing, the three tells recruiters catch, why a single prompt can't tailor a resume properly, and a ten-minute audit you can run on any AI output before you send it. Let's get into it.

The unlimited AI trap: why your resume reads like a robot

Most "unlimited AI" resume builders have a math problem they don't advertise. If a tool promises endless rewrites for a flat monthly fee, it can't afford to run the best, most expensive models on every request. So it routes your resume to the cheapest model that produces passable text.

Cheap models play it safe. When they're unsure what to say, they fall back on the highest-probability phrasing in their training data. That data is millions of existing resumes and job ads, so the model mirrors the average of all of them. The result is what recruiters call a resume monoculture: near-identical wording and structure no matter who the candidate is or what they actually did.

You feel it as vagueness. Padded metrics, filler verbs, and summaries that describe a job title instead of a person. The tool isn't broken. It's doing exactly what a low-compute model does when nobody paid for anything better.

Cheap models vs. frontier models: the hidden downgrade

There's a real quality gap between the cheap models behind "unlimited" plans and the frontier models that cost more to run. The difference isn't grammar. Both write clean sentences. The difference is judgment: how well the model reads a job posting, matches it to your experience, and picks specific language over safe language.

A stronger model notices you shipped a payments feature under a deadline and writes a bullet about the trade-off you made. A cheaper model writes "improved operational efficiency" and moves on. One reads like a person who was in the room. The other reads like a template.

The "unlimited" pitch hides this downgrade. You're told you can generate as many resumes as you want, and technically you can. What you're not told is that every one ran through a model chosen for cost, not quality.

Why models sound generic in the first place

LLMs predict the next likely token. Without strong, specific input, "likely" collapses to "common," and common resume language is buzzword-heavy by default. The model can't invent your impact. It only knows what you feed it, and when you feed it little, it reaches for legacy filler like synergy, stakeholder management, and team player.

That's also why AI text feels weird even when it's fluent. It's abstract. It describes categories of work ("cross-functional collaboration") instead of the concrete thing you did ("ran weekly syncs between design and backend to unblock the checkout redesign"). Recruiters read that abstraction as evidence you're hiding a thin story, whether or not that's true.

The 3 dead giveaways of a generic AI resume

Recruiters spot AI resumes fast because the tells are consistent. Here are the three that matter most, and what each one signals.

1. Stock phrases with no proof behind them

The clearest giveaway is buzzword-heavy phrasing with nothing to back it up. Results-driven professional with a proven track record is a claim, not evidence. A human writes cut checkout errors 30% by rebuilding form validation. One asserts. The other shows.

The problem isn't that the words exist. It's that people stop at that generic layer and never add the proof. Once a resume leans on stock phrases without a number, a decision, or a specific project, it reads as filler.

2. Padded or invented metrics

Cheap models love round, vague numbers because they sound impressive and cost nothing to generate. "Increased efficiency by 40%" with no baseline, no timeframe, and no method is a padded metric. Recruiters have read thousands and discount every one.

Real metrics have texture: what you measured, over what period, and how. "Reduced average API response time from 800ms to 210ms over one quarter by adding caching" is believable because it's specific. If your AI resume is full of clean percentages you can't defend in an interview, that's a tell and a risk.

3. Identical structure and overly formal tone

AI-written resumes tend to follow the same skeleton: a templated summary, an oversized skills section, then bullets that all start with the same handful of verbs. The language is formal and abstract, with no personal voice and no sense of the decisions you made.

Modern applicant tracking systems (ATS) like Workday, Greenhouse, and Lever already parse a normal resume without that padding. So the bloated skills section and interchangeable summary aren't helping you pass filters. They just make you look like everyone else who used the same tool.

Why one prompt isn't enough for a tailored resume

A single prompt can't tailor a resume properly because tailoring is several different jobs, and one pass does none of them well. When you paste your resume and type "tailor this to the job," the model tries to read the posting, find your matching experience, decide what to emphasize, and rewrite everything, all in one shot. It ends up doing each step shallowly.

The most common failure is that the model only loosely incorporates the actual job description. You get bullets that are broadly plausible for the role but not tightly aligned to its specific requirements. In a pool where half your competitors used the same tool, loose alignment is what makes resumes blend together.

If you're going to work with a general chatbot anyway, at least give it a proper brief and split the task into stages: analyze the posting, extract requirements, plan what to emphasize, then rewrite. The prompts that pull specifics out of a model instead of averages are the ones that force each of those steps separately.

How a multi-agent pipeline fixes the problem

The fix is to break tailoring into specialized steps and run each one properly, instead of asking one model to do everything at once. That's what a multi-agent pipeline does: separate AI agents handle analysis, keyword matching, strategy, rewriting, and review, and each hands its output to the next.

This is how Roleframe works, and each step exists to kill a specific source of generic output:

Deep job analysis. An agent reads the posting like a senior recruiter: role type, seniority, and every requirement, mapped against your real experience. This tightens alignment to the actual job instead of a generic version of it.
Keyword extraction and matching. It pulls the exact terms recruiter filters scan for, then checks which your resume already covers and which are real gaps, so nothing gets stuffed in blindly.
Tailoring strategy. A prioritized plan for this exact role: what to rewrite, reorder, and emphasize, and why. This is the judgment step cheap single-prompt tools skip.
Full rewrite. Your summary and bullets get rewritten and the missing keywords woven in honestly, never inventing experience you don't have.
Recruiter-grade final review. A second pass audits the result for remaining gaps and anything only you can fix, so you don't ship padded metrics you can't defend.

The point isn't magic. It's that spending real compute on each stage produces specific language, because a model that has actually analyzed the job and your history has something concrete to write about. Roleframe exports the final result as a clean, ATS-friendly PDF that matches the editor exactly.

Advanced AI vs. everyday AI: paying only for what matters

The honest way to run good models on every resume is to meter the heavy work instead of promising it's unlimited. That's the trade behind Roleframe's credit-based pricing, and it's the opposite of the "unlimited" model that forces a tool to route everything to the cheapest option.

Roleframe splits AI into two buckets. Everyday AI is free and unlimited on every plan, including the free one: rewriting a single bullet, checking whether a fix worked, the inline assistant. Advanced AI, the heavy multi-agent work that decides whether you get an interview, costs credits: tailoring a resume to a job, scoring and auditing it, generating a cover letter, and full tailoring reports.

A paid subscription gives you 1,000 credits a month. At roughly 25 credits to tailor a resume, that's about 40 fully tailored resumes every month, and everyday AI stays free on top. Current advanced-AI costs are roughly 25 credits to tailor a resume, 18 to analyze one, and 15 for a cover letter. Those are current values that can change. You see the cost before you run anything, failed runs are refunded, and there's a 14-day money-back guarantee.

Why do it this way? Metering the advanced runs means each one can use the best models available. You pay only for the runs that matter, and you never pay for the small stuff. The takeaway for your resume: "unlimited AI" and "high-quality AI" are usually opposites. If quality matters more than volume, that's the trade to look for.

How to audit your current resume for AI cliches

Run this on whatever your AI tool gave you before you send it anywhere. It takes about ten minutes and catches the phrasing recruiters flag.

Do the name test. Cover your name and read the top third. If the summary could belong to any candidate with your title, rewrite it around one specific thing you're known for.
Hunt the stock phrases. Delete or replace results-driven, proven track record, leveraged, spearheaded, synergy, stakeholder management, and team player. Each is a claim begging for proof.
Interrogate every number. For each metric, ask: baseline, timeframe, method. If you can't answer all three, the number is padding. Make it specific or cut it.
Check verb variety. If most bullets open with the same two or three verbs, your resume looks machine-generated. Vary them and lead with the action that actually happened.
Test alignment to the job. Put the posting next to your resume. Highlight every requirement your bullets clearly address. Thin coverage means the AI wrote broadly instead of tailoring.
Add the context AI can't invent. For your top three bullets, write one clause on why the work mattered or what trade-off you made. That decision logic separates you from the monoculture.
Read it aloud. Anything that sounds like a press release gets rewritten in plain words. If you wouldn't say it in an interview, don't put it on the page.

The single highest-leverage move is replacing abstract claims with concrete outcomes. AI defaults to "improved collaboration" because it can't infer what you actually did. Only you know you unblocked the checkout redesign by getting design and backend into one weekly sync. That's the detail that makes a resume sound human, and no model can supply it unless you do.

FAQ

Why do AI models often sound generic?

Language models predict the most likely next token, and "likely" means "common." Trained on millions of existing resumes and job ads, they default to the average phrasing across all of them. Without specific input from you, they reach for safe, high-level claims like "improved efficiency" instead of the concrete thing you did. Cheap models do this more, because they have less capacity to weigh context and pick specific language.

Is it bad if my resume sounds like AI?

Using AI isn't the problem. Many hiring teams now expect polished, keyword-aware resumes and treat them as normal hygiene. The problem is stopping at the generic layer, where your resume becomes interchangeable with everyone else's. When a recruiter can't tell you apart from the next candidate, your resume stops being proof of ability. So edit the AI output until it sounds like you.

Why does AI text sound weird even when it's grammatically correct?

Because it's abstract. AI describes categories of work ("cross-functional collaboration") instead of the concrete instance ("ran weekly syncs to unblock the checkout redesign"). The tone is often overly formal, with no personal voice and no sense of the decisions behind the work. Fluent but empty reads as filler.

Why does my ChatGPT resume come out so generic?

Usually the brief and the single-pass approach. If you say "make my resume better," the model has nothing specific to work with and falls back on buzzwords. It also tries to analyze the job, match your experience, and rewrite everything in one shot, so it does each step shallowly. Feed it detailed inputs, split the work into stages, and tell it exactly which requirements to align to.

Does an "unlimited AI" resume builder produce worse resumes?

Often, yes. To offer unlimited rewrites at a flat fee, a tool has to route most requests to the cheapest model it can afford, and cheap models lean harder on generic phrasing. Metering the heavy work instead means each of those runs can use the best models. If output quality matters more to you than raw volume, look for tools that charge for advanced work rather than promising it's unlimited.

Originally published at roleframe.ai.