Skip to content

How to get a core engineering job with a cold email

Core engineering hiring runs on trust that you can be put on a shop floor, a site or a design desk and be useful soon. Lead with hands-on work: the plant, the site or the drawing you worked on, what you did yourself, and the software and equipment you used.

Updated

What core engineering posts ask for

Titles include graduate engineer trainee (GET), diploma engineer trainee, design engineer, production, maintenance or quality engineer, and site engineer. What the posts ask for differs by branch:

  • Mechanical: CAD (AutoCAD, SolidWorks, Creo or CATIA), GD&T, manufacturing processes and, for some roles, analysis in ANSYS. Production and quality roles name methods such as 5S, Kaizen and root cause analysis.
  • Electrical and electronics: wiring and control panels, PLC and SCADA for automation roles, AutoCAD Electrical, maintenance of motors and transformers and, for power roles, protection and substations.
  • Civil: site execution, AutoCAD drawings, quantity estimation and billing (BOQ) and, for design roles, STAAD.Pro or ETABS. Site roles often name the kind of project: buildings, roads or water.
  • Shifts and place: plants run in shifts, sites are wherever the project is, and many posts say “ready to relocate”.
  • A branch and a batch year, and sometimes a minimum percentage. Diploma and degree holders are often hired for different titles.
  • Safety awareness and, for site and plant roles, a willingness to work on the floor, not only at a desk.

Your proof as a fresher

As a fresher, the proof that counts is time on a real floor, site or drawing:

  • In-plant training or an internship: the plant, the line or section, what you did with your own hands, and anything you measured or improved.
  • A final-year project that was built and tested, such as a machine, a rig, a circuit or a structural model, and what it did.
  • A competition where you built something that ran, such as SAE BAJA, Formula Student, robotics or bridge-building events, and the part you owned.
  • Software you have used on real drawings or models, with one example rather than a list.
  • A graduate or diploma apprenticeship, if you have done one: it counts as a year of work.

Say your branch in the first line. A plant head reading an email for a mechanical opening shouldn’t have to guess whether you are an electrical engineer.

Your proof if you are switching in

Moving between core roles, or back to core engineering from IT or sales? Lead with the engineering you have done most recently:

  • From one core role to another, such as maintenance to design or site to planning: the work you did in the new area within your current job.
  • From an IT services job back to core: your degree project, and any core work since, such as a design course with a real model you made.
  • From a diploma role to a degree role: your years on the floor, and the degree you finished alongside.
  • From selling engineering products: the technical work you did for customers, such as sizing pumps or specifying cables.

Your proof in two sentences

Sentence one: where you worked (plant, site or design office), on what, with which software or equipment. Sentence two: what you did yourself, and a result someone measured.

Mechanical, fresher

During my six-month internship at an auto parts plant in Pune, I worked on the machining line that makes brake drums. I timed each step of a changeover and suggested two fixtures that could be set up while the machine was running, and the changeover now takes about half as long.

Civil, back from IT

After two years at an IT services company, I returned to civil engineering as a site engineer on a four-storey residential building. I kept the daily progress reports and the bar bending schedules, and checked every slab’s reinforcement against the drawings before the pour.

Both are made-up examples. The numbers in yours must be your own, and ones you can explain in an interview.

An example email

Mahesh, the plant head at a maker of electrical panels, posts for graduate engineer trainees in electrical engineering, 2026 batch, with an address for resumes. Kavya finished her B.Tech in electrical engineering this year and did her internship at a solar EPC company. This is the whole email.

To
mahesh@voltcraft.example
Subject
Graduate Engineer Trainee (Electrical): Kavya Reddy, B.Tech 2026

Hi Mahesh,

I saw your post for Graduate Engineer Trainees at Voltcraft. I finished my B.Tech in Electrical Engineering this year, and I want to start my career on the shop floor, building panels and not only drawing them.

During my internship at a solar EPC company, I drew the single-line diagrams for three rooftop projects in AutoCAD Electrical and went to site for the inverter and panel installations. On one site I found that a cable in the drawing was too small for its length, and the corrected size went into the final bill of materials.

Your panels go into the kind of solar and industrial sites I worked on, which is why your post stood out. My resume is attached, and I am ready to relocate to your plant.

Kavya Reddy
+91 98xxx xxxxx

linkedin.com/in/kavyareddy-example

A made-up example: Kavya, Mahesh and Voltcraft are fictional. Every claim in the email comes from Kavya’s own resume.

What makes it work:

  • Her branch, her batch and the post’s title are all in the subject and the first line.
  • Hands-on work a plant head recognises: drawings, site visits and installations.
  • One catch, an undersized cable, shows she checks her work, which matters more in a core role than any software.
  • “Ready to relocate” answers a question every plant and site role has.

The subject line

The title as the post writes it, your branch in brackets, your name, and your degree and batch or your years.

  • Graduate Engineer Trainee (Electrical): Kavya Reddy, B.Tech 2026
  • Design Engineer (Mechanical, SolidWorks): Rahul Patil, 2 years in fixture design
  • Site Engineer (Civil): Mohammed Arif, B.E. 2026, internship on a residential site

Avoid subjects like “Job application” or “Resume”. The person who posted may have several openings, and the role first tells them which one.

Mistakes to avoid

  • The same email for every branch’s post. A mechanical, an electrical and a civil opening want different proof.
  • A list of software with no drawing or model to show for it.
  • Writing for a site or plant role when you want a desk job. Say what you want, and answer the posts that fit it.
  • Photos or drawings from an employer’s project, shared without permission.
  • Leaving out your branch and batch. Many core posts are for one branch and one year.
  • Posts that ask for a fee for training, a uniform or a joining kit. Real employers don’t charge you to join.

And the ones that hurt in every role: a guessed address, a generic resume, and an email longer than a phone screen. More in how to email a recruiter about a LinkedIn hiring post.

Where core engineering posts appear

  • LinkedIn posts by plant heads, HR at manufacturing companies, EPC and construction firms, and design consultancies.
  • Careers pages of manufacturers, contractors and design firms; smaller firms often give an email address there.
  • Telegram and WhatsApp groups for each branch, which forward GET, apprentice and site engineer openings. Check that the company is real before you write.
  • Your college’s training and placement office, and alumni who work in plants and on sites: they know who is hiring.

A LinkedIn post search to start from (search Posts, Date posted Past 24 hours):

Core engineering posts for freshers

("mechanical engineer" OR "electrical engineer" OR "civil engineer" OR "graduate engineer trainee") ("send your" OR "share your") fresher

4 of 5 ORs, ANDs and NOTs

Keep only your branch’s title for fewer, closer posts. For site roles, "site engineer" finds civil and electrical site openings. LinkedIn finds nothing at all once a search has more than five ORs, ANDs and NOTs: see how to find hiring posts on LinkedIn. If there is no reply in about a week, follow up once.

Guides for other roles