[ENGINEERING · EARLY CAREER]
This post is for new engineers figuring out how to survive real projects, real deadlines, and real pressure.
Summary
- University teaches you how to pass exams. It doesn’t prepare you for missed deadlines in the workplace, awkward client calls, or the panic of real-world engineering.
- Most of my early mistakes came from guessing, rushing, and being too scared to ask for help when I needed it.
- Deadlines aren’t “nice to haves” — people, money, and entire project timelines depend on them.
- You grow fastest when you own your mess-ups, communicate early, and take boring processes (checklists, planning, reviews) seriously.
- If you’re new: slow down, speak up, and ask the question you think sounds stupid. It’ll save you every time.
Failure Doesn’t Stop When You Get the Job
At uni, failure is simple: you mess up an exam, you resit, life goes on.
In a real job, failure spreads. Fast.
It looks like:
- a deadline quietly slipping away
- a client asking for an update you’ve been avoiding
- a document coming back from QA absolutely bleeding red ink
- a tiny mistake turning into extra cost and extra stress for everyone
There’s no reset button. No module to retake. You’ve just got to deal with it.
And I learned that the hard way.
From Lecture Notes to Live Projects
I walked into my first engineering role thinking something similar to what I wrote about in failing at university.
“I’ve passed my modules… surely this can’t be too bad?”
I quickly discovered:
- Projects don’t care that you’re new.
- No one hands you a perfectly formatted assignment brief.
- You’re juggling tasks, people, and expectations all at once.
No one warns you how different real projects feel compared to tidy university assignments.
Meanwhile, I was:
- saying “yes” to everything because I didn’t want to look slow
- underestimating how long things would take (every single time)
- keeping questions to myself until “later”
- hoping problems would quietly fix themselves (they didn’t)
Spoiler: nothing magically sorts itself out.
What I Actually Did
On paper, my tasks were straightforward:
- review drawings
- write up documentation
- answer technical questions
- coordinate with different teams
In reality?
- I agreed to timelines I didn’t fully understand
- I didn’t challenge unrealistic deadlines
- I tried to guess my way through unclear instructions
- I stayed quiet for far too long when I fell behind
All of which led to late nights, rushed work, and “Can we have a chat?” messages nobody ever wants to get.
And that’s when the wheels started coming off.
Where It Went Wrong
Mistake #1 – Treating Deadlines Like Suggestions
Early on, I thought deadlines were like uni coursework dates:
“If I hand it in around the deadline… that’s fine, right?”
Nope.
In the real world:
- people are waiting on you
- other teams can’t move until you finish your bit
- money depends on timelines staying intact
When I slipped, I wasn’t just late, I was blocking an entire chain of people.
Consequence:
- pressure from above
- rushed work trying to catch up
- a little bit of trust lost each time
Not because I was useless, but because I wasn’t realistic.
Mistake #2 – Saying “Yes” When I Meant “I Have No Idea”
When someone asked, “Friday okay?” my brain went:
“Say yes quickly before they realise you’re new.”
So I said yes… to everything.
Even when:
- I didn’t fully get the task
- I already had too much on
- I had no chance of hitting the deadline
Consequence:
- overbooked weeks
- half-finished work
- constant firefighting instead of actually doing things properly
These days, the bravest thing I ever say is:
“I can’t do Friday — but I can do Wednesday next week.”
Mistake #3 – Staying Quiet Instead of Asking for Help
I often knew when something wasn’t clear:
- a spec that didn’t make sense
- a guess disguised as a plan
- an assumption that probably wasn’t safe
But instead of asking, I thought:
“If I ask, they’ll think I’m clueless.”
And that always cost more time than it saved.
So I guessed. And hoped. And usually regretted it.
Consequence:
- rework when the assumption was wrong
- longer hours fixing something I could’ve avoided
- stress I absolutely didn’t need
Every single time I finally asked, the reply was:
“You should’ve said something earlier.”
Mistake #4 – Thinking Processes Were “Admin Stuff”
Engineering has processes for a reason:
- checklists
- design reviews
- sign-offs
- version control
- templates that look boring but save lives (and jobs)
At first, I treated all of it like annoying admin.
Consequence:
- small mistakes slipping through
- inconsistent documents
- QA catching things I should’ve caught myself
Eventually I realised that “boring” processes are the only reason complex projects don’t fall apart.
What I Learned
A few lessons hit me over and over again (usually the hard way):
- Be realistic, not heroic. Longer, honest timelines beat impossible ones every time.
- Ask the question. Stupid questions don’t exist, expensive mistakes do.
- Write things down. Your brain is not a reliable storage system. Journal it if you need to.
- Take “almost mistakes” seriously. A near miss is a lesson, not luck.
- Speak up early. “I might slip” is far better than “I’ve already slipped.”
What To Do Instead (If You’re New)
Here’s what I wish someone had sat me down and told me on day one.
1. Add Buffer to Every Estimate
Think it’ll take two days? Plan for three.
Not because you’re lazy. Because life loves interruptions.
2. Break Work Into Small, Clear Steps
“Finish the design” is not a task.
“Review requirements → sketch options → run basic checks…” is.
3. Do a Weekly Mini-Debrief
Ask yourself:
- What did I finish?
- What’s blocking me?
- What might slip next week?
4. Use Checklists
They catch mistakes before QA does and save you awkward conversations.
Example: The Deadline That Nearly Went Wrong
Client needs a design by Friday. You think, “Aye, maybe 2–3 days.” So you say yes.
By Wednesday:
- another urgent job drops on your desk
- a part of the spec still isn’t clear
- you’re way behind
Old me would’ve stayed quiet and sent a rushed mess late on Friday.
New me says something on Wednesday:
“I’m hitting a few issues. This will likely be Monday unless we adjust scope or get help.”
People are surprisingly reasonable when you warn them early.
Next Steps for You
If you’re just starting out, here are a few small wins you can do this week:
- Add honest buffer to any deadline you’re given.
- Ask one question you’ve been avoiding.
- Create a tiny checklist for one recurring task.
- Do a 5-minute reflection on what nearly went wrong.
Related Posts
Closing Thoughts
Failure doesn’t vanish when you start your career.It just changes shape.
You’ll still underestimate, panic, and make mistakes. That’s normal.
Nobody expects perfection. Just honesty, effort, and the willingness to learn faster next time.
If this hit home, pass it on to someone else starting out or send me a message about a mistake you learned from. No judgement here. We’re all just trying not to be eejits.
Leave a Reply