PWS
All free guides

Get shortlisted

50 Action Verbs For Tech Resumes

Priya, recruiter, 1,340 resumes, six seconds each. Her eye runs down the left edge of the page and catches the first word of each line . "Worked", "Responsible", "Helped". Next resume. "Built", "Reduced", "Deployed". She slows down.

9 min readFree, no email neededUpdated 11 September 2026

Step 1 · Resume

The first word

👀

Priya, recruiter, 1,340 resumes, six seconds each. Her eye runs down the left edge of the page and catches the first word of each line. "Worked", "Responsible", "Helped". Next resume. "Built", "Reduced", "Deployed". She slows down.

A bullet has three parts: did X, measured by Y, by doing Z. The verb is X. It tells Priya what kind of person you are before she reads a single number.

Pick the verb by asking one question about what you actually did. The answer sends you to the right page.

Did you make a thing that did not exist?BUILT · page 4
Did a number go up or down because of you?IMPROVED · page 5
Did a manual, repeated task disappear?AUTOMATED · page 6
Did you find something out and act on it?ANALYSED · page 7
Did other people do things because of you?LED · page 8
Did it reach real users on a real server?SHIPPED · page 9

Every example below is written for a fresher. Change the numbers to yours. Keep the shape.

Group 1 · Proves you can make things

Built

Built a hostel mess-menu web app used by 220 students, by scraping the weekly PDF into a React front end with a Node API.
Developed a REST API for a college event portal that handled 1,200 registrations in 3 days, using Express, MongoDB and JWT login.
Designed a 9-table PostgreSQL schema for a library system with zero duplicate records across 4,000 books, using foreign keys and unique indexes.
Implemented Razorpay test-mode payments in a canteen ordering app, completing 150 mock orders with 0 failed callbacks, using webhooks and retries.
Created a Chrome extension that hides LeetCode difficulty tags, installed by 80 classmates, using vanilla JavaScript and the Storage API.
Engineered a rate limiter that capped each IP at 100 requests a minute, cutting bot hits on the login page by 90%, using Redis and Express middleware.
Prototyped a voice-note-to-text app in 48 hours at a college hackathon, placing 2nd of 60 teams, using Flutter and the Whisper API.
Integrated Google Sheets as the database for a club attendance form, syncing 500 entries with no manual copying, using Apps Script and the Sheets API.
Wrote 60 unit tests covering 85% of a Django expense tracker, catching 7 bugs before the demo, using pytest and coverage.
Configured Nginx and PM2 on a ₹500-a-month VPS to serve 3 Node apps with 99.5% uptime over 4 months, with free SSL from Let's Encrypt.
Group 2 · Proves you can make things better

Improved

Reduced page load from 4.2 s to 1.1 s on a portfolio site by lazy-loading images and caching API responses in React.
Improved search on a notes app from 60% to 92% relevant results across 50 test queries, by adding fuzzy matching with Fuse.js.
Optimised a monthly report query from 6 s to 0.4 s by adding a composite index and removing a nested subquery in PostgreSQL.
Cut the Docker image of a Flask app from 1.1 GB to 180 MB by switching to a slim base image and a multi-stage build.
Increased test coverage from 20% to 78% on a Spring Boot backend by writing 45 JUnit tests for the service layer.
Sped up a data-cleaning script from 40 minutes to 3 minutes on 2 lakh rows by replacing Python loops with pandas vector operations.
Refactored a 900-line Java file into 6 classes, cutting the time to fix a bug from 2 hours to 20 minutes, with all 30 tests still passing.
Fixed a race condition that double-booked 1 in 40 hostel room slots, by wrapping the booking in a PostgreSQL transaction with row locking.
Simplified sign-up from 9 fields to 3, raising form completion from 45% to 80% across 300 users, by moving optional details to a later step.
Scaled a quiz app from 50 to 1,000 concurrent players during the college fest by moving sessions to Redis and adding a second Node instance.
Group 3 · Proves you remove boring work

Automated

Automated the college notice board with a Telegram bot used by 300 students, with zero missed notices in 3 months, using Python and BeautifulSoup.
Scripted a bash tool that set up 30 lab machines in 10 minutes instead of a full day, installing Java, VS Code and Git from one file.
Scheduled a nightly cron job that backed up a 2 GB MySQL database to Google Drive, restoring cleanly in 2 drills, using mysqldump and rclone.
Streamlined placement-cell resume collection from 400 separate emails to one Google Form and script, saving the coordinator 6 hours a week.
Eliminated 200 manual attendance entries a week by scanning a QR code at the classroom door, using a Flask API and a phone camera.
Generated 1,500 personalised event certificates in 4 minutes from a CSV, replacing 2 days of manual work, using Python and ReportLab.
Replaced a manual Excel fee-tracking sheet with a Django app used by 3 office staff, cutting month-end reconciliation from 5 days to 1.
Consolidated 4 department WhatsApp groups into one Discord bot posting 120 announcements a month to role-based channels, using discord.py.

The number to look for: hours saved per week, or entries no longer typed by hand. Time the manual way once with a stopwatch. That is your Y.

Group 4 · Proves you think before you type

Analysed

Analysed 10,000 LeetCode submission logs to find the 5 most-failed patterns, then built a practice list that raised the club's weekly solve rate by 30%, using pandas.
Measured latency across 20 API endpoints with k6, found 3 above 800 ms, and brought them under 200 ms with response caching.
Tested a payment flow against 40 edge cases (expired cards, timeouts, double clicks), finding 6 bugs before launch, using Postman and Jest.
Debugged a memory leak that crashed a Node server every 6 hours, tracing it to an unclosed database connection with Chrome DevTools heap snapshots.
Benchmarked 3 sorting approaches on 1 million records, picked the one 4× faster, and wrote up the results for the team, using Python timeit.
Profiled a React app and found one component re-rendering 40 times per keystroke; cut it to 1 with useMemo and a debounced input.
Identified that 70% of app crashes came from one missing null check on the login screen, by reading 500 Crashlytics logs, and fixed it in one release.
Evaluated 4 models on a 5,000-row crop-price dataset, choosing XGBoost at 88% accuracy over a 71% baseline, using scikit-learn.

Notice: every one ends with an action. Analysis that changed nothing is a report, not a bullet.

Group 5 · Proves people can work with you

Led / Collaborated

Led a team of 4 to build a lost-and-found portal for 2,000 hostel students, delivering in 6 weeks with weekly demos, on the MERN stack.
Mentored 25 first-year students in Python over 8 weekends through the coding club, with 20 of them finishing a working project.
Coordinated a 36-hour hackathon for 300 participants, managing 12 volunteers and a ₹40,000 budget with zero schedule slips.
Presented a campus-bus tracking project to 5 faculty and 2 industry judges, winning 1st of 40 teams.
Reviewed 30 pull requests from 6 teammates on a club project, catching 12 bugs before merge and writing the shared PR checklist.
Documented a 15-endpoint API with request and response examples in Swagger, cutting new-member onboarding from 3 days to half a day.
Organised a weekly DSA study group of 15 students for 4 months, with 9 members crossing 200 LeetCode problems.
Trained 3 office staff on a new fee-tracking app in two 1-hour sessions, with zero support calls in the following month.

The trap: "Led" with no team size is a red flag. Always say how many people, and what they delivered.

Group 6 · Proves it left your laptop

Shipped / Deployed

Shipped 12 feature updates in 3 months to an expense-splitting app with 40 active users, based on feedback collected inside the app.
Deployed a Spring Boot and React app on AWS EC2 with Nginx and HTTPS, serving 500 users with 99.6% uptime over 2 months.
Launched a hostel laundry-booking app on the Play Store, reaching 350 installs and a 4.4 rating in the first month, using Flutter and Firebase.
Released an open-source npm package for Indian phone-number validation, reaching 1,200 weekly downloads and 3 outside contributors.
Migrated a college club website from PHP to Next.js on Vercel, cutting hosting cost from ₹3,000 to ₹0 a year and load time by 60%.
Published an 8-post blog series on Git for beginners, read 15,000 times and linked from 2 college course pages.
🚀

Priya searches every resume for one thing before she reads it: a live link. "Deployed", "Launched" and "Shipped" tell her it exists before she clicks. That is why this group, though the smallest, is the one to use on your best project.

Verbs to delete

These four phrases start most fresher bullets. Each one hides what you actually did. Find them, replace them.

Responsible for

Responsible for the backend of the college fest website.

Rewrite

Built the backend for the college fest website, handling 1,200 registrations in 3 days, using Express and MongoDB.

Worked on

Worked on a machine learning project for crop price prediction.

Rewrite

Evaluated 4 models on a 5,000-row crop-price dataset, choosing XGBoost at 88% accuracy, using scikit-learn.

Helped with

Helped with testing the payment feature.

Rewrite

Tested the payment flow against 40 edge cases, finding 6 bugs before launch, using Postman and Jest.

Involved in

Involved in organising the college hackathon.

Rewrite

Coordinated a 36-hour hackathon for 300 participants, managing 12 volunteers and a ₹40,000 budget.

Also delete: "Was part of", "Participated in", "Assisted in", "Learned", "Exposure to", "Familiar with". If your only honest verb is one of these, the line does not belong on the resume.

Verb tense rules

Past tense for anything finished. Present tense only for something you are still doing today.

Finished projectPast. Built a hostel laundry app used by 350 students.
Finished internshipPast, even if it ended last week. Reduced API latency by 60% at XYZ Labs.
Still running, you still maintain itPresent. Maintain a Discord bot for 400 club members; ship a fix within 24 hours of every report.
Still running, you moved onPast verb, present result. Built a notice-board bot in 2024; still used by 300 students.
Current internship or jobPresent for the role, past for finished tasks inside it. Own the billing service; migrated it to PostgreSQL in June.
Hackathon, one weekendPast. Prototyped and presented in 48 hours.

Three more rules

  • One tense per bullet. "Built and maintaining" is wrong; "Built, now maintaining" is fine.
  • Never "-ing" as the first word. "Building an app" reads as unfinished. Use "Built" or "Maintain".
  • No "I", no "my". The verb comes first: "Built", not "I built".

Want this on your phone?

Everything above, as a PDF built to read on a phone the morning of the interview. It costs nothing — we ask for an email so we can send it, and that is all.

Get the PDF, freeSee every guide