DEV Community

HappyBug
HappyBug

Posted on

(Help) Roadmap to be a better engineer

Hello folks,

Context
If you came here looking for some wisdom, you are wrong.
I am mid level engineer at top MNC company (just by years in the industry and not really by skills). I have spent considerable amount of my time in my current company doing things that require absolutely bare minimum brain and effort.

Cool software and services were made by partner teams, all our org did was onboard to them.
To summarize the experience was mostly from onboarding to another, robotically following the docs given and apply the steps from the doc to our services and call it done. I tried to automate certain things and it was exciting time but that has also saturated.

These things might be good for running overall services in my company but as engineer, i find it dull and boring my skulls out.

Help
I have loads of free time or i am busy doing stuff that doesnt help me grow.
So here I am looking for some guidance to come out of this swamp and be better engineer.

I realize I lack so many skills that a person with my years of experience in IT industry is expected to have.

For starters, knowing async programming, design patterns, HLD. Given the new trends of introducing AI agents everywhere, i feel even more aliened and anxious.
I just don't know where to get started with so many things to learn and so many resources online. It is overwhelming.

TLDR
I so called mid level engineer in MNC but skills at fresher level. I need assistance to build a proper roadmap and stop my career from being a failure.

Top comments (1)

Collapse
 
js402 profile image
Alexander Ertli

Hey,

I see where you're coming from. I’ll skip the usual “feeling alienated and overwhelmed is normal”... because really, what matters is staying predictable and reliable while you feel that way. That’s what keeps you in the game.

Here’s what I think you can do:

You mentioned “cool software and services were made by partner teams” that's perfect.

Look up job postings for roles in those kinds of teams. Not to apply (unless you want to), but just to read through the tech stack listed.

That list is gold — it’s curated by people doing the work you wish you were doing. Now, pick the first thing on that list you don’t know.

Just one. Learn it in whatever way fits you: a book, a course, a hands-on project, doesn’t matter. Don’t worry about mastering it, just start using it.

Repeat that with the next thing on the list once the first starts making sense. And this way you get your roadmap, just one grounded in the position you actually would like to be in, and not one of some tech guru's theory on what you should know to confidently be able to call you a mid-level engineer.

I hope that helps you a bit in gaining clarity