ResumeCrew
Menu
Start free

Resume example · Mechanical Engineer · 2 to 5 years

Mechanical Engineer resume with 2 to 5 years of experience: a sample from India

At two to five years the reader wants to know what you owned on the shop floor: a line, a cell, a maintenance area or a design package. Units per shift, downtime, OEE and rupees saved replace project titles, school marks come off, and the summary names the tools you use every day. The step up from fresher is that every claim now needs a baseline and a period.

Last reviewed
October 2026
Fictional sample
2 to 5 years of experience
Build yours in the chatCheck yours

Summary examples for 2 to 5 years of experience

Two ways to open the page. Neither is the summary on the sample resume beside it, so you can see more than one approach.

Summary example 1

Summary
Maintenance Engineer with 4 years in a 300-machine forging and machining plant. Cut unplanned downtime from 12% to 7%, moved breakdown tracking into SAP PM and trains operators on autonomous maintenance. Looking for a Senior Maintenance Engineer role.A maintenance profile: downtime, system and people in three short claims. Use it when the next role is a larger plant.

Summary example 2

Summary
Design Engineer with 3 years in agricultural-equipment fabrication. Designed 25 weld fixtures in SolidWorks, released 180 drawings and cut fabrication rework by 30%. Seeking a design engineer role in an OEM team.Replaces duties with a count of drawings released and a rework number. Suits a design engineer moving from a supplier to an OEM.

Bullet rewrites, weak to strong

Each pair shows a line people really write and a stronger version of the same fact. The numbers are illustrations. If you have no number, see resume bullets with numbers when you have none.

  1. Before

    Responsible for production

    After

    Planned and ran two shifts of a 12-machine turning shop producing 1,800 shafts a day; held scrap at 1.6% against a 2.5% target for 8 months

    Why

    Output, scrap and the target it was held against, over a stated period. 'Responsible for' offers none of the three.

  2. Before

    Reduced breakdowns

    After

    Cut unplanned downtime on 6 hydraulic presses from 14% to 8% in 7 months with a lubrication schedule and a critical-spares list of 25 parts

    Why

    Machine count, a before-and-after rate and two practical actions. A maintenance reader can judge whether the fix is believable.

  3. Before

    Did kaizen

    After

    Led a kaizen on coolant-tank cleaning that saved 1.5 hours of machine time a week on each of 9 machines, worth about ₹4 L a year after finance review

    Why

    A small kaizen is believable when the saving is converted to hours first and rupees second, and a finance review is named. Avoid round, unexplained savings figures.

  4. Before

    Made fixture drawings in SolidWorks

    After

    Designed a weld fixture in SolidWorks for a chassis sub-assembly that cut weld set-up from 25 to 10 minutes and lifted the dimensional pass rate from 91% to 98%

    Why

    For design roles the number belongs to the part: set-up time and pass rate. The drawing is only the route to it.

  5. Before

    Worked on energy saving

    After

    Surveyed compressed-air leaks across 3 shops, fixed 46 of them and cut compressor running hours by 11%, saving about ₹2.8 L a year in power

    Why

    Leak counts and running hours are things an energy-minded manager can verify. The rupee figure follows from the hours, not the other way round.

  6. Before

    Handled team of operators

    After

    Supervised 30 operators on a two-shift assembly line and cut absenteeism-driven stoppages from 9 a month to 3 using a cross-trained backup list

    Why

    People scope plus the problem you removed. At this level, supervision is credible only when a number moved.

Skills to list, grouped

Group skills into three or four lines and keep only those you could discuss for ten minutes. Each should appear in a bullet, a project or a certificate.

  • Production: OEE, SMED, Kaizen, 5S, Line Balancing
  • Maintenance: Preventive Maintenance, SAP PM, MTTR
  • Design and quality: AutoCAD, SolidWorks, GD&T, Root Cause Analysis

What recruiters for this role tend to look for

  • A line, cell or maintenance area you can call yours, with output per shift or per day and the target it was measured against.
  • OEE, downtime, scrap or first-pass yield with a before-and-after and a period. One or two per role are enough.
  • Kaizen or cost-saving work with a rupee figure that someone verified, and what was actually changed.
  • Tools in context: AutoCAD, SolidWorks or SAP PM inside a bullet, not only in a list, since screeners check for evidence.
  • Progression: a larger machine group, shift or team in the second role, with dates in months and no unexplained gap.

Mistakes common at this level

  • Keeping Class X and XII marks after three years on the shop floor. They no longer help and take space your OEE and savings numbers need.
  • Writing duties from the job description ('maintain machines as per schedule') instead of the downtime or cost result of doing it.
  • Claiming plant-wide savings for a team effort. Say which part you led, and keep the figure to what finance or your manager confirmed.

Section order on the sample

The sample uses the Classic Single template, A4 (210 by 297 mm), one column, with the sections in this order: Summary, Experience, Skills, Education, Certifications. The order follows the level: skills and experience lead and school marks have come off.

Questions people ask

Can I put kaizen savings in rupees if the figure was never audited?

Only if you can explain how it was worked out. State the unit that moved first (hours, scrap pieces, units) and use 'about' for the rupee value. If finance signed it off, say so. A figure you cannot defend in an interview does more harm than leaving it out.

I moved from maintenance to production. How do I show both?

Give each role its own dated line with the title as it was, and lead with the strongest result from each. Use the summary to join them in one line. A parser reads titles and dates, so keep them accurate.

Do I need SAP on a mechanical engineer's resume?

Only if you have used it. Name the module (PM for maintenance, PP for production planning) and attach it to a result, such as breakdown orders logged or MTTR tracked. A module name with no result reads the same as a tool you saw once.

Keep reading

Next step

Build yours in the chat

Answer a few questions, one at a time. The reviewer drafts each line, asks for the numbers it cannot guess and never adds a fact you did not give. Already have a resume? Check it first and see what a parser reads.

Build yours in the chatCheck yours