Skip to content
Course contents

Lesson 23

Writing Your Resume in English

5 min read

Why this matters

A recruiter usually spends less than a minute on your resume before deciding whether to call you. If your English is unclear or your bullet points only list duties, strong experience can look average. A few simple writing patterns make your work easy to scan and easy to believe.

The core skill

The bullet point formula

Each bullet point should show what you did and why it mattered. A simple formula:

Action verb + what you did + result (with a number if possible)

Compare these two bullets for the same work:

Weak:   Responsible for the checkout page.
Strong: Rebuilt the checkout page in React, cutting load time by 40%
        and raising completed orders by 12%.

The weak version describes a job title. The strong version describes an achievement. If you don't have exact numbers, use honest estimates or describe the scale: "used by 30,000 daily users", "across 4 teams", "in 6 weeks".

Start with a strong verb, and drop "I"

English resumes have a special style. You don't write I, and you don't use full sentences. Each bullet starts directly with a verb:

Not this: I was working on migrating our services to Kubernetes.
This:     Migrated 14 services to Kubernetes, reducing hosting costs by 25%.

Use the past tense for previous jobs (built, led, reduced). For your current job, you can use the present tense (build, lead, maintain) or the past tense for finished projects. Choose one style per job and stay consistent.

Good verbs for developers:

  • Building: built, developed, designed, implemented, launched
  • Improving: improved, optimized, reduced, refactored, automated
  • Leading: led, mentored, coordinated, introduced, drove
  • Fixing: debugged, resolved, stabilized, migrated

Avoid weak openings like responsible for, worked on, helped with and was involved in. They hide what you actually did.

The summary at the top

Many English resumes start with a short summary of two or three lines. Write it without I, and focus on what you offer:

Full-stack developer with 6 years of experience building web apps in
React and Node.js. Focused on performance and clean, tested code.
Looking for a senior role on a product team.

Keep it specific. "Hard-working team player passionate about technology" could describe anyone, so it tells the recruiter nothing.

Skills and keywords

Many companies use software called an ATS (Applicant Tracking System) to filter resumes by keywords. Use the exact names from the job post, and write them correctly:

Languages:  TypeScript, JavaScript, Python, SQL
Frameworks: React, Next.js, Node.js, Express
Tools:      PostgreSQL, Docker, AWS, GitHub Actions

Check capital letters: it's JavaScript, not Javascript, and PostgreSQL, not postgres SQL. Small errors here look careless to a technical reader.

Useful phrases

Showing results

  • Reduced page load time by 40%.
  • Increased test coverage from 35% to 80%.
  • Saved the team around 5 hours per week by automating releases.
  • Cut cloud costs by $2,000 per month.

Showing scale and ownership

  • Led a team of 4 developers to deliver a new mobile app.
  • Owned the payments service end to end. (End to end means "from start to finish, all parts".)
  • Built a reporting dashboard used by 200+ internal users.

Showing collaboration

  • Worked closely with designers and product managers to ...
  • Mentored 3 junior developers through their first year.
  • Introduced code review guidelines across 3 teams.

Common mistakes

"Responsible for developing new features." Correct: "Developed 15+ features for the customer portal, including search and notifications." "Responsible for" describes a duty, not an achievement. Start with the verb.

"Improved the performance." Correct: "Improved API response time from 800 ms to 200 ms." Without a number or detail, the reader can't tell if the improvement was big or small.

"Have experience in React, Node.js and etc." Correct: "Have experience in React, Node.js and TypeScript." Etc. already means "and other things", so "and etc." is wrong. On a resume, list the real skills instead of using etc.

"I developed a mobile app." Correct: "Developed a mobile app ..." English resumes leave out I. Every bullet starts with the verb.

Formal vs. casual

Your resume is always formal, but formal doesn't mean complicated. Compare:

  • Too casual: "Did a ton of backend stuff and fixed loads of bugs."
  • Too complicated: "Was tasked with the facilitation of the optimization of backend processes."
  • Just right: "Optimized backend jobs, cutting nightly processing time from 3 hours to 40 minutes."

Short, clear words with specific details sound the most professional.

Exercise

Take your current or most recent job and write three resume bullet points about it.

  1. Pick three things you did: a feature you built, a problem you fixed, and something you improved.
  2. Write each one with the formula: action verb + what you did + result.
  3. Add a number or a sense of scale to each bullet.
  4. Check that no bullet starts with I, responsible for or worked on.

Hint: if you can't remember numbers, look at old pull requests, release notes, tickets or monitoring dashboards. They often have the data you need, such as how many users, how much faster, or how many hours saved.

Recap

  • Use the formula: action verb + what you did + result.
  • Start every bullet with a strong verb, and leave out I.
  • Add numbers or scale wherever you honestly can.
  • Use the exact skill names from the job post, spelled correctly.
  • Keep the language simple and specific. Clear beats impressive.