The Question a Senior Developer Asked Me

In 2024, a senior developer pulled me aside after a team session. He’d spent the morning watching AI tools generate code faster than he could review it.

He asked me, quietly: “If AI can write eighty percent of my code, am I still a senior? Or am I just the person who fixes what it gets wrong?”

I didn’t have a clean answer. I told him so. What I did say was: “The question isn’t whether you’re still a senior. It’s whether the work that remains is work you want to do—and whether you can see how valuable it actually is.”

That conversation has stayed with me. Because it is the honest version of the question most organizations are performing around, rather than actually asking.

If you’re a Scrum Master, Agile coach, engineering leader, or anyone whose value has always lived partly in the unwritten parts of your role—this article is for you. Your most important work is not what AI threatens. But you may need to learn to see it.

What AI Actually Threatens—and What It Does Not

Let’s be precise, because precision matters more than comfort here.

AI can automate status aggregation, draft requirement documents from prompts, generate code, summarize meetings, detect dependency patterns, and produce dashboards that look authoritative. These are coordination tasks. They are, in most cases, the least valuable part of what knowledge workers do each day.

AI cannot read the room.

It cannot hear a voice drop half an octave during a standup and know that the developer who said “I’m fine” is not fine. It cannot send the private message afterward: “You seemed hesitant about that database change—want to pair on it?”

That moment—that noticing, that follow-up—prevented a compliance failure on a production system I was involved with. It is not in any job description. It never will be. And it is precisely the kind of work that makes the difference between a functioning team and a performing one.

“AI is coming for the work in your job description. The work that was never written down is safe—if you know where to find it.”

Hype Has a Pattern. You’ve Seen It Before.

In 2012, the hottest skill on LinkedIn was a particular certification. By 2016, the language had shifted to lean. By 2019, DevOps transformation was the imperative. Now it’s AI.

The label changes every four to five years. The underlying need—humans who can navigate complex adaptive systems, build psychological safety, name the truth that no algorithm surfaces, and hold a team together when the plan meets reality—does not.

I’ve served as a Distinguished Toastmaster and District Director in Toastmasters International, working with thousands of communicators over many years. The skill that distinguished exceptional leaders from competent ones was never the ability to deliver information. It was the ability to create a room where truth could be spoken and heard.

That is not automatable. It is barely teachable. And in AI transformation, it may be the most critical capability in the building.

Hype is just weather with a marketing budget. You can check the forecast, dress appropriately, and continue your work. Executive FOMO is not a signal that your skills are obsolete. It’s a signal that the market is reacting to novelty—which it always does.

Three Capabilities That Don’t Appear on Resumes

Over fifteen years of facilitating transformation in regulated industries, I’ve consistently seen three capabilities separate leaders who deliver real results from those who deliver impressive reports.

1. The Art of Naming What Is Actually Happening

Most organizational dysfunction is not caused by a lack of information. It’s caused by the presence of information that no one is willing to name out loud. The politics between teams. The unspoken doubt about whether the AI model actually works on production data. The executive who believes the timeline and the engineer who knows it’s impossible.

The leader who can name these things—not as accusations, but as observations worth examining—provides a capability that no tool offers. AI can generate a status report. It cannot ask the question that makes the room go quiet and then productive.

In integrity-centered leadership, I call this the courage of naming: the discipline to say what is true in the moment it needs to be said, at the cost of momentary discomfort, in service of actual outcomes.

2. The Economics of Earned Trust

Your reputation in an organization is not what you say about yourself. It is a ledger—a running balance of every honest report, every difficult conversation, every moment you said “I don’t know” when you didn’t know, rather than filling the space with confident imprecision.

Executives are surrounded by people who manage upward rather than report upward. The professional who gives an honest amber—“here is the risk, here is our hypothesis, here is when we will know”—becomes invaluable not despite their candor but because of it.

“Your reputation isn’t your resume. It’s your ledger. Every status update either deposits or withdraws. Spend wisely—or go broke when it matters.”

Performative certainty is a withdrawal. Every green status that covers an amber reality takes something from the account. Organizations that have trained people to manage the appearance of progress rather than report its reality are not solvent. They are burning the inventory they will need when the next difficult initiative arrives.

3. The Skill of Grounded Presence Under Pressure

AI transformation initiatives fail not primarily because of technical problems, but because of human ones: the decision-maker who cannot tolerate uncertainty and pushes for commitment before the experiment is complete; the team that fragments under pressure; the leader who disappears when the honest conversation becomes unavoidable.

Grounded presence—showing up steady in the face of chaos—is the leadership capability the current AI moment demands most, and the one most rarely discussed. Teams with a calm, grounded leader take better risks, make more honest reports, and catch problems earlier.

In regulated industries, where the cost of a missed signal is measured in regulatory incidents rather than sprint velocity, this is exactly the capability that needs to be protected.

New Roles, Not Replacement Roles

AI will replace the mechanical components of most roles: documentation, aggregation, routine reporting. This is not a threat—it is what tools have always done. The industrial revolution replaced the mechanical work of the body. AI is replacing the mechanical work of the mind.

What AI will not replace:

•       The AI Decision-Maker: who maintains the experiment portfolio alongside the feature list and makes go/no-go decisions based on genuine evidence.

•       The Ethics Scout: a rotating role that builds ethical literacy across the entire team rather than concentrating it in a compliance function.

•       The Embedded ML Engineer: who participates in every coordination event as a first-class team member, not as a consultant called in when models fail.

And underneath all of these: the leader with the judgment, presence, and courage to hold the honest conversation that no algorithm can initiate.

What I’d Tell That Developer Today

If AI can write eighty percent of your code, and all your organization can see is the code—then yes, your position is under pressure.

But if the organization can see the decisions you prevent, the conflicts you navigate, the integrity you maintain under pressure, the trust you build across the team—AI has not threatened you. AI has revealed you.

Most organizations cannot see this yet. That is the real problem. Not the technology. The measurement systems that have always credited visible work and ignored the invisible work that made the visible work possible.

Your job in this moment is not to learn every AI tool. It is to become clear about what you actually do that no tool does—and to find the language to make that visible to the people who need to see it.

That is not a defensive posture. It is a strategic one.

📋  HONESTY CHECKPOINT: What did you do this week that a language model cannot? Name it specifically—not in category terms, but as an actual moment. If you cannot name it, that is not evidence that AI has replaced you. It is evidence that you have not yet learned to see your own most valuable work.

What’s one thing you do regularly that you’ve never seen in a job description but know matters deeply to your team? Drop it in the comments.

Gopu Shrestha is an enterprise architect and published author working at the intersection of strategic honesty, integrity-centered leadership, and AI transformation in regulated industries.