---
title: "C++ | Skills We Assign For | Azendo"
description: "C++ for performance-critical work — where it is justified, what it costs, plus the Azendo roles assigned for it."
url: "https://azendo.co/skills/cpp/"
---

[Skills](https://azendo.co/skills/) Languages and runtimes 

# C++.

C++ is a compiled systems language offering direct memory control and no mandatory runtime overhead. In data and quantitative work it appears where latency or throughput requirements exclude interpreted languages.

## Where C++ fits on a long engagement.

C++ is chosen when a measured requirement excludes the alternatives: microsecond-scale latency, tight memory budgets, or throughput where an interpreted language's overhead dominates. That is a narrow set of situations, and outside it the productivity cost is rarely repaid.

Modern C++ is a substantially safer language than its reputation, provided the codebase actually uses it. Smart pointers, RAII and the standard containers eliminate most manual memory management, but a codebase mixing modern idioms with raw pointers inherited from older code has the failure modes of both.

## What an assigned team does with C++.

The defects C++ permits are the expensive kind. Memory corruption and undefined behaviour produce failures far from their cause, sometimes months later, and diagnosing them requires tooling and experience rather than reasoning about the source.

Sanitisers and static analysis in the build are not optional refinements here; they are how the language is made survivable, and they are part of the delivery standard scoped under [how the monthly fee is built](https://azendo.co/pricing/).

## What we use C++ for.

* Latency requirements that exclude alternatives Work where a measured microsecond budget rules out an interpreted runtime.
* Consistent modern idioms RAII and smart pointers throughout, rather than mixed with inherited raw pointers.
* Sanitisers in the build Memory and undefined-behaviour detection running continuously rather than after a crash.

## How C++ capacity is assigned.

C++ capacity is assigned under [outsource software development services](https://azendo.co/services/software-development/), with the performance requirement established by measurement before the language is chosen.

## Roles we assign C++ for

* [Quantitative Analyst Data science](https://azendo.co/services/data-science/quantitative-analyst/)

## Service lines it sits in

* [Data science](https://azendo.co/services/data-science/)

Capacity is agreed as a committed monthly capacity across a discipline, not per skill.

## Related in languages and runtimes

* [Python — skill we assign for](https://azendo.co/skills/python/)
* [Java — skill we assign for](https://azendo.co/skills/java/)
* [TypeScript — skill we assign for](https://azendo.co/skills/typescript/)
* [Node.js — skill we assign for](https://azendo.co/skills/nodejs/)
* [React — skill we assign for](https://azendo.co/skills/react/)
* [Next.js — skill we assign for](https://azendo.co/skills/nextjs/)
* [R — skill we assign for](https://azendo.co/skills/r/)
* [.NET — skill we assign for](https://azendo.co/skills/dotnet/)

## Tell us what your roadmap needs C++ for.

A service delivery manager replies with the disciplines we would assign, the monthly capacity and what the first month looks like.

[All skills we assign for](https://azendo.co/skills/)