How to write a mechanical engineer resume
Updated 2026-09-02
A mechanical engineer’s resume is measured in parts that shipped: which part or mechanism was yours, how many were made, and which failure the tolerance stack and the analysis kept from reaching the customer. The person reading it has released drawings of their own and looks for three things: the part in your name, its process and volume, and the number that moved because of a decision you made. A row of CAD packages with no part behind it answers none of the three.
This page is about the metal and the plastic, not the electronics mounted on them and not the tool they sit inside. Board-level evidence belongs on the hardware engineer page; tool availability belongs on the equipment engineer page. Mechanical design proves itself with a drawing that released, a stack that closed, an FEA result a test agreed with, a mold that reached production after one steel change. The employers reading this resume in English are semiconductor equipment vendors, automotive tier-one suppliers, industrial-automation and consumer-hardware brands, and the hiring manager is usually the mechanical lead who signed the drawings. Every example here is in English because that is the output language, and every figure stays [N]: the microns, the cycle counts and the unit cost have to be numbers you measured or negotiated.
One thing the first sentence has to settle: which kind of mechanical engineer you are. Precision mechanisms and stages, structural and thermal analysis, plastic and sheet-metal product design, or test and validation. Openings are split along those lines, and a summary that claims all four is routed to none. What follows: the order of sections, a summary for each career stage, bullets sorted by competency, five weak lines and their rewrites, what earns a place in Skills, the terms a parser matches, the errors specific to this role, and the third question each claim leads to in the interview.
What a finished one looks like
Below is a complete sample for a fictional person, rendered as a real page by the product's own sheet and scored by the same rules engine the editor uses — the number is computed, not typed in. Every figure a bullet owes is left as [N], which is why the score stops under the cap. That is not a flaw in the example; it is the product's rule, demonstrated.
Hsin-Yu Chang
Education
- Designed the gearbox housing and drivetrain mounts for the university’s student racing car, cutting housing mass by [N]% through topology optimization while meeting the torsional-stiffness target on the first test
- Led the [N]-member chassis subteam at the student formula competition, the department’s best finish in [N] years
Experience
- Owned the mechanical design of a wafer-handling end-effector module from concept to first customer shipment, holding placement repeatability within [N] µm on [N] acceptance units and passing site acceptance on the first attempt
- Halved the module’s part count, from [N] to [N] machined parts, by merging a bracket stack into one five-axis-milled body, which took [N] weeks out of the supplier lead time and [N]% out of unit cost
- Eliminated a recurring alignment drift by rebuilding the tolerance stack around a GD&T datum scheme referenced to the wafer plane, replacing [N] positional callouts that had been stacking against one another
- Improved the stiffness of a [N] kg stage frame so its first natural frequency rose from [N] Hz to [N] Hz in FEA, confirmed within [N] Hz by a hammer test on the first article, without adding mass
- Designed the injection-molded bumper, chassis and battery door of a robot vacuum that shipped [N] thousand units, releasing all [N] tools with a single steel-safe change after first shots
- Doubled the cycle life of the bumper’s spring-return pivot in bump testing, from [N] thousand to [N] thousand cycles, by replacing a snap-fit hinge with a molded-in steel pin
- Resolved a wheel-arm field crack in [N] weeks by reproducing it in FEA as a stress concentration at a sharp internal corner and adding a [N] mm radius, with no recurrence across the next [N] thousand units
- Reduced enclosure cost by [$N] per unit by consolidating [N] sheet-metal brackets into one progressive-die stamping and moving the top cover from PC/ABS to glass-filled PP after a UV-aging test
Projects
- Built a tolerance-stack calculator with worst-case and Monte Carlo modes that [N] design teams now run before drawing release, cutting stack reviews from [N] days to [N] hours
Additional Information
Structure and section order
Single column, plain headings, no renders. The first reader is a parser and the second is a mechanical lead who has signed drawings; a rendered assembly on the sheet is blank space to the first and a distraction to the second. Renders and drawings go behind a portfolio link, where a person can open them.
The ordering rule: the shipped part first. What you designed, what it was made of, how it was made and how many were made are the spine of the page, and everything else is arranged around them. Entry-level candidates put the capstone mechanism and the internship part in that seat.
- 1Summary
Three sentences: your lane (mechanisms, structures and thermal, plastics and sheet metal, or validation), the product class, the part that shipped at the largest volume. The reader routes from here.
- 2Experience
Reverse chronological, one entry per product or machine. Each carries the part or subsystem you owned, its material and process, [N] units or [N] machines built, and one failure the design change removed. Most of the page.
- 3Part Record (optional)
One line per part: year, product class, process (machined, molded, stamped, welded), your role, the volume it reached. Every line will be asked about, so keep only the ones you can walk through drawing by drawing.
- 4Skills
CAD, analysis, manufacturing processes and test methods, grouped. The keyword table against the posting, holding only tools you have released a drawing from.
- 5Education
One or two lines once a part has shipped. Entry-level candidates put the capstone and any competition-team hardware here, with what it was built from and how it performed.
- 6Portfolio link (optional)
One line, one URL, at the end of the header. Consumer-hardware brands ask for it; semiconductor equipment vendors rarely do. Three parts with a sentence each beat thirty renders.
Summary examples by level
The summary is a ten-second routing decision for a mechanical lead: your lane, your product class, the part that shipped at the largest volume. One example per stage, figures left as [N] for you to fill.
Mechanical engineering graduate who designed the gearbox housing and drivetrain mounts for a student racing car, cutting housing mass by [N]% in topology optimization while meeting the torsional-stiffness target on the first test. Comfortable in SolidWorks and Ansys, and on a mill and a lathe. Looking for a design seat where the first drawing I release goes to a supplier.
At entry level the evidence is a mechanism that was built and measured: the mass it lost, the stiffness test it passed on the first run. The last sentence says which seat you want: one where the drawing actually reaches a supplier.
Mechanical engineer with [N] years designing precision mechanisms for semiconductor equipment and molded enclosures for consumer robotics. Owned a wafer-handling module from concept to first shipment, halved its part count, and closed a recurring alignment drift with a rebuilt GD&T datum scheme. Works best where a tolerance stack, an FEA result and a supplier’s capability have to agree before the drawing releases.
Mid-career routing needs the facts in view: two product classes, one module carried from concept to shipment, one part-count reduction, one stack rebuilt. The last sentence describes the working position: stack, analysis and supplier capability have to agree before release.
Senior mechanical engineer leading a [N]-person design group across [N] machine programs, owning tolerance policy, the FEA sign-off and the drawing-release gate. Cut design-caused rework to zero on the last [N] programs by making a closed tolerance stack and a matched analysis-to-test result conditions of release. Trains engineers to write drawings a supplier can quote without a phone call.
Senior evidence is what got written into the release conditions: a closed stack and a correlated analysis became gates. The last sentence describes the drawing quality you train into people: a supplier can quote it without calling.
Bullets grouped by competency
Four components in every bullet: a verb, a part in your name, a method, a result left as [N]. Unit counts, microns, kilograms and unit cost are the units a mechanical engineer states scale in. Whichever is missing stays blank.
Part and mechanism ownership
· Owned the mechanical design of a wafer-handling end-effector from concept to first customer shipment, holding placement repeatability within [N] µm on [N] acceptance units.
· Designed the injection-molded bumper, chassis and battery door of a robot vacuum that shipped [N] thousand units, releasing [N] tools with one steel-safe change after first shots.
· Engineered a [N]-axis inspection gantry with [N] µm straightness over [N] mm of travel, choosing crossed-roller guides over linear rails on a stiffness-per-cost comparison the customer accepted.
Tolerance analysis and GD&T
· Eliminated a recurring alignment drift by rebuilding the tolerance stack around a datum scheme referenced to the wafer plane, replacing [N] positional callouts that had been stacking against one another.
· Reduced the worst-case stack on a [N]-part optical mount from [N] µm to [N] µm by tightening one functional tolerance and opening [N] others, which cut the supplier’s quote by [N]% and removed shimming at assembly.
· Introduced Monte Carlo stack analysis on a [N]-piece sheet-metal enclosure, showing the [N] mm worst-case gap would appear on fewer than [N] in [N] thousand units and letting the team drop a machining step.
Structural and thermal analysis (FEA and CFD)
· Improved the stiffness of a [N] kg stage frame so its first natural frequency rose from [N] Hz to [N] Hz in FEA, confirmed within [N] Hz by a hammer test on the first article, without adding mass.
· Delivered the thermal design of a charging dock, holding the charger board under [N] °C at [N] °C ambient with a natural-convection chimney sized in CFD and verified in a climate chamber.
· Cut the mass of a robot-arm link by [N]% with topology optimization and a two-piece welded design, holding deflection at the tool point under [N] mm at full payload.
DFM, suppliers and cost
· Halved the part count of a machined module, from [N] to [N], by merging a bracket stack into one five-axis-milled body, which took [N] weeks out of the supplier lead time.
· Reduced enclosure cost by [$N] per unit by consolidating [N] sheet-metal brackets into one progressive-die stamping and moving the top cover from PC/ABS to glass-filled PP after a UV-aging test.
· Negotiated a [N]% price reduction on a family of [N] turned parts by walking the supplier’s floor, removing a grinding operation the drawing did not need and relaxing a surface finish no mating part touched.
Test and validation
· Doubled the cycle life of a bumper’s spring-return pivot in bump testing, from [N] thousand to [N] thousand cycles, by replacing a snap-fit hinge with a molded-in steel pin.
· Resolved a wheel-arm field crack in [N] weeks by reproducing it in FEA as a stress concentration at a sharp internal corner and adding a [N] mm radius, with no recurrence across the next [N] thousand units.
· Secured a first-run pass on the [N] g shock and random-vibration qualification by adding a constrained-layer damper to the bracket the pre-test FEA had flagged, saving a [N]-week retest.
Drawing release and design process
· Standardized the drawing template and GD&T conventions across [N] design teams, cutting supplier clarification requests from [N] to [N] per release.
· Led design reviews for [N] mechanical programs against a written checklist covering stack-ups, fastener torque, service access and DFM sign-off, so no drawing released with an open action.
· Built a tolerance-stack calculator with worst-case and Monte Carlo modes that [N] design teams now run before release, cutting stack reviews from [N] days to [N] hours.
Before and after
The same experience written two ways. Weak mechanical writing has fixed patterns: the software instead of the part, the whole machine instead of your subsystem, an analysis with no measurement beside it, a supplier meeting instead of a drawing change.
Responsible for mechanical design using SolidWorks.
Owned the mechanical design of a wafer-handling end-effector from concept to first shipment, [N] machined parts across [N] drawings, holding placement repeatability within [N] µm.
Why it works · “Responsible for” plus a CAD package says which chair you sat in. The rewrite names a mechanism, its part and drawing counts, and a performance figure you held.
Performed tolerance analysis on assemblies.
Eliminated a recurring alignment drift by rebuilding the stack around a datum scheme on the wafer plane, replacing [N] positional callouts that had been stacking against one another.
Why it works · “Performed” is an action with no result attached. The rewrite names the failure (drift), the method (a datum scheme) and what the stack replaced. An interviewer can ask straight away how you chose the datums.
Used FEA to optimize the frame design.
Improved the stiffness of a [N] kg stage frame so its first natural frequency rose from [N] Hz to [N] Hz in FEA, confirmed within [N] Hz by a hammer test, without adding mass.
Why it works · “Used FEA” gives the credit to the software. The rewrite has the metric (frequency), the constraint (no added mass) and the test that agreed with the model. An analysis counts only when a measurement stands next to it.
Worked with suppliers to reduce costs.
Negotiated a [N]% price cut on a family of [N] turned parts by removing a grinding operation the drawing did not need and relaxing a surface finish no mating part touched.
Why it works · “Worked with” contains no decision. The rewrite has two drawing changes you made and the price they bought. Cost reduction on a mechanical resume is a drawing change, not a meeting.
Involved in product testing and validation.
Doubled the cycle life of a bumper pivot in bump testing, from [N] thousand to [N] thousand cycles, by replacing a snap-fit hinge with a molded-in steel pin.
Why it works · “Involved in” is a bystander’s phrase. The rewrite names the test, the before-and-after, and the design change that moved it. Validation is worth writing only as the failure it found and the fix it confirmed.
What belongs in the skills section
The person reading this section has signed drawings. Every term has to survive one question: which drawing did you release with it?
Worth the space
SolidWorks · Creo · NX · CATIA · GD&T (ASME Y14.5 / ISO GPS) · Tolerance stack-up
FEA (Ansys, Abaqus) · CFD · Modal & vibration · Thermal · Topology optimization · Hand calculations
CNC machining · Injection molding · Sheet metal · Die casting · Welding · Additive
DVT / reliability testing · Shock & vibration · Climate chamber · DFM / DFA · FMEA · ECO / PLM
Cut these
- Every CAD package ever opened · The reader asks which one you released a drawing from. Keep the two you have shipped with; delete the one from a university lab.
- “Mechanical design” as a skill · That is the job title. Its evidence is a part that shipped, and it belongs in Experience with a unit count beside it.
- “Problem solving” and “teamwork” · Every resume claims them. In mechanical work, problem solving is a root cause you found and the drawing change that removed it. Write that as a bullet.
- Home 3D printing and garage machining as professional skills · A bracket printed at home is not a released drawing. If the role is hands-on, keep shop skills to one line, and keep the printer out of Skills.
- Internal part numbers and program codenames · They mean nothing outside the building and may sit under an NDA. Describe the part by class and process: a five-axis-milled end-effector body for a wafer-handling module.
ATS keywords
The parser counts keywords before the mechanical lead reads a sentence. These are the terms that recur in postings for this role, by category, spelled the way US postings spell them.
List only the tools you have released a drawing from and the processes you have taken a part through. The mechanical lead will ask which part and which program, and one keyword you cannot answer for costs more than the blank would have. Stacking terms does not make the parser count twice, and the person after it reads noise.
The evidence that is not on the resume
Most of what a mechanical engineer produces belongs to the employer. The part files, the drawings, the specification and the test reports stay in someone else’s PLM the day you leave. So the question for this role is not whether you have a portfolio. It is which things you are entitled to show, and which you can only point at with one line. A mechanical lead checks two kinds of evidence: what can be looked up — patents, licences, certificate numbers — and what can be seen, which is a product on sale or a mechanism you built yourself.
- The CAD file is not yours to send
Part files, STEP exports, a drawing with the title block still on it, a customer specification: all of it belongs to the employer or the customer, and none of it becomes yours by sitting on your laptop. A .sldprt attached to an application tells the reader exactly what you will send on the day you leave them. Point at the work by class instead — an end-effector module for a wafer-handling system. No files, no screenshots, no part numbers.
- The first thing opened is a product, not a link
The order is predictable. A mechanical lead looks first for the product or machine class your part shipped inside, then for a patent, then for a portfolio PDF, and only then for a capstone or a competition car. A consumer product on a shelf is already public, so naming the product class and the years puts something in the reader’s hands without you attaching anything. That is the work the line shipped [N] thousand units is doing in your Experience section.
- A patent is the line that survives being checked
A published patent carries your name as an inventor, the assignee, the filing date and a number anyone can search. Almost nothing else on a mechanical resume verifies itself that way. Write it as one line: Patents: US [N], inventor — precision stage mechanism, assigned to employer. If the application has not published yet, give no number and write patent pending, filed [Month Year]. If it was abandoned, or you came off the inventor list, leave it out. The register is public, and a number that disagrees with your page costs more than the blank would have.
- A licence needs its jurisdiction, its number and its renewal date
In the US the route is the FE exam, EIT status, then a PE licence issued by a state board, and every board publishes a lookup anyone can run. Taiwan issues its mechanical engineer licence through the national professional examination; the UK route is CEng through IMechE. Write it as Licensed Professional Engineer (Mechanical), [State] #[N], renewed [Month Year]. Dropping the state or the number drops exactly the half that could have been verified. If it has lapsed, write inactive and the year.
- Whether a licence matters at all depends on the seat
A stamp is required for work that gets stamped: building services and HVAC, pressure vessels and piping, structures, plant, and consulting practices that issue drawings to an owner. Consumer products, semiconductor equipment and automotive design almost never ask, and leading with a PE on one of those applications reads as a resume sent to the wrong industry. When a posting wants one and you do not have it, write the stage as a fact: FE / EIT certified ([State]); PE exam scheduled [Month Year]. A stage can be checked. “PE eligible” is a hedge.
- A CAD or GD&T certification counts once it has a number
Vendor certifications such as CSWP and CSWE issue a certificate ID the vendor’s own directory will confirm. ASME’s GDTP certification is examined and comes at two levels, Technologist and Senior. A two-day GD&T course is training, and the resume should use that word for it. Put the level and the ID together: Certified SolidWorks Professional (CSWP), cert. [N].
- A portfolio PDF is three parts, one page each
Consumer-hardware and robotics employers ask for a link; semiconductor equipment vendors mostly do not. When it is wanted, send three pages: one part per page, an isometric, a drawing view with the datum scheme and the tolerances visible, and one measured result. A deck of renders answers a different question — the reader wants to know whether you can dimension a part, not whether you can light a scene. Everything on those pages has to be yours to show: the competition car, the capstone, a personal project, open hardware, or the exterior of something already on sale.
- When there is nothing to show, take the link out
An empty personal site, three downloaded STLs, a URL that no longer resolves: each of those gets clicked, and a 404 in your header costs more than a header with no link in it. If every part you have touched sits under an NDA, say so in one line and carry no URL. Bring a physical part to the onsite instead — one machined or molded piece, and a page you wrote on the trade-offs behind it. A GitHub link earns its place here only if you wrote tooling: a stack calculator, a test-rig logger, a script that pulls measurements back against the model. An account holding two STL files argues against you.
Common mistakes on mechanical engineer resumes
- 1A row of CAD packages with no part in your name
SolidWorks, Creo and NX are on every mechanical resume. What is yours is the part: which product, which material and process, how many were made, which failure the design removed.
- 2The whole machine’s specification written as your contribution
“Designed a lithography stage” describes the company’s product. Write the subsystem you owned: the end-effector, the frame, the cable carrier. A small scope with a number beats a large scope without one.
- 3Tolerances described as tight rather than as a stack
“Designed parts to tight tolerances” says you typed a small number. Write the stack: how many parts, what the functional requirement was, what the worst case came to, and which tolerance you opened or tightened to close it.
- 4An analysis with no measurement beside it
An FEA result on its own is a picture. Write the measurement that agreed with it: a hammer test, a strain gauge, a thermocouple, and how far apart the two came out.
- 5Supplier work written as attendance
“Coordinated with suppliers” shows no decision. Write the drawing change and what it bought: the operation removed, the tolerance opened, the price or lead time that fell.
- 6No lane in the first sentence
Mechanisms, structures and thermal, plastics and sheet metal, or validation. Openings are split that way, and a summary claiming all four is routed to none of them.
- 7Program codenames and customer names on the page
Contract and equipment work is usually under NDA. Describe by class: an end-effector module for a semiconductor wafer-handling system, a molded chassis for a robot vacuum.
The follow-up each claim invites
Every follow-up in this field separates one thing: did you design the part, or did you draw someone else’s concept? Before an [N] goes on the page, think about the third question it leads to.
Owned the mechanical design of the module from concept to first shipment.
Which requirements did you write and which did you inherit? Name one design decision you would reverse today, and what it cost at the time.
“Owned” means you can defend the trade-offs. Bring one: why crossed-roller guides over linear rails, what it cost in budget or schedule, what you learned. If the concept was inherited, say so and describe what you changed.
Eliminated a recurring alignment drift by rebuilding the tolerance stack.
What were the datums before and after? Why did the old stack drift rather than fail at assembly? How did you prove the design change fixed it and not a supplier’s process change?
Have both datum schemes in your head, the worst-case and statistical numbers for each, and the measurement on [N] units that separated the design fix from a supplier fix.
Halved the part count of the module.
What did the merged part cost against the parts it replaced? What did five-axis milling do to the supplier pool and to lead time? Which tolerance got harder?
Part-count reduction always trades something away. Bring the cost comparison, the supplier count before and after, and the one tolerance that moved from a fixture onto the machine.
Improved stiffness so the first natural frequency rose from [N] Hz to [N] Hz.
What were the boundary conditions in the model, and how did you check them? How far was the hammer test from the model, and what explained the gap?
An analysis claim is judged on its boundary conditions and its correlation. Say what you fixed, what you sprung, and the mode shape you saw on the bench, and the number is yours.
Doubled the cycle life of the pivot in bump testing.
What was the failure mode of the old design, and how many units did you test? Was the profile from a standard or written in-house? Did the field-return rate move?
Bring the failure photo, the sample size, the test spec and the return curve after the change. Without a sample size, a doubling is one lucky unit.
FAQ
My parts were designed for a customer’s machine under NDA. How much can I write?
Class and process, yes; customer, codename and unreleased specifications, no. “An end-effector module for a wafer-handling system” places you for a peer and names nobody. Volumes and performance can be relative, or left as [N].
When unsure, describe one level up: the module class rather than the machine, the machine class rather than the customer.
What changes when a machine-builder or contract-manufacturer background is written for a semiconductor equipment vendor?
The unit of evidence. A machine builder’s resume lists machines and years; the vendor wants the subsystem you owned, the tolerance and stiffness it met, the analysis a test agreed with, and drawings a supplier could quote without a question.
Second, the language. Design reviews, FMEAs and supplier drawings at a vendor are in English, and the resume is the first sample of yours they see.
I only have a capstone mechanism and one internship. Does that count as design experience?
It does if it was built and measured. Write what it was made from, how it was made, what it was tested against, and what you would change. A racing-car gearbox housing with a mass figure and a stiffness test is real evidence at entry level.
Internship work you followed is labelled as support. Write the part you did with your own hands: the drawing, the fixture, the measurement.
Should the resume carry a portfolio link?
For consumer-hardware and robotics brands, yes, one line in the header. For semiconductor equipment vendors and automotive suppliers, usually not, because most of the work sits under NDA anyway.
Three parts with one sentence each, a render and a drawing view, beat thirty renders. Anything on it must be yours to show.
I do both mechanical and electrical work at a small company. Which do I lead with?
The lane of the posting. For a mechanical role, lead with parts, tolerances, analysis and validation, and compress board and firmware work into one line of cross-domain evidence. For an electronics role, reverse it.
Keep the two apart on the page. A bullet that mixes a bracket and a firmware fix leaves the reader unsure which half was yours.
Turn your drawings into a resume a mechanical lead can question
Describe your parts in plain language: what they were made from, how they were made, how many, what the stack or the test found. The Tech lens rewrites them into English bullets at the level of this page. The 0–100 score comes from a rules engine and cannot change between runs of the same draft, and every missing micron, cycle count and unit cost stays a yellow [N] until your own drawings and test reports fill it.
Try 2 free drafts