11 min read
Your Skills block says Kubernetes, but bullet one under your current job still reads "worked on backend services." That's the gap. Recruiters search Greenhouse for stack plus scope, not a cloud of nouns in a sidebar. You've got the experience. The file just isn't showing it where the parser and the human both look first.
Check your resume for free on the export you'll attach tonight. The resume mistakes software engineers make are rarely missing degrees. They're duty lines, tool dumps without outcomes, and proof that lives in Skills instead of under the employer who paid for the work.
Below you'll see the bar strong SWE bullets clear, before/after pairs across five stacks, what weak versions share, and a copy-paste skeleton you can drop under your current role. Job searching's already slow. Don't burn another week wondering if you're underqualified when the file never named the stack they queried.
Open the posting you're targeting. Highlight three must-haves. We'll rewrite bullets so one lands in the first eight words. You won't need a new template. You need lines a sourcer can forward without a cover note explaining what you actually built.
Quick Wins
- Put the posting's top stack in the first eight words of bullet one.
- Replace "responsible for" with built, shipped, cut, or owned plus a number.
- Move proof out of Skills into the employer line that paid you.
- Three bullets per recent job, newest role first, single column.
What strong software engineer bullets are judged against
A sourcer types "Python" and "AWS" into Greenhouse. Your row only lights up when those strings sit in parsed Experience, tied to an employer and a date range. Skills without job context reads like a tutorial list. Bullet one should answer: what did you ship, with which tools, at what scale, and when.
The first bullet under your current role is your headline. Everything else supports it. Hiring managers skim that line before they open the PDF. If it still says "participated in agile ceremonies," they'll assume the rest of the file matches.
Strong SWE bullets follow a simple shape: action verb, stack or system name, measurable outcome, scope hint. "Built payment retry service in Go on AWS ECS, cutting failed charges 14% in Q2 2025 for 2.1M monthly transactions." That's searchable and readable in six seconds.
Edge case: you're a generalist applying to a specialist req. Pick the stack the posting names three times and lead with honest proof from the last eighteen months. Edge case: contract work with NDA limits. Name the system type and metric band without the client logo: "Refactored HIPAA audit pipeline in Java, reducing manual review hours 22% for a regional payer."
For layout rules that keep Experience readable in Workday, read how to write resume experience ATS understands before you rewrite bullets inside a two-column template.
Junior engineers often ask whether to lead with education. Once you have one paid engineering title with production proof, Experience goes first. Education drops to three lines: degree, school, graduation year if recent. Certifications belong in one row only when the posting names them, such as AWS Solutions Architect for a cloud-heavy req.
Before/after resume bullets across SWE stacks
Each pair below is a composite from files I've screened. Copy the After line structure, not the fake company names. Swap in your stack, your metric, your quarter.
Backend: Python and AWS
Before: Worked on microservices and REST APIs using Python. Improved system performance.
After: Built order-ingestion microservices in Python and FastAPI on AWS Lambda, cutting p95 latency from 420ms to 290ms for 180K daily orders in 2024.
The Before line could describe any backend hire from 2016. The After names the service boundary, the cloud runtime, and a latency band a staff engineer would ask about in a screen.
Frontend: React and TypeScript
Before: Developed UI components in React. Collaborated with designers on new features.
After: Shipped checkout redesign in React and TypeScript, lifting completed purchases 9% and cutting Largest Contentful Paint 0.8s on mobile in Q1 2025.
Frontend files die when bullets read like ticket titles. Tie the component work to a business or performance outcome recruiters can repeat to the hiring manager without translating design jargon.
DevOps and SRE: Kubernetes and CI/CD
Before: Maintained CI/CD pipelines and Kubernetes clusters. On-call rotation.
After: Migrated 34 services to Kubernetes on EKS with GitHub Actions deploy gates, shrinking release lead time from 3 days to 6 hours and holding error budget at 99.95% uptime in 2024.
On-call alone is not a selling point. Pair reliability work with deploy frequency or incident reduction so the line signals senior scope, not pager fatigue.
Mobile: iOS and Swift
Before: Built iOS apps in Swift. Fixed bugs and released updates to the App Store.
After: Led SwiftUI rewrite of onboarding flow for iOS 17, raising day-7 retention 6 points and cutting crash-free sessions below 0.3% across 420K MAU in H2 2024.
App Store verbs without user counts look junior. MAU, retention, and crash rates are the mobile equivalent of backend latency proof.
Data and ML: SQL and Python
Before: Worked with data pipelines and machine learning models. Python, SQL, Spark.
After: Built nightly feature store jobs in Python and Spark on Databricks, feeding fraud model that flagged 12% more blocked transactions with false positives flat in Q3 2024.
Tool lists at the end of a duty line are a Skills spillover. Move Spark and Databricks into the sentence that shows the model outcome, not a comma dump after "models."
Full-stack: Node and PostgreSQL
Before: Full-stack developer on Node.js applications. Responsible for database design.
After: Owned billing portal in Node.js and PostgreSQL, adding usage-based pricing that lifted expansion revenue 11% for 3,400 SMB accounts in 2025.
"Full-stack" in the title still needs stack proof in bullet one. Otherwise sourcers file you as generic web dev when the req asked for payments depth.
Embedded and systems: C++ and Linux
Before: Wrote firmware in C++. Debugged hardware issues on embedded Linux devices.
After: Ported sensor driver stack from C++11 to C++17 on embedded Linux, cutting boot time 18% and field-replace rate 7% across 24K deployed devices in 2024.
Hardware roles get vague fast when bullets only say "debugged." Name the subsystem, the language version or kernel layer, and a field metric buyers care about.
Copy-paste bullet skeleton for your current role:
[Action verb] [system or feature] in [primary stack from posting] on [cloud or platform], [metric verb] [number] [unit] for [scope: users, requests, accounts] in [quarter or year].
[Second bullet: integration or reliability proof with second must-have tool].
[Third bullet: leadership or scope: team size, repos owned, cost saved].
Repeat newest employer first. No tables. Skills list stays short; proof lives here.
For metric phrasing that survives parsing, read how ATS interprets numbers on resumes before you add percentages inside garbled two-column exports.
What weak software engineer bullets share
Duty verbs without objects. "Supported," "assisted," and "helped with" tell me you were in the room, not what shipped. Swap for built, shipped, migrated, owned, or cut tied to a system name.
Stack in Skills, silence in Experience. Fifteen languages in a grid and zero under your last three employers means the parser and I both assume tutorial exposure. Move the three tools the posting repeats into bullet text under the job that used them.
Team outcomes with no "I" boundary. "We improved performance" is fine in standup, weak on paper. One line on your slice: the service you owned, the migration you led, the test suite you added. Hiring managers know teams ship together. They still need your lane.
Projects that outrank jobs. A GitHub toy above your staff engineer role signals misordered priorities. Keep one flagship repo if it's your only proof for the target stack. Otherwise Projects sits below Experience with dates.
Keyword stuffing at the bottom. A paragraph of frameworks after Education looks like SEO from 2012. Greenhouse may file it as Skills without employer context. Integrate keywords into bullets or drop them.
Title inflation without proof. "Principal Engineer" on a file where every bullet reads mid-level triggers a credibility check in the first ten seconds. Match title to scope in bullet one or use the internal level the company would verify on a reference call.
Edge case: bootcamp grads stacking five capstone projects above a short internship. Flip order once you have six months of paid production work. Edge case: staff candidates listing twenty bullets per job. Recruiters stop reading after five. Keep three strong lines and cut the rest.
Acronyms without first use. Writing "SLA" and "RBAC" in every bullet assumes the reader knows your last employer's internal vocabulary. Spell the system once, then shorten: "role-based access control (RBAC) for admin console serving 8,200 internal users."
Missing dates on side projects. A repo with no year looks stale or fictional. Add Month Year beside the project title the same way you date jobs. Recruiters use chronology to guess whether your React proof is from this stack version or a course from 2019.
This won't fix applying when you lack the posting's must-have years. It stops qualified engineers from getting filtered because the file read like a Skills dump instead of shipped work.
Match bullets to the posting before you apply
Paste the job description into the free ATS resume checker with your revised export attached. Low match scores on tools you actually used usually mean the words sit in Skills, not under your current employer.
Applying to five similar reqs this week? Run the job match score on each posting against one master file, then tweak bullet one per req instead of rebuilding layout every time.
Save versions as Firstname-Lastname-Backend.docx or Firstname-Lastname-Platform.docx when you target different tracks. Same layout, different bullet one. You'll spot faster which track your proof actually supports instead of sending one generic cloud file to every req.
Fix resume mistakes software engineers make, then tailor
The resume mistakes software engineers make almost always live in Experience wording, not missing credentials. Move stack proof into bullet one, swap duty lines for shipped outcomes, and cut Skills down to what you'd defend on a technical screen.
Open your file tonight. Pick the posting you want most. Rewrite the first bullet under your current job using one Before/After pair above as a mold. Run the checker. If match flags a tool you used, add it to that bullet, not the footer.
Save one master DOCX. Tailor bullet one per req, not the whole design. Layout is one-time work. Keyword placement is per application. Mixing the two is how strong engineers burn weekends on templates while weak bullets stay untouched.
When the portal asks for a cover letter, generate a cover letter that names the same stack and metric you put in bullet one. Letter and resume should tell one story after Greenhouse parses both fields.
Read more
Frequently asked questions
No. List core tools you would defend in a screen, then prove them in Experience bullets. Greenhouse search often weights job titles and bullet text above a long Skills grid. A posting that asks for Go and PostgreSQL needs those words under your current employer, not floating alone in a sidebar list.
Three to five for recent roles, two to three for older ones. Lead with the bullet that names the stack and outcome for the posting you want next. If you cannot fill three proof lines for a job, you may be keeping a title that no longer matches the work you did there.
Drop them once you have two full-time engineering roles with shipped outcomes. Keep one internship only when it is your only production proof for the target stack. Senior files should not push a 2019 bootcamp project above a 2024 platform migration.
A link helps after the bullet earns the click. Recruiters search parsed text first. Write one line that names the repo scope, stack, and user or traffic impact, then add the URL on the same line or in a Projects subsection with dates.