Post image

Over the last two years, many conversations about “great engineers” have quietly shifted to “engineers who know how to use AI.”

But that’s a mistake.

Knowing how to poke at ChatGPT or auto‑complete a function in Copilot is not what makes someone a high‑impact engineer in 2026, just like knowing how to Google didn’t automatically make someone a great developer in 2008.

AI has changed the job, but it hasn’t replaced the fundamentals.

Below are 12 traits that actually matter now when you’re evaluating software engineers (of any title) in the age of AI. You’ll notice most of them aren’t about tools; they’re about how people think, decide, and build under new conditions.

1. They Start With the Problem, Not the Tool

A great engineer doesn’t begin with “Where can we shove AI?” They start with: "What are we trying to improve or predict?"

This mirrors the distinction in AI roles: builders vs. tourists. The same applies to general software engineers. The best ones don’t chase novelty. They anchor on outcomes.

What it looks like in real life:

  • In design reviews, they push for a clear problem statement before discussing models, frameworks, or vendors.
  • In interviews, they ask clarifying questions before jumping into code or architecture.
  • They’re comfortable saying, “We don’t need AI here; a cron job and a better index will do.”

2. They Think in Systems Instead of Features

Modern AI guidance talks about “AI system architects”, people who understand ingestion, context, permissions, orchestration, evaluation, and operations, not just the model.

Great software engineers do the same thing with every solution, AI or not. They see:

  • How data moves
  • Where failures show up
  • Who owns what
  • What has to be monitored and governed over time

What it looks like:

  • They sketch end‑to‑end flows instead of just the part they own.
  • In code reviews, they care about downstream effects, not just local correctness.
  • They instinctively ground every solution in reality: clarifying where the underlying knowledge comes from, how it flows through the system, and who is accountable for keeping it accurate and up to date.

3. They Treat AI Output as Untrusted Code

One of the biggest risks right now is that engineers accept AI output as truth. Great engineers understand that AI systems are probabilistic, context‑sensitive, and occasionally spectacularly wrong. They know AI is advisory, not authoritative.

In practice:

  • They wrap AI‑generated code with tests, logs, and guardrails.
  • They assume hallucinations are possible, and design for them.
  • They can explain where human judgment must stay in the loop.
  • If someone can’t tell you how they’d evaluate whether an AI‑assisted solution is good enough, they’re not ready for high‑stakes work.

4. They’re Fluent in Messy, Real‑World Data

Authoritative AI guidance emphasizes that trustworthy systems come from trustworthy surrounding data and retrieval logic, not just model choice.

You see the same trait in great engineers generally: they don’t flinch when data is fragmented or hidden across six different systems and three Slack channels.

What it looks like:

  • They ask, “Where does this data actually live, and who owns it?”
  • They’re comfortable writing glue code, data migrations, and adapters.
  • They push for improving data quality as part of the solution, not an afterthought.

5. They Know How to Evaluate a System

One of the most overlooked traits in hiring is evaluation.

They don’t just ship; they define and defend standards. A great engineer can articulate what “good” looks like, how performance will be measured over time, and where the line sits between acceptable failure and unacceptable risk.  This is especially critical when AI is in the loop, but it matters everywhere.

Signals to watch:

  • In interviews, they talk about how they tested and monitored past work.
  • They use language like “acceptable risk,” “thresholds,” “confidence,” “guardrails,” and “rollback plan.”
  • They can distinguish a cool demo from a reliable workflow.

6. They Understand Boundaries and When Not to Automate

Modern enterprise AI guidance stresses governance, privacy, and responsibility. Great engineers internalize that. 

A great engineer weighs whether something should be automated, how data should be protected, and who must be accountable when the system gets it wrong.

In real life:

  • They push back when someone wants to dump sensitive logs into a public LLM.
  • They’re okay assuming the system isn’t ready for production yet.
  • They flag places where a human must remain the final decision‑maker.

7. They Talk About Risks and Tradeoffs

Weak candidates talk mostly at the tool layer: brands, models, frameworks, features. Strong engineers talk about tradeoffs, constraints, operational friction,  and maintenance costs.

You’ll hear statements like:

  • “We could use AI here, but the governance overhead might outweigh the benefit at our scale.”
  • “This makes onboarding easier, but it increases our blast radius if the model drifts.”
  • “We’re trading latency for accuracy. Is that acceptable for this use case?”

If someone can’t articulate tradeoffs, you’re not looking at a senior, no matter how many tools they can name‑drop.

8. They’re Comfortable With Ambiguity (And Can Reduce It)

In AI‑heavy environments, requirements are rarely crisp. You’re exploring new capabilities, unclear value, and shifting constraints.

Great engineers don’t freeze in that ambiguity. They ask sharp questions, carve the unknown into testable chunks, and design small experiments to learn faster.

9. They Have Strong, Boring Software Engineering Habits

This might sound unglamorous, but in an AI era full of demos and hype, boring is underrated.

Great engineers still:

  • write readable, maintainable code
  • care about tests and observability
  • design interfaces thoughtfully
  • document decisions in a way others can follow

AI doesn’t make these habits less important. It makes them more critical, as code is produced at a greater speed and complexity increases around orchestration, data, and potential failure modes.

The best people you can hire are the ones who can absorb new tools without abandoning the fundamentals.

10. They Don’t Confuse Using AI Tools With Building AI Capability

The current market is full of engineers whose main value proposition is, “I know how to use Tool X really well.”

Great engineers understand the difference between using an AI assistant in their own workflow versus helping the organization systematically adopt, govern, and benefit from AI

In practice:

  • They think in terms of shared patterns, internal libraries, and reusable workflows, not just personal productivity hacks.
  • They design solutions that survive contact with operations, not just look great in a screen recording.
  • They’re happy to teach others how to use these tools safely and effectively.

11. They Design for Real-World Use

A system that nobody uses is a failed system, even if the code is beautiful.

Great engineers know that:

  • Training, docs, and UX matter
  • Change management is part of shipping
  • The “human wrapper” around a tool is as important as the model behind it

What you’ll see:

  • They volunteer to run brown‑bags or write internal how‑tos.
  • They think about how support, customer success, or non‑technical teams will interact with what they build.
  • They’re curious about how their work lands in the real world, not just whether it passed CI.

12. They’re Honest About What They Don’t Know

In a title‑inflated market, humility is a competitive advantage.

Great engineers don’t pretend to be frontier model researchers if they’re not. They don’t overstate their AI expertise because they’ve copied a few clever prompts from Twitter

Signals:

  • They distinguish clearly between hands‑on experience, things they’ve only read about, and areas where they’d need support.
  • They’re skeptical of buzzwords, including the ones they use themselves.
  • They’re willing to challenge hype, even when it would be easier to nod along.

In a world where everyone does AI, that kind of grounded honesty is one of the clearest markers of real seniority.

What You Should Really Be Hiring For Now

If you’re a CTO or VP of Engineering, the hiring bar has shifted. It’s no longer about who can list the most AI tools or show the flashiest demo. What matters is how clearly someone thinks about problems, systems, and tradeoffs in an AI‑shaped world. High‑impact engineers can reason through ambiguity, design with real constraints, and see the full lifecycle of a system, from idea to adoption and long‑term maintenance.

These are the traits we look for when we evaluate engineers, whether the title says “AI engineer,” “platform engineer,” or “senior software engineer.” Tools and model names will keep changing. Judgment will not. 

Because in this market, “knows how to use Opus” is not a hiring strategy.

And it definitely isn’t what makes a great engineer.