---
title: "MATLAB | Skills We Assign For | Azendo"
description: "MATLAB in engineering and research — existing models, migration questions, plus the Azendo roles assigned for it."
url: "https://azendo.co/skills/matlab/"
---

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

# MATLAB.

MATLAB is a numerical computing environment and language used in engineering, control systems, signal processing and quantitative research, with toolboxes covering specialised domains and code generation for embedded targets.

## Where MATLAB fits on a long engagement.

MATLAB estates are usually research assets: models developed over years by engineers or quantitative researchers, validated against physical systems or market data, and trusted precisely because they have been used for a long time. They are rarely written as production software, because that was not the purpose.

The tension arrives when a model needs to run in production. Rewriting in Python risks losing behaviour that was never fully specified anywhere but the MATLAB code; keeping MATLAB in production means licensing and an integration path. Neither answer is automatically right, and the decision needs the validation cost accounted for honestly.

## What an assigned team does with MATLAB.

The safest route is usually a rewrite with rigorous equivalence testing against the original across a wide input range, rather than either a blind port or an assumption that the two will agree.

That testing is the bulk of the work and the part most often underestimated, which is why it is scoped explicitly as part of [how the monthly fee is built](https://azendo.co/pricing/).

## What we use MATLAB for.

* Existing models understood before moving Behaviour documented, because the code is often the only specification.
* Equivalence testing across the input range A rewrite verified against the original rather than assumed to match.
* Integration where a rewrite is not justified MATLAB called from a production system, where porting cost exceeds the benefit.

## How MATLAB capacity is assigned.

MATLAB work is assigned under [managed data services](https://azendo.co/services/data-engineering/), with equivalence validation scoped as the main deliverable in any migration.

## Roles we assign MATLAB 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 MATLAB 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/)