← All articles
Growth Series

Module 0: Ownership Is Not Given. It's Taken.

The mindset shift that separates engineers who grow from engineers who wait — and why AI makes it more urgent than ever

January 13, 2025 · 4 min read


Someone asked me once if I felt ready for my next level.

I said no. They promoted me anyway.

That conversation stuck with me — not because of the promotion, but because of what my manager said next. "You've been operating at that level for months. You just haven't noticed."

I hadn't noticed because I was still waiting. Waiting for someone to tell me I was ready. Waiting for the right project to be handed to me. Waiting for permission I already had.

That's the mindset trap most engineers fall into. And in a world where AI is handling more of the execution work, the engineers who can't get out of that trap will stagnate the fastest.


The real blocker isn't technical

Last month I spoke with over 40 engineers who were stuck in their careers. I kept expecting the pattern to be something technical — gaps in skills, outdated stack knowledge, not enough system design experience.

That wasn't it. The blockers were almost always mindset. Recognition. Communication. The inability to see themselves as someone operating at a higher level before anyone else did.

The engineers growing fastest around them weren't the most technically gifted. They were the ones who stopped waiting.


What ownership actually looks like day to day

I've watched leaders hand over responsibility and assume ownership would follow. It often doesn't.

You can give someone a project, a title, a decision. That doesn't mean they feel accountable for the outcome. Ownership starts earlier than execution. It begins when someone sees the work as something they're stewarding — not just completing.

In my experience, the people who truly take ownership don't wait for permission. They ask better questions. They think about second-order effects. They leave things better than they found them.

Ownership is also visible. It shows up in how people speak about problems — not "that's not my area" but "I noticed this and here's what I think we should do." It shows up in how they represent work when no one else is in the room, and in how they respond when things don't go as planned.


Why AI raises the stakes on this

AI is coming for engineering tasks, not engineering jobs. There's a difference.

Tasks are specific and bounded. Write this function. Generate this test. Summarize this PR. AI is exceptionally good at those things.

Jobs are broader. They involve judgment, context, ownership, relationships, and accountability across time. AI does not have a job. Engineers do.

As AI handles more execution, the premium on human judgment goes up — not down. The engineers who thrive are the ones who've built the habit of ownership before the environment forces it on them.

AI is the multiplier. Not you grinding through the wrong problems faster.


The four ownership behaviors that managers actually notice

1. They anticipate instead of react

The engineer with ownership sees the dependency risk before the sprint starts. They flag the ambiguity before it becomes a blocker. They don't wait for someone to connect the dots — they connect them.

2. They ask why, not just what

Anyone can execute a ticket. The ownership question is: are we solving the right problem? That question — asked at the right moment — is one of the most valuable contributions an engineer can make.

3. They absorb problems instead of redistributing them

When things go sideways, ownership shows. Do they figure it out and communicate clearly? Or do they look for someone to hand it back to? Leaders remember both behaviors.

4. They make their context visible

Ownership isn't just internal. It shows up in how you communicate your work — in your updates, your PRs, your 1:1s. If the people who can advocate for you don't know what you're doing and why it matters, ownership stays invisible.


The question that changes things

Every promotion, breakthrough, or transformation I've seen comes after an uphill push. That's not coincidence. That's the cost of progress.

You can only coast downhill. Comfort will pull you backward. And you cannot elevate your position by coasting.

The question I'd ask yourself this week: where am I waiting for permission that I could just take responsibility instead?

That question, answered honestly, is where growth starts.

Justin Otero

Director of Engineering at Navan · Founder, Value Driven Careers

Justin coaches software engineers, leaders, and founding teams to grow their impact, income, and influence — without burning out.

Next step

Want to grow faster without burning out?

Whether you are an engineer looking to level up or a leader building a high-performing team, Value Driven Careers can help.