Resume example
Software developer resume example.
A fictional resume for a mid-level developer with four years of experience. Shows how to describe technical scope, cross-team work, and outcomes in bullets that a hiring manager can scan quickly.
Every name, employer, project, and number here is invented. Use it to learn structure, not to copy content.
Bilal Farooq
Full-stack developer · TypeScript & Node.js focus
- bilal.farooq@example.com
- +92 300 5550001
- Karachi, Pakistan
- github.com/example-bilal
- bilal-farooq.dev
Summary
Full-stack developer with four years of experience building web applications in TypeScript and Node.js. Shipped a customer-facing portal serving 12,000 monthly users, and led the migration of a legacy PHP service to a Node.js API. Comfortable owning features end-to-end, from database design to deployment. Looking for a mid-senior role on a team that cares about code review and testing.
Experience
Full-stack Developer
Mar 2022 – presentLumen Labs · Karachi (remote)
- Led a 4-month migration of a legacy PHP customer portal to a TypeScript + Node.js API, eliminating ~30% of outstanding production bugs and reducing median page load from 3.4s to 1.8s.
- Designed and shipped a real-time notification service used by 12,000 monthly users; wrote the PostgreSQL schema, the Node.js consumer service, and the delivery retry logic.
- Introduced end-to-end tests (Playwright) to the team's CI pipeline; new bugs caught in review increased by roughly 40% over the following quarter.
- Mentored two junior developers through their first six months, including onboarding, weekly 1:1s, and code review.
Junior Developer
Aug 2020 – Feb 2022Northfield Digital · Lahore
- Built and maintained 12 client-facing marketing sites using React, Next.js, and Tailwind; worked directly with design and content teams.
- Rewrote the shared CSS system across projects to use CSS custom properties, removing duplicate styles and simplifying colour changes from days to hours.
- Collaborated with the SEO lead to fix Core Web Vitals issues on three client sites; all three moved into Google's "Good" range for LCP within a month.
Projects
OpenSource Contribution — Prisma ORM
2023 – presentgithub.com/example-bilal/prisma-fixes
- Contributed two merged PRs to Prisma ORM — one fixing a TypeScript type mismatch and one adding documentation for an undocumented connection pool option.
Education
BSc Computer Science
2016 – 2020University of Karachi
Skills
- TypeScript
- JavaScript
- Node.js
- React
- PostgreSQL
- Playwright
- Docker
- Git
- AWS (basic)
What makes this developer resume work
1. The migration bullet shows technical + business impact
The migration bullet is the strongest on the resume because it ties technical work to a business metric. A PHP-to-Node.js migration could be described as "migrated the legacy service", which tells the reader almost nothing. Instead, Bilal's bullet shows: scope (4 months, legacy to modern stack), outcome (30% fewer bugs), and user impact (median load time cut in half). This is what senior engineers mean when they talk about "impact".
2. The bullets use specific technology names
"TypeScript", "Node.js", "PostgreSQL", "Playwright" — each bullet names the actual tools used. This matters both for human readers (who want to know what stack you've worked in) and for ATS parsing (which matches keywords). "Worked on backend services" tells neither reader anything.
3. Team-level work is described
Two bullets describe collaborative work — introducing a testing practice to the team, and mentoring junior developers. This signals seniority without claiming it. Many mid-level resumes are all about individual output; including team-level work distinguishes a candidate who's ready for the next level.
4. The open-source contribution is credible and small
Two merged PRs to a well-known open-source project is a real, verifiable contribution. It's small (not "I am a core contributor") but honest. Overselling open-source work — claiming to be a "maintainer" of a project you've submitted one PR to — is a common and easily checked lie. Keeping it modest makes it credible.
5. Education is compressed
Four years into a career, education can be a single line: degree, institution, dates. No GPA, no coursework, no final-year project. The work history is what matters now. This is the correct treatment of education for a mid-career resume.
6. Skills are ordered by relevance to the target role
TypeScript, JavaScript, Node.js, React — these are the primary technologies. Then comes PostgreSQL (relevant but secondary), Playwright (a specialty), Docker and Git (expected), and AWS (a bonus). This ordering helps a reader who scans only the first line of the skills section.
Common mistakes this example avoids
- Listing every technology ever touched. The skills section has 9 items. It could list 30; it doesn't. Everything listed is something Bilal can defend in an interview.
- Vague "backend developer" descriptions. Every bullet names specific technologies or quantifies an outcome.
- Pretending personal projects are work. The open-source contribution is under Projects, not Experience. Only paid work is under Experience.
- Inflated "senior" claims. The summary says "mid-senior" — honest for 4 years of experience. Claiming "senior" at 4 years is a red flag to many hiring managers.
- Metrics without context. "Reduced load time by 1.6s" is specific and helpful. "Improved performance dramatically" is not.
Related resources
Open the builder with the Tech Pro template — a single-column technical layout designed for developer resumes.