/

Recruiting

What Does a Senior Software Engineer Really Do?

What Does a Senior Software Engineer Really Do?

What Does a Senior Software Engineer Really Do?

Software engineers combine three kinds of experience: years, context and stack depth. See which one each role needs and how to test for it in interviews

Software engineers combine three kinds of experience: years, context and stack depth. See which one each role needs and how to test for it in interviews

Florencia Crescenzi

Florencia Crescenzi

Head of Talent Acquisition

Published

Topic

Recruiting

A seated statue typing on a yellow laptop, with a line of cubes growing in size coming out of the screen

You hired a senior engineer. Twelve years on the résumé, strong interview, sharp on the stack. Three months later, they’re still waiting for someone to tell them what to build. Or the opposite happens: the engineer with the not-so-flashy résumé is helping you make decisions, pushing back on weak ideas and making the rest of the team better.

You hired a senior engineer. Twelve years on the résumé, strong interview, sharp on the stack. Three months later, they’re still waiting for someone to tell them what to build. Or the opposite happens: the engineer with the not-so-flashy résumé is helping you make decisions, pushing back on weak ideas and making the rest of the team better.

Neither case is luck. Most teams treat "senior" as one number, and that number is almost always years. It's really three kinds of experience that don't always move together, and every role needs a different mix. Hire on only one of them and the mistakes are predictable.

What does "senior" mean for a software engineer?

A senior software engineer combines three kinds of experience: total years doing the work, exposure to different contexts such as companies, industries and team sizes, and depth in the technology the role requires. Each predicts something different. Years point to judgment, varied contexts point to adaptability, and stack depth points to day-one productivity.

What are the three kinds of seniority in software engineering?

An hourglass, a suitcase with travel stickers and a vintage keyboard, standing for years, contexts and stack

Overall experience: how long they've done the work

This is the number everyone measures, and on its own it tells you the least. Years build craft and judgment, but they don't tell you what kind of years they were. When researchers revisited decades of hiring studies in 2022, years of job experience landed among the weakest predictors of job performance (Sackett et al., Journal of Applied Psychology).

Exposure to different contexts: how many environments they've worked in

Three years at a startup, four at an enterprise and three running their own business is not the same as ten years at one company. Each move forces someone to read a new business, new people and new constraints, and become useful anyway.

Is an engineer who has spent 20 years maintaining the same COBOL backend at a bank senior? Yes. But only in that system, at that bank.

An open suitcase with a hard hat, an ID badge and a headset coming out of it

Experience in the required technology: how long they've used your stack

The role asks for Python. The candidate has used it for one year. The other nine were in .NET. On paper that's a junior Python developer. In practice, it's a senior engineer who will need a few weeks to get fluent in a new syntax and ecosystem.

Which kind of experience predicts what on the job?

Each dimension answers a different question about the person you're hiring:

  • Overall experience tells you about judgment: trade-offs, estimates, knowing what not to build.

  • Exposure to contexts tells you about adaptability: walking into a business they don't know, reading the situation and becoming useful quickly.

  • Stack experience tells you how productive they'll be on day one.

A stable maintenance role can lean on the third. A client-facing role, or one in an environment that changes fast, depends more on the second. That describes almost anything touching AI today, and it's the dimension almost nobody measures or asks about in an interview.

Which kind of seniority does each engineering role need?

  • Legacy system maintenance. Matters most: stack experience. Why: the system won't change much. Knowing its quirks is the job. Where you can flex: variety of contexts.

  • Product development. Matters most: overall experience. Why: every sprint is a trade-off between scope, speed and tech debt. Where you can flex: years in the exact stack.

  • Client-facing role. Matters most: exposure to contexts. Why: they need to read a new business fast and earn trust in the room. Where you can flex: total years.

  • Applied AI project. Matters most: exposure to contexts. Why: tools change every few months. The real work is finding where AI fits a specific business. Where you can flex: years in a given framework.

If you're scoping a role and aren't sure which column it falls into, tell us about the role and we'll help you map it.

Which engineers do you need at each stage of your software project?

The kind of senior you need shifts as the project moves. Staff the whole thing with one profile and you'll overpay in one phase and come up short in another.

  • Discovery and scoping. Exposure to contexts. Someone has to understand a business they've never seen and turn it into a plan. Leads and analysts who've worked across industries catch wrong assumptions early.

  • MVP build. Overall experience. Speed with judgment: what to build now, what to fake for a demo, what to skip.

  • Scaling. Overall experience and stack depth. Architecture, performance and the limits of your stack start to cost real money.

  • Maintenance and support. Stack experience. The system won't change much. Knowing where it breaks is the job.

  • Adding AI to the product. Exposure to contexts. The hard part is finding where AI fits the workflow, not picking the library.

A team usually changes shape as the product grows. Plan for that when you staff it, instead of hiring only for the stage you're in today.

What hiring mistakes come from measuring seniority by years?

Filtering on total years

A "10+ years" filter quietly removes the people who've worked in five different environments in seven years. For a role that needs adaptability, those are often the best candidates on the list.

A statue hand holding a sieve while yellow cubes fall through its holes

Making "X years in technology Y" a hard requirement

People can learn a technology. Judgment is much harder to teach. A hard stack requirement trades a few weeks of ramp-up for a smaller, weaker pool.

Proxies like this are hard to drop, even when companies say they want to. A Harvard Business School and Burning Glass Institute study found that 45% of firms that removed degree requirements from job posts made no real change in who they hired (Burning Glass Institute). Rewriting the job post isn't enough. The evaluation has to change too.

Cloning your top performer

It's tempting to write the hiring profile around your best engineer. The problem is you can't separate what comes from their talent and what came from their context: the codebase they grew up in, the manager who backed them, the timing. You end up hiring for the résumé, not the reasons it worked.

A philosopher bust followed by three faded photocopies of it, crossed out in yellow

When does stack experience matter more than adaptability?

Sometimes depth in one system beats variety. A go-live in three weeks leaves no room for anyone to learn the stack. A heavily regulated legacy system can reward ten years of knowing exactly where it breaks.

The point isn't that exposure to contexts always wins. It's that you need to know which dimension matters most for each role before you write the job description.

Where should you start when defining seniority for a role?

  1. Write down what the person will face in their first 90 days. Problems, people and pace, not a list of tools.

  2. Rank the three dimensions for that role. One of them should clearly come first.

  3. Set a hard requirement only on the dimension that comes first. Treat the other two as signals.

  4. Use structured interview questions to test the top dimension directly. Structured interviews hold up as one of the strongest predictors in the same 2022 research.

How do you interview for exposure to different contexts?

Years and stack show up on a résumé. Adaptability only shows up when you ask. A few questions that work:

  • "What's the most different environment you've worked in, and what did you have to unlearn?"

  • "Walk me through your first two weeks in your last role. When did you ship something useful, and how did you figure out what mattered?"

  • "Tell me about a time a new company's way of working clashed with yours. What did you do?"

  • "What would have changed in your last project if the team had been ten times bigger? Or a third the size?"

Listen for specifics: names of systems, people and decisions. Vague answers usually mean the person stayed in one context, even if they changed employers.

Why do years and hourly rates fail as a way to hire engineers?

The staffing industry reduced talent to two shortcuts: years of experience and hourly rate. Both are easy to compare and both miss most of what makes an engineer right for a role. AI staffing is repeating the same move. "AI engineer" now often means six months with a framework.

We've been building engineering teams for US companies since 2003, long enough to see how often a good résumé lands in the wrong role. If you're about to build your team, start from what each role has to handle, not from a number. For AI Transformation work, that usually points to engineers who have worked across several businesses, not just several tools. Our case studies show what that looks like in real projects.

Frequently asked questions about senior engineers

What makes a software engineer senior?

A mix of three things: years doing the work, exposure to different companies and contexts, and depth in the required technology. Which one matters most depends on the role.

How many years of experience does a senior engineer need?

There's no fixed number. Years alone are a weak predictor of performance. What those years included, and whether they match what the role needs, matters more than how many there were.

Is a senior developer in one language still senior in another?

In judgment and craft, yes. In day-one productivity, not quite. A senior .NET engineer moving to Python usually needs a few weeks to ramp up, not years.

How do you test seniority in a technical interview?

Use structured questions tied to the dimension the role needs most. Test stack depth with real code, judgment with trade-off scenarios, and adaptability with questions about past changes in context.

How does AI change what senior means?

AI tools change every few months, so years in a specific framework age fast. Exposure to different contexts matters more, because the hard part is figuring out where AI fits a business, not which library to use.

Hiring for a role where the wrong kind of senior would cost you?

When you’re ready to move your product forward, talk to us. Kubikware has matched the right talent to the right project since 2003, using our own methodology and systems to find the fit quickly. Talk to Kubikware about your project.

Florencia Crescenzi

Written by

Florencia Crescenzi

Florencia Crescenzi

Head of Talent Acquisition

/More articles.

Contact us today for a free consultation and let's discuss your next project.

By submitting, you agree to our Terms and Privacy Policy.

KUBIKWARE

Artisans, within reach. Since 2003.

© 2003–2026 Kubikware, LLC

All rights reserved.

Contact us today for a free consultation and let's discuss your next project.

By submitting, you agree to our Terms and Privacy Policy.

© 2003–2026 Kubikware, LLC

All rights reserved.

Contact us today for a free consultation and let's discuss your next project.

By submitting, you agree to our Terms and Privacy Policy.

KUBIKWARE

Artisans, within reach. Since 2003.

© 2003–2026 Kubikware, LLC

All rights reserved.

Contact us today for a free consultation and let's discuss your next project.

By submitting, you agree to our Terms and Privacy Policy.

KUBIKWARE

Artisans, within reach. Since 2003.

© 2003–2026 Kubikware, LLC

All rights reserved.