#base camp

Contract vs Permanent Jobs 2026: A Salary Breakdown

A Tool That Hasn’t Changed Much

The CV has been part of hiring for decades, and in many ways, it hasn’t changed much.

It still serves a clear purpose — giving a quick overview of someone’s background, experience, and career progression. For an initial screen, that’s useful.

The issue is that the role of the CV has expanded, while its structure has stayed the same.

In many hiring processes, it’s still treated as the primary basis for decision-making. And that’s where the mismatch starts to show.

What a CV Actually Tells You

A CV is good at summarising history. It shows where someone has worked, what roles they’ve held, and how their career has progressed over time.

What it doesn’t show is how that experience translates into real performance.

Two candidates can have very similar CVs — similar titles, similar years of experience, even similar tools listed — but perform very differently once they’re in the role. One may operate independently and solve problems quickly, while the other may struggle without clear direction.

That difference rarely shows up on paper.

The Problem With Reading Too Much Into It

Hiring decisions often rely on signals that the CV was never designed to provide.

A well-known company name might suggest quality. A senior job title might suggest leadership. A long tenure might suggest stability.

Sometimes those assumptions are correct. But just as often, they aren’t.

Job titles vary widely between organisations. Responsibilities are not always comparable. And in many cases, the context behind a role matters more than the title itself.

Without that context, it’s easy to misread what a CV is actually saying.

What Gets Missed

The biggest gap is behavioural.

How someone handles uncertainty, communicates with others, or responds when things don’t go as planned — these are the factors that often determine success in a role.

But they’re difficult to capture in a structured document.

You see this most clearly during interviews. A candidate with a strong CV may struggle to explain their decision-making in a real scenario, while someone with a less polished background can walk through problems with clarity and confidence.

That difference is hard to predict from the CV alone.

How Better Hiring Processes Work

Organisations that hire more consistently well tend to treat the CV as a starting point, not a conclusion.

After that initial filter, they focus more on how candidates think and operate.

For example, instead of asking hypothetical questions, they might ask candidates to describe a real situation they’ve handled — what the challenge was, what decisions they made, and what the outcome was. These conversations tend to reveal far more than general answers.

Even simple exercises can make a difference. Asking a candidate to walk through how they would approach a problem, or to explain a past project in detail, often gives clearer insight than reviewing qualifications alone.

The goal isn’t to make the process more complicated. It’s to make it more reflective of real work.

What This Means for Candidates

For candidates, this shift changes how to approach the hiring process.

A strong CV still matters — it helps open the door. But it’s only one part of the evaluation.

What matters just as much is how you communicate your experience, how clearly you can explain your thinking, and how you respond when faced with unfamiliar questions or situations.

Candidates who prepare examples, think through their past decisions, and engage actively in conversations tend to stand out more than those who rely solely on a well-written document.

A More Balanced Perspective

The CV isn’t going away, and it shouldn’t.

It remains a practical tool for organising information and starting conversations. But it has limits, and those limits are becoming more noticeable as roles become more dynamic.

The organisations that recognise this are not abandoning the CV — they’re simply placing it in the right position within the hiring process.

And in doing so, they’re making more informed decisions about the people they bring into their teams.

The Assumption That Quietly Stopped Working

For a long time, growth in technology teams followed a familiar pattern. When demand increased, companies added more people. More engineers meant faster delivery. More support staff meant smoother operations.

It made sense—and for a while, it worked.

But over time, that relationship started to weaken. In some teams, adding more people has actually made things slower, not faster. Work begins to pass through too many hands, decisions take longer, and coordination becomes a task on its own.

At the same time, smaller teams with the right mix of skills have often moved quicker and handled change better. The difference isn’t just about size. It comes down to what each person is able to contribute.

The Nature of Technology Work Has Changed

A big part of this shift comes from how the work itself has evolved.

Not long ago, even a simple internal tool could take weeks and multiple people to build — a developer, a tester, sometimes even a separate operations layer. Today, a capable developer can often get a working version up in a day or two using the right tools.

That change has real consequences.

When individuals can do more on their own, adding more people doesn’t always improve output. After a point, it can slow things down instead. More dependencies form, more coordination is needed, and small delays start to add up.

This is why some teams are becoming more deliberate about who they hire, rather than how many. What Capability Looks Like in Practice

Capability isn’t just about experience or qualifications. It shows up more clearly in how someone handles real situations.

A capable hire is someone who can step into an unclear problem, figure things out, and keep things moving without needing constant direction.

In everyday work, that might look like:

Picking up a new tool or system without much guidance

Working through problems that weren’t part of the original plan

Explaining ideas clearly to different types of stakeholders

Taking ownership, even when the boundaries of the role aren’t perfectly defined

These qualities are not always obvious during hiring, but they tend to matter the most once the work begins.

A Simple Comparison

You see this quite clearly when looking at how different teams operate.

A 20-person engineering team with very defined roles can sometimes move slower than a 12-person team where people are comfortable stepping into different areas when needed—whether that’s backend work, cloud infrastructure, or automation.

With a smaller team, there are usually fewer handovers and less waiting around for the next person to pick things up. Work moves more directly, and decisions don’t get stuck across layers.

This doesn’t mean smaller teams are always better. But it does show how capability can have a bigger impact than headcount alone.

Why This Shift Is More Noticeable in Asia

Across Asia, this shift is becoming harder to ignore.

Many companies are now operating across several markets at the same time, and each one comes with its own expectations and constraints. What works in one country doesn’t always translate neatly into another.

At the same time, hiring is no longer tied to a single location. It’s common for teams to consider candidates from across the region. While that creates more options, it also makes it harder to rely only on qualifications as a signal of quality.

In that kind of environment, technical skills are only part of the picture. How someone adapts, communicates, and works through problems often matters just as much.

Where Hiring Processes Still Fall Behind

Even with all these changes, hiring processes haven’t really evolved at the same pace.

CV filters, keyword searches, and loosely structured interviews can show where someone has worked, but they don’t always reveal how that person actually operates day to day.

This is often where mismatches happen. Someone may look strong on paper but struggle once they’re in the role—not because they lack knowledge, but because the way they work doesn’t fit what the role actually demands.

More effective approaches tend to focus on practical insight. Simple problem discussions, structured conversations, or asking candidates to walk through real past work can reveal far more than a list of credentials.

A More Useful Way to Think About Hiring

The shift from headcount to capability isn’t about changing everything. It’s about asking better questions.

Instead of focusing only on how many people are needed, it helps to look at what kind of people will actually move the work forward.

That small shift in thinking influences everything else—how roles are defined, how candidates are assessed, and how teams perform over time.

And increasingly, it’s becoming the difference between teams that keep up and teams that quietly fall behind.

Remote IT Hiring in Asia: Why More Companies Are Going Borderless in 2026

Remote IT hiring isn't a shortcut — it's becoming the standard. In the Asia Pacific, 80% of organisations are now sourcing talent remotely, and the data supporting this shift is compelling.

In this video, we break down what the new global workforce model actually looks like: where the talent is, what it costs, which roles are hardest to fill locally, and how companies are building distributed tech teams that genuinely perform.

Whether you're a startup scaling your first engineering team or an enterprise rethinking your talent strategy, this is the context you need.

🔗 Learn more about specialist IT recruitment across Asia: basecamp.com.sg

Music Credits: Life is a Dream by Michael Ramir C. @ Mixkit Stock Music