A recruiter eye-tracking study show that recruiters spend about 7.4 seconds on the first pass of your resume. In that window, most of them never reach your work history. They read the few lines at the top and decide.
This is consistent with my experience: I screened resumes for 13 years as a recruiter, including at Google.
On popular roles there, I went through 200+ resumes a day. Now, with TechieCV, I rewrite resumes for engineer and tech professionals.
This is the order I write a Profile Summary in to pass recruiter screens. Try it out if you struggle with getting interview callbacks!
1. Pull title, tools and domain from job postings
Why it matters: When I screened resumes, I checked 4 things in the summary, in order: title, level, stack, domain. If one was missing, I moved to the next CV. I never went hunting for skills in the Experience section during the first review, because I didn't have time.
How to do it:
- Open 2 or 3 postings for the role you want.
- Write down the job title, the required tools and the shared domain.
- Your first three bullets have to match this list.
Here's an example:
Target title: iOS Developer
Must-haves: Swift, SwiftUI, Combine, XCTest
Domain: consumer fintech apps
2. Open with title, years and products
Why it matters: In the Ladders study, recruiters looked at job titles longer than at anything else on the page. Your first bullet tells them you're the right role and the right level.
How: Start with the title exactly as written in the posting. Add your years of experience, your specialty/engineering domain, the products or systems you built and one project you're proud of. Mention employers only if people know them (think big tech or unicorns). Juniors can stay vague on years with "a solid track record".
Example:
iOS Developer with 6 years of experience building secure, offline-first banking apps, including the card controls and instant transfers of a mobile bank with 3M users.
3. Add your main tech stack
Why it matters: This is where the recruiter ticks off the must-have tools from their checklist.
Listing every tool you've ever touched "muddies the water" in the profile summary (your full list should be placed in the "Technical Skills" sectin).
How:
- List the tool categories the role uses, with your specific tools in parentheses.
- Put the posting's must-haves first.
- Keep tools inside a sentence about your work (cramming keywords WILL hurt you)
Example:
Strong across languages (Swift, Objective-C), UI frameworks (SwiftUI, UIKit), async code (Combine, async/await), testing (XCTest, XCUITest) and CI (Fastlane, GitHub Actions).
4. Specify the area you're best at
Why it matters: The summary is the one part of a resume where you get to judge your own profile skills. Recruiters tend to take that claim at face value, before looking for proof of it in your job blocks. That's confirmation bias working in your favor ;-)
How: Pick 2 to 4 specialties inside your discipline: your "claim to fame". Then add the methods and concepts that are industry standard in your field.
Example:
Deep expertise in app performance, accessibility (VoiceOver, Dynamic Type) and modular architecture, using MVVM and Swift Package Manager modules to keep build times low.
5. Show who you work with and how
Why it matters: Recruiters want to picture you on their team. Adjectives like "hard-working" or "detail-oriented" don't help them do that because these are subjective statements (and frankly, everyone uses them).
How: List the teams you work with, what you collaborated on, and how you work together: Agile, sprint planning, code reviews. Finish with a short phrase about your style, so you read like a person.
Example:
Close partner to Product Designers, Android Engineers and QA in two-week sprints, running design handoffs and API contract reviews with a calm, low-ego style.
6. Prove you make the team better
Why it matters: Leadership on a resume covers more than managing people. Mentoring, side projects and sharing what you know all show that you care about helping others.
How:
- People management, if you have it.
- Mentoring or peer support.
- Projects outside your main role.
- Articles, internal docs or tech talks.
Example:
Mentor to 3 junior iOS developers, owner of the team's release checklist, and speaker at the internal mobile guild on moving from UIKit to SwiftUI.
7. Add an X factor if you have one
Why it matters: Plenty of candidates share your stack. This optional bullet is what sets you apart from them.
How: Use spoken languages, certifications that fit the target role, open-source work, a company you started, awards or patents. If nothing fits, stop at bullet 5. Padding costs you a line.
Example:
Fluent in English and Spanish, and maintainer of an open-source SwiftUI charting library with 1.2k GitHub stars.
While you write, cut objective lines like "seeking a challenging position", drop "I" and "my", and keep each bullet to 2 lines at most.
The checklist
- Pull the title, required tools and domain from 2 or 3 postings.
- Open with the exact title, your years and the products you built.
- Group your stack by type, tools in parentheses, must-haves first.
- Claim 2 to 4 specialties and the methods behind them.
- List the teams you work with and how you work together.
- Show mentoring, side projects or talks.
- Add languages, certifications or open source, only if they fit.
Your summary does the recruiter's first screen for them, so build it from the posting, one bullet per requirement ;-)
The full guide has 13 profile summary examples by tech role and a version for no work experience, from IT support to FPGA engineering, if you want to see the formula applied to your own job.
I hope it helps!
Top comments (3)
opening with title/years/products before the stack list is the part most summaries skip.
Yep! A few stats on resumes I screen (rough estimations):
That 80% missing products is the easy win. Titles and years don't tell a hiring manager what someone actually shipped.