NOW LOADING ...

0%

← Back to blog
19 April 2026 aicareerwork

What If Your Role Isn't Just Your Role Anymore?

The old career playbook is breaking. And that's a good thing.

Originally posted on Substack

I was sitting in a company meeting last week.

Different teams were presenting updates. Engineering talked about what they were shipping. Product walked through the roadmap. Then marketing got up and shared what they were working on.

I had an idea. Something timely, something that could work for what they were trying to do. So after the meeting, I made it.

I’m not in marketing. I’m in a senior AI ops role. My job is helping teams adopt AI, building agents, enabling workflows. Content creation isn’t in my job description.

But I had the skills to execute. So I did.

I sent it to a few people on the marketing team. Casual. “Hey, I was just messing around. How funny is this?”

The response surprised me.

“You should post that. That’s great.”

They loved it. It went out on company socials. It performed well. People engaged with it in ways I didn’t expect.

And I couldn’t stop thinking about what that meant.

This isn’t new for me

I’ve been thinking this way since I got into AI.

My role isn’t just my role. I have a skill set that can be leveraged across multiple teams. I’ve done this with product. I’ve built tools that changed how other teams work. I’ve created agents that sit in workflows I don’t own.

Every time I build something, I think about it from multiple angles. If I was a PM, how would I approach this? If I was the customer, how would this impact me? If I was in marketing, what would actually resonate?

That cross-functional thinking isn’t something I was taught. It’s something the tools made possible.

I’m not the best designer. I’m not the best engineer. I’m not the best marketer. But with AI tools at my disposal, I can get a hell of a lot better than I ever could before.

And that gap, between what I could do a year ago and what I can do now, is enormous.

The models have changed everything

A year ago, I couldn’t have made that content.

Not because I didn’t have ideas. Because I didn’t have the tools to execute them at a level worth sharing.

That’s changed.

Opus 4.6. GPT 5.4. NanoBanana 2 Pro for images. Claude Code for building anything I can think of. The models have come so far in the last twelve months that it’s hard to overstate.

And it’s not slowing down. It’s accelerating.

I think most people underestimate how fast this is moving. We’re very close to a point where anyone can do this kind of stuff. Not just people in AI roles. Not just technical people. Anyone who takes the time to learn the tools.

The barrier between having an idea and executing on it is collapsing. And that changes everything about how work gets done.

The old model is breaking

For a long time, work was about lanes.

Designers stayed in design. PMs stayed in product. Marketers stayed in marketing. Engineers stayed in engineering. You had your role, your team, your responsibilities. Crossing into someone else’s territory was overstepping.

That made sense when the barriers were high. You couldn’t make professional content without years of design experience. You couldn’t build a tool without engineering skills. You couldn’t analyse data without knowing SQL.

Those barriers kept everyone in their boxes.

Now the barriers are dropping. Fast.

And the people who realise this, who start building skills outside their lane, who learn to execute on ideas that aren’t technically their job, those people are going to have a massive advantage.

This is about job security

There’s a lot of fear right now. And I think there’s going to be more.

AI is changing what companies need from their people. It’s changing how teams are structured. It’s changing what’s possible with fewer resources.

But here’s what I’m seeing in the market.

The people who are thriving aren’t the ones who are best at staying in their lane. They’re the ones who understand the business beyond their role. Who can think across functions. Who see opportunities that others miss because they understand how different teams work.

A designer who understands product strategy is more valuable than a designer who only thinks about pixels.

A PM who can prototype with code is more valuable than a PM who only writes specs.

A marketer who understands data is more valuable than a marketer who only thinks about campaigns.

And someone in any role who has AI skills, who can build and automate and create, is going to be dramatically more valuable than someone who doesn’t.

The gap is already widening. Every month. Every week. The floor is rising. What used to be exceptional is becoming expected.

The uncomfortable truth

If you’re a designer who only designs, you’re competing against designers who design and prototype and build.

If you’re a PM who only writes requirements, you’re competing against PMs who ship MVPs themselves.

If you’re a marketer who only runs campaigns, you’re competing against marketers who create content and analyse their own data and build their own tools.

This isn’t a prediction. This is what’s happening right now.

The people who see it are already moving. Learning the tools. Building skills outside their job description. Looking for opportunities to contribute in ways that aren’t expected of them.

I’m not saying do everyone’s job

I want to be clear about something.

This isn’t about constantly doing other teams’ work. That’s not sustainable. That’s not the point.

But if you see an opportunity, and you have the ability to act on it, why wouldn’t you?

Even if the work doesn’t get used. Even if it goes nowhere. You’re building skills. You’re learning how other parts of the business operate. You’re developing taste in areas outside your core expertise.

That compounds over time.

The content I made took me less than an hour. It might not have gone anywhere. Marketing might have said “thanks but we’ve got it covered.” And that would have been fine.

But it didn’t go nowhere. It went viral. And now I have a new skill I didn’t have before. A new muscle I can keep building.

Start now

You don’t need to become an expert in every function. That’s not realistic.

But start learning the tools. Start understanding how other teams work. Start looking for opportunities to contribute outside your lane.

A piece of content. A prototype. A workflow you automated. An idea you executed on that wasn’t your job but you did anyway because you could.

Those skills stack. That understanding compounds. And when the market shifts, and it will, you’ll be ready.

The tools are here. The models are good enough. The only question is whether you’re going to use them.

The people who see this coming are already moving.

Are you?