Roadmap

Your First 90 Days as an Engineer: A Practical Roadmap

A 30-60-90-day plan for a new engineer: learn how work moves, prepare one small piece of work, then own a small deliverable from inputs to review comments to final.

Roadmap · Last reviewed

Early engineering work is a chance to learn how decisions are documented, checked and communicated. The plan below is built around small deliverables and regular feedback from your supervisor or mentor. Your employer's procedures take precedence over anything here.

Days 1 to 30: learn how work moves

  • Find out where approved files live, how revisions are identified, who reviews calculations, and how questions are escalated.
  • Ask for one completed deliverable that shows the standard the team expects, and read it from start to finish.
  • Choose a drawing or calculation and trace its inputs. Note what was given, what was assumed, and which decisions needed a review.
  • Learn the project vocabulary: system names, abbreviations, drawing numbering, and the codes and standards in use.

Deliverable for days 1 to 30: a one-page workflow map (who gives what to whom, and where it is stored) and a glossary of the project terms you met.

Days 31 to 60: prepare a small piece of work

  • Agree a limited task with your supervisor. Write down its purpose, its inputs and the date it is due.
  • List your assumptions and the method you will use before you start calculating.
  • Check the arithmetic and the units before you submit. Keep unit labels on every number.
  • Ask for feedback on two things: the result, and how clearly the work shows its reasoning.

Deliverable for days 31 to 60: one reviewed calculation, schedule or drawing markup, with a record of the revisions.

Days 61 to 90: close the feedback loop

  • Take responsibility for a small deliverable within your assigned scope.
  • Confirm the inputs, track open questions, and incorporate review comments, noting what changed in each revision.
  • Explain the final result and its limits to the reviewer in a few sentences.
  • Write a short personal checklist from the comments you received, to run before your next submission.

Deliverable for days 61 to 90: a completed item with a short review history, and your personal checklist.

Habits worth building from the start

  • Write the unit next to every number, and state the source and revision of every input.
  • Separate what you observed from what you concluded.
  • Ask one clear question at a time, with the context needed to answer it (see the question template).
  • Record the revision and what changed each time you issue work.

Questions to ask in the first week

  • Who reviews my work, and how long does a review usually take?
  • Where do approved drawings, calculations and specifications live, and how are revisions marked?
  • Which codes, standards and company templates apply to my first projects?
  • How should I record my time and report progress?
  • Who can answer questions about the software we use?

Common early mistakes

  • Working from an old revision of a drawing or specification.
  • Leaving units off numbers, or mixing unit systems in one calculation.
  • Waiting too long to ask a question and then rushing the answer.
  • Treating a reviewer's comment as a verdict on you instead of information about the work.
  • Changing something the reviewer did not mention without recording it.

A simple progress log

Keep a short weekly log with three lines: what you finished, what you learned, and what you will ask next week. At day 30, 60 and 90, read it back with your supervisor. It turns vague feedback into specific goals.

Related tools and labs

Calculators, labs and simulators are part of the All-Access Pass.

More first 90 days

Questions

What if my employer has a different onboarding plan?

Follow it. This roadmap fits around most plans and gives you a way to track what you are learning.

How often should I ask for feedback?

At each deliverable, and after the first piece of work in particular. Ask what was clear, what was unclear and what you should do differently next time.

Does this apply outside engineering firms?

The habits (state assumptions, show units, track revisions, ask clear questions) apply to most technical work.

Should I ask for a mentor?

Yes, if your employer does not assign one. A mentor who is not your direct supervisor can answer questions that feel too basic to put to your reviewer.

How do I show initiative without overstepping?

Finish the assigned task, then offer a specific improvement and ask whether it is wanted. Do not change the scope on your own.

Educational material. Examples use simplified, hypothetical inputs and are not a design, a construction document or professional engineering advice. Confirm requirements with the codes and standards adopted where the work is built and with a licensed engineer.

← All first 90 days