Skip to the article
Conxfolio
Example · Engineering

A mechanical engineer résumé example, counted in parts and claims

One complete mechanical engineer résumé, written out in full. The person is invented. The reading and the score come from the product itself.

— part count down is a result. cad software is not.

The mechanical engineer example résumé drawn as a complete page in the Nexus design: name, summary, the roles with their bullet lines, education and a skills row
The example below, drawn by the builder's own renderer in the Nexus design. The picture was taken by pressing this page's own Use this example door and photographing what the editor rendered.

Mechanical engineering résumés fill up with software names and project titles, and a design manager learns almost nothing from either. This example is written out in full so you can read a page of results, then put through the tools here so you can see what a parser stores. The candidate is invented. Alessia Krogsgaard-Neve does not exist, neither employer exists, and every figure was chosen to demonstrate a shape.

The example, in full

An invented person. Not a real document, and not yours.

Alessia Krogsgaard-Neve
Mechanical Design Engineer
Turin, Italy · [email protected] · +39 011 555 0148

Summary
Mechanical design engineer with eight years on packaging machinery and pumps. Works on tolerances, supplier drawings and the part that fails on the third prototype.

Experience

Senior Mechanical Engineer · Valdarno Machine Works, Turin · 2021 to present

  • Led the design of 4 packaging machines now running on 30 customer sites.
  • Cut warranty claims on the flagship machine by 46% by redesigning 2 wear assemblies.
  • Reduced part count on a filling head from 61 to 38 and cut its cost by 24%.
  • Ran design reviews with 6 suppliers and released 320 drawings in 2 years.

Mechanical Engineer · Bramfell Pumps, Brescia · 2017 to 2021

  • Designed 12 pump variants across 3 product families to a shared component set.
  • Completed 40 finite element studies and validated 9 of them on the test rig.
  • Cut prototype lead time from 14 weeks to 9 by standardising 20 purchased parts.

Education
MSc Mechanical Engineering · Politecnico della Dora, Turin · 2012 to 2017

Skills
mechanical design, SolidWorks, GD and T, finite element analysis, design for manufacture, tolerance stacks, supplier drawings, test rig validation, technical documentation, root cause analysis

Languages
Italian · native · English · C1 · German · B1

Part count, cost, warranty

Part count on a filling head from 61 to 38, with cost down 24%. Warranty claims on the flagship machine down 46% after two wear assemblies were redesigned. Those are the two numbers that describe a mechanical designer, because one is what the drawing achieved and the other is what happened when customers used it.

Four machines running on thirty customer sites is the scale line. It says the designs were built and sold, which is a different claim from designs that were completed.

Validation is the honest half

Forty finite element studies, nine of them validated on the test rig. The ratio is the point again. An engineer who reports forty analyses and nine rig validations is telling you they know the difference between a model and a machine, and that is the conversation an interviewer wants.

The standardisation line is the commercial one: prototype lead time from fourteen weeks to nine by standardising twenty purchased parts. Purchasing, design and programme in a single sentence.

What the reading found

The door on this page hands the document to the résumé builder as plain text, through the same import an uploaded file goes through, and the review shows each field beside the line it came from. Here the completeness pass found four readable sections, 116 words of experience evidence and ten distinct skills, with three languages in their own section.

The Conxfolio import review after the door opened, showing Alessia Krogsgaard-Neve's example read into fields beside the rendered page, with the line saying it is an example
The real import review, opened by this page's own door. It names Alessia Krogsgaard-Neve as invented before anything is saved, and it shows every field beside the line it came from.

No language model is used. The readers are deterministic functions with their own rules, every string they emit is checked in code to be a span of the document, and a field that fails that check is dropped and counted.

What the checker scored it

The same import review on a 390 pixel phone screen, with the example notice above the accept button
The same door on a phone. Nothing is withheld on the small screen: the notice, the reading and the accept button are all there.

Ninety-seven out of 100, with one improvement remaining worth 8 points. The arithmetic is 100 × 30% + 100 × 30% + 92 × 40% = 97, explained in the article on the score. Seven action-led lines, five of them measurable, seven lines of depth, and 198 readable words against a band opening at 250.

Two roles in eight years is a normal engineering career and a short page. Run your own through the ATS checker and the same rule will apply in the same words, with the readable word count printed rather than implied.

What this example leaves off

No CAD version numbers, no list of every material worked with and no customer names. A design manager assumes the software and reads the part counts, the cost changes and the warranty figures.

Patent numbers are left off unless they are granted and yours to name. A pending application is a claim a reader cannot check, and a granted patent with its number is worth one line rather than a section.

What to change for your own

Change the product. Automotive, medical devices, aerospace and process plant all use this shape with different standards and different failure modes. Then put in your own part counts, cost reductions, warranty changes and validation records.

Keep the supplier coordination line. Keep the languages if you work with foreign suppliers, because on this job they are a working tool. The guide on experience bullets covers the construction, the design gallery holds 37 layouts, and the electrical engineer example, the civil engineer example and the architect example sit beside this one.

Write yours beside it

Opens the builder with Alessia's example loaded, saved as its own entry in the Nexus design. Replace every line with your own. Free, no account.

Use this exampleCheck a résumé instead

Questions

Is Alessia Krogsgaard-Neve a real engineer
No. She is invented for this page, and so are Valdarno Machine Works and Bramfell Pumps. The figures show a shape and describe nobody.
Is warranty data usable on a résumé
A percentage change is, and it is one of the strongest lines a design engineer has. Warranty claims down 46% after two wear assemblies were redesigned is the whole argument for a design career in one sentence.
Where should the CAD packages go
In the skills row. A design engineer is not hired for owning a licence. The experience lines should carry part counts, cost changes, lead times and validation results.
What did the checker score it
97 out of 100, with one improvement remaining worth 8 points. The document has 198 readable words, and the volume rule's top band opens at 250.
Should I mention drawings released
As a rate, yes. Three hundred and twenty drawings across two years with six suppliers describes throughput and coordination together, which a design manager reads as capacity.
Which design is this rendered in
Nexus, one of the 21 ATS-safe layouts out of 37. It is a compact technical page that keeps two roles and three languages legible.

Conxfolio is a free set of four career tools: a résumé builder with 37 rendered layouts, an ATS résumé checker that prints its own arithmetic, a cover letter builder that traces every proof paragraph back to the line it came from, and a portfolio builder with 20 authored designs. There is no account to create, nothing is held back for a paid plan, and no language model is used anywhere in the product, so the readers, the score and the letter are deterministic code you can check.