OR-Path Market Intelligence Q2-2026

Hello OR-Path readers,

What did the Operations Research job market actually demand in Q2 2026?

For this edition, we analyzed 53 job descriptions captured by OR-Path during Q2, across North America, Europe, Asia, Latin America and multi-region opportunities.

The purpose is simple: look beyond job titles and understand what employers are actually asking OR and optimization professionals to know, build and deliver.

This is a curated dataset, not a census of the global labor market. But within these 53 descriptions, several patterns stand out.

Let’s take a closer look.

Base: 53 job descriptions.

One of the most notable characteristics of Q2 is the relatively balanced geographic distribution.

Europe accounts for 28.3% of the sample, North America for 26.4%, and Latin America for 24.5%.

That is a much less concentrated picture than one dominated by a single region.

The work-arrangement mix is also distinctive:

Almost half of the Q2 sample is classified as remote.

🔎 Insight: Q2 shows a geographically distributed OR market in this dataset, with remote work playing a particularly visible role. But remote should still be read together with location restrictions: many remote positions are tied to a specific country or region.

Base: 53 job descriptions.

More than half of the Q2 descriptions — 50.9% — do not make seniority explicit in the title.

Explicit Senior roles account for 28.3%, while Lead, Staff, Principal and Expert titles represent another 9.4%.

Junior and Associate roles represent 3.8%, with one internship in the sample.

🔎 Insight: Q2 continues to show a meaningful concentration of experienced roles, but titles alone do not tell the whole story. For more than half of the sample, candidates need to look at responsibilities, expected autonomy and technical ownership to understand the true level of the position.

Base: 53 job descriptions. Categories overlap.

Python appears in 84.9% of the Q2 descriptions.

That makes it the clearest individual technical skill in the sample.

Signals related to production, deployment and integration appear in 75.5% of the descriptions.

This is one of the strongest findings in Q2.

It suggests that many of these roles expect professionals not only to formulate or solve optimization models, but also to connect them to operational systems, applications and production environments.

LP / MIP / MILP appears in 47.2% of the sample.

Among named tools:

These percentages measure mentions in job descriptions. They should not be interpreted as solver market share or as mandatory requirements in every role.

Machine learning appears in 43.4% of Q2 descriptions.

Simulation appears in 30.2%, while forecasting appears in 11.3%.

Explicit references to LLMs or generative AI appear in 22.6%.

🔎 Insight: Q2 reinforces a hybrid technical profile: mathematical optimization remains central, but employers frequently combine it with software engineering, machine learning and production implementation.

The recurring expectation is not simply to build a mathematically correct model.

It is to build something that can operate inside a broader decision system.

The dataset does not use a standardized industry classification, so the most consistent way to analyze application areas is through the operational-problem fields coded in each description.

Base: 53 job descriptions. Categories overlap.

Scheduling is the most frequent explicitly coded problem area, appearing in 34.0% of Q2 descriptions.

Inventory appears in 20.8%, followed by routing and dispatch at 18.9%.

Stochastic or robust optimization appears in 15.1%.

Pricing and revenue applications appear in 5.7%.

These categories can overlap. One role can involve scheduling, inventory and uncertainty at the same time.

🔎 Insight: The Q2 sample reinforces the breadth of OR applications. What connects these jobs is not a single industry, but the need to make constrained decisions involving resources, time, networks, inventory and uncertainty.

Base: 53 job descriptions. Categories overlap.

Advanced degrees remain prominent in Q2.

A Master’s degree is mentioned in 58.5% of descriptions, while a PhD appears in 41.5%.

Bachelor’s degrees appear in 26.4%.

These categories overlap, and a mention does not necessarily mean that the degree is an absolute requirement. Some descriptions present different educational paths or distinguish between preferred and required qualifications.

🔎 Insight: Academic depth remains relevant in OR hiring, but the practical interpretation matters. Candidates should read whether a degree is required, preferred or one option among alternative experience profiles.

Claude Code, Codex, and Cursor are on every engineer's stack. Most still treat them like a search bar. Top engineers work from a system, these 100+ prompts are that system. Sign up for The Code and get the prompts free, plus a 5-minute daily newsletter to keep sharpening your edge.

Claim your free prompts

Q2 points to a clear combination of skills.

With Python appearing in 84.9% of the descriptions, strong programming capability remains one of the most consistent signals in the dataset.

Production, deployment and integration appear in 75.5%.

That makes implementation capability almost as visible as Python itself.

Understanding APIs, software architecture, data flows or how optimization services interact with operational systems can therefore complement modeling expertise.

LP / MIP / MILP appears in 47.2% of Q2 descriptions.

Gurobi appears in 45.3% and CPLEX in 30.2%.

The fundamentals of mathematical optimization remain highly relevant.

Machine learning appears in 43.4%, simulation in 30.2%, and LLMs / generative AI in 22.6%.

The dataset suggests that OR professionals increasingly operate alongside other quantitative and AI methods rather than in isolation.

Scheduling appears in 34.0% of descriptions, inventory in 20.8%, and routing / dispatch in 18.9%.

Being able to say which decision you improved gives context to the optimization methods you know.

Because 50.9% of Q2 roles do not make seniority explicit in the title, candidates need to evaluate the actual responsibilities and level of ownership described in the posting.

A useful framework remains:

What decision are you improving?

How are you modeling it?

How are you implementing it?

And how does the solution reach the operation?

The Q2 2026 sample shows an Operations Research market strongly connected to software implementation and operational decision systems.

Python appears in 84.9% of the 53 descriptions.

Production, deployment and integration appear in 75.5%.

Mathematical optimization remains central, with LP / MIP / MILP appearing in 47.2% and Gurobi in 45.3%.

Machine learning appears in 43.4%, while explicit LLM or generative-AI references reach 22.6%.

At the application level, scheduling leads at 34.0%, followed by inventory at 20.8% and routing / dispatch at 18.9%.

And geographically, Q2 is notably distributed: Europe represents 28.3%, North America 26.4%, and Latin America 24.5% of the analyzed sample.

Strong OR profiles combine mathematical modeling, programming, implementation and an understanding of the operational decision being improved.

If these patterns match what you are seeing in your own market or career, reply to this newsletter or connect with OR-Path.

I’d be interested to hear what you are seeing in Operations Research hiring.

Until next time 👋
OR-Path newsletter