How to write a developer resume that gets interviews

A resume (or CV) has one job: to get you a conversation. Recruiters and hiring managers often spend only a few seconds on a first scan, and many companies use an applicant tracking system (ATS) to store and search resumes. A clear, honest, well-organised document wins.

Resume or CV?

In many countries resume means a short (usually one page, up to two for experienced people) summary tailored to a job, while CV can mean a longer academic document. In Bangladesh and some other places "CV" is used for the same job-hunting document. Follow the format the employer or country expects, and check the job post.

Basic rules

• One page for freshers and early-career developers. Two pages at most with long experience.
• Reverse chronological order: newest first.
• Simple, clean layout: one column, consistent fonts, clear headings, enough white space.
• Tailor it to each job. Move the most relevant skills and projects to the top.
• Save as PDF unless told otherwise. Name it clearly, such as Firstname-Lastname-Resume.pdf.
• No lies. Interviewers will test anything you claim.

Structure that works

1. Header

Name, city and country, email, phone, and links to GitHub, LinkedIn and a portfolio. Use a professional email address. A photo, age, religion and marital status are usually not needed (follow local norms, but many international employers prefer not to see them).

2. Short summary (2 to 3 lines, optional)

Who you are, your main skills and what you are looking for.

Backend developer with experience building REST APIs in Node.js and PostgreSQL. Built and deployed three full-stack projects. Looking for a junior backend role.

3. Skills

Group them so they are quick to scan:

• Languages: JavaScript, TypeScript, Python, SQL
• Frameworks: Node.js, Express, React
• Databases: PostgreSQL, Redis
• Tools: Git, Docker, Linux, GitHub Actions

List only skills you could discuss in an interview. Avoid skill bars and percentages ("Python 80%"), which mean nothing.

4. Experience

For each role: title, company, dates, and 3 to 5 bullet points about achievements, not duties.

5. Projects (very important for freshers)

Pick 2 to 4 strong projects. For each: name, link (GitHub and live demo), the tech used, and bullets on what it does and the result.

6. Education

Degree, institution, dates, relevant coursework or results if strong. Certificates only if relevant.

7. Optional: open source contributions, competitions and hackathons, publications, volunteering, languages.

Writing bullet points that show impact

Weak bullets describe duties:

• "Worked on the backend of an e-commerce site."

Strong bullets show what you did, how, and the result, using an action verb and a number if you honestly can:

• "Built a REST API with Node.js and PostgreSQL serving 12 endpoints, covered by 40 automated tests."
• "Reduced page load time by 35% by adding caching and compressing images."
• "Automated deployment with GitHub Actions, cutting release time from 30 minutes to 5."
• "Designed a database schema for orders and payments, handling 1,000 test transactions without errors."

A handy formula: Action verb + what + how/tools + result. Start with verbs such as built, designed, improved, reduced, automated, led, launched, fixed.

Use real numbers only. If you do not have measurements, describe scope instead (for example, number of features, users, endpoints or tests).

For freshers with no experience

• Lead with projects and skills, then education.
• Show deployed work and GitHub repositories with clear READMEs.
• Include internships, freelancing, open source, hackathons and relevant coursework.
• Describe projects like work: the problem, your solution and the result.

ATS-friendly tips

• Use standard headings (Experience, Education, Skills, Projects).
• Avoid tables, text boxes, images and unusual fonts for key content.
• Use the keywords from the job description where they are true for you (for example "REST API", "PostgreSQL", "CI/CD").
• Spell out acronyms at least once.
• Do not hide keywords in white text. It is detected and looks dishonest.

Common mistakes

• A long, dense resume with every task you ever did.
• Typos and inconsistent formatting. Proofread carefully, and ask a friend to read it.
• A vague objective such as "seeking a challenging position".
• Listing duties instead of achievements.
• Broken links and empty GitHub profiles. Check every link.
• Using the same resume for every job.
• Including every technology you have ever seen. Focus on your real strengths.

Final checklist

1. Fits one page, easy to scan.
2. Contact details and links work.
3. Top third shows your most relevant skills and projects.
4. Bullets show impact with true numbers.
5. Tailored keywords from the job post.
6. No spelling mistakes, saved as a clear PDF.
7. You can talk about every line in an interview.

Takeaway: keep it short, clear and honest. Lead with your strongest projects and skills, write impact-focused bullets, tailor it to each job and check every detail.

---

Career series, Part 1 (getting hired): 1 of 5.