Skip to sources
Time Machine

Operations research analysts

Also called Decision scientist, Optimization analyst, Supply chain analyst, Management scientist, Network analyst

In brief

In May 2025, BLS counted 108,510 US operations research analysts, with median pay of $88,940 a year. Of the BLS counts since 2003, the highest was 117,880, in May 2023. The earliest figure here is an estimate of 2,000 from 1952, not measured the same way as today's count. The last full technology era for operations research analysts: Python ML stack + cloud compute, 2015 to 2022.

What the sources say

Official outlook

BLS projects employment to grow 11.9% from 2025 to 2035.

BLS Employment Projections 2025-35

AI exposure studies

Data as of BLS OEWS May 2025; BLS Employment Projections 2025-35. BLS publishes these counts as yearly survey snapshots and cautions against reading them as a precise trend. In May 2021 BLS changed how it estimates these counts (a model-based method using three years of survey data) and moved fully to the 2018 occupation codes, so part of a change across 2021 can come from the method rather than the work.

Last updated .

Cite this page
APA

Future History. (2026, October 11). Operations research analysts: jobs and pay since 1952 [Data set; data as of BLS OEWS May 2025; BLS Employment Projections 2025-35]. https://futurehistory.earth/timeline/15-2031

Chicago

Future History. "Operations research analysts: jobs and pay since 1952." Data as of BLS OEWS May 2025; BLS Employment Projections 2025-35. Last modified October 11, 2026. https://futurehistory.earth/timeline/15-2031.

BibTeX

@misc{futurehistory_15_2031, author = {{Future History}}, title = {Operations research analysts: jobs and pay since 1952}, year = {2026}, month = oct, howpublished = {\url{https://futurehistory.earth/timeline/15-2031}}, note = {Last updated 2026-10-11. Data as of BLS OEWS May 2025; BLS Employment Projections 2025-35}, }

The access date is today's date on your device.

drag to travel through time
195019752000now
2026
Known then as Operational Research Scientist / Analyst (British military coinage)
Known then as Operations Research Analyst / Management Scientist (post-war civilian adoption)
Known then as Operations Research Analyst / Industrial Engineer / Management Scientist
Known then as Operations Research Analyst / Decision Scientist (early computing era)
Known then as Operations Research Analysts (BLS SOC 15-2031)
Known today as Operations Research Analysts (BLS SOC 15-2031)
Projected to still be called Operations Research Analysts (BLS SOC 15-2031)
Data from the May 2025 survey
US Employment
109K
Est.

Stated in source: BLS OEWS

Official statistic
Report an error
Median Annual Wage
$88,940
Est.

≈ $86,660 in 2024 prices (derived by us, CPI-adjusted)

Official statistic
Report an error
Beat · 1937

A. P. Rowe coins the term "operational research" at the Bawdsey Research Station in the UK while working on how to operationalize radar data into an air defense system. The RAF subsequently creates OR sections throughout its commands, setting the institutional template for embedding analysts in operational units rather than isolating them in research departments. The discipline is born military, multidisciplinary, and results-focused.

Beat · 1942

Philip Morse organizes ASWORG, the Anti-Submarine Warfare Operations Research Group, for the US Navy in early 1942. By 1945 it has grown to over seventy analysts. The group's work on convoy routing, search patterns, and depth-charge settings demonstrably improved the kill rate of German U-boats. George Kimball, Morse's deputy, later co-authors with Morse the first OR textbook, "Methods of Operations Research" (1952), which codifies the discipline's methods for a peacetime civilian audience.

Beat · 1947

George Dantzig, working on US Air Force planning problems at the Pentagon, invents the simplex method for linear programming during the summer of 1947. He is later challenged by colleague Marshall Wood to see whether it is possible to mechanize the Air Force's planning process; the result is Project SCOOP and the first large-scale LP implementation. Dantzig later says that arriving late to a statistics class and assuming two unsolved problems on the blackboard were homework assignments was what put him on the path to the work.

Beat · 1952

On May 26, 1952, seventy-three academics, military analysts, and industry researchers gather at the Arden Estate in Harriman, New York, to found the Operations Research Society of America. Philip Morse, who organized ASWORG for the Navy in 1942, serves as the first president. The following year, The Institute of Management Sciences (TIMS) is founded to serve the business-management audience for the same methods. The two societies will merge into INFORMS in 1995.

Beat · 1959

American Airlines' SABRE (Semi-Automated Business Research Environment) reservation system, developed with IBM between 1957 and 1964, becomes one of the first large-scale commercial applications of OR and computer science together. The airline industry will remain one of OR's most intensive application domains through the end of the 20th century: seat pricing, crew scheduling, fleet assignment, and gate planning are all LP and IP problems at massive scale. SABRE's direct operating cost savings are estimated at roughly $30 million annually in 1960s dollars by the time it goes live.

Beat · 1995

On January 1, 1995, the Operations Research Society of America (ORSA, founded 1952) and The Institute of Management Sciences (TIMS, founded 1953) merge to form INFORMS: the Institute for Operations Research and the Management Sciences. The merger reflects the disciplinary convergence of OR methods with management science, decision theory, and early analytics. INFORMS counts approximately 12,500 members at its founding. The merger coincides with the explosion of internet-based commercial optimization: Amazon (1994), Priceline (1997), and eBay (1995) will all become major employers of OR and operations analytics talent within a decade.

Beat · 2013

INFORMS launches the Certified Analytics Professional (CAP) credential in 2013, the first professional certification specifically for analytics practitioners. The CAP exam tests competency across the analytics lifecycle: problem framing, data modeling, analytics technique selection, deployment, and lifecycle management. The credential addresses a growing concern in the profession: as "data science" and "analytics" became buzzwords adopted by workers with very different skill levels, OR practitioners sought a way to distinguish rigorous quantitative work from dashboard-building and descriptive statistics. By 2026 more than 1,800 professionals hold the CAP credential.

Beat · 2023

The release of GPT-4 in March 2023 and Cursor in late 2023 marks a qualitative shift in how OR analysts write optimization models. Analysts at supply chain firms, management consultancies, and tech companies begin using LLM coding assistants to scaffold PuLP, OR-Tools, and Gurobi formulations from natural-language problem descriptions. Gurobi documents that LLMs and mathematical solvers are complementary: LLMs bring fluency and problem articulation while solvers provide the provable precision that optimization problems require, with human–AI–solver loops as the emerging practice. Model validation by a trained OR professional remains essential as AI-generated formulations proliferate. BLS responds by projecting 21% growth for the occupation in its 2024-34 cycle, the strongest projection the role has ever received.

How to read this number

OEWS is a point-in-time survey snapshot, not a continuous time series; BLS advises against using it for year-over-year trend comparison.

Each dot is a cited figure over time; the dotted line only links them (values between aren't measured). Hollow dots are estimates.

Official statistic: Copied by a script from a statistics agency table or a published study's table, not retyped by hand. BLS figures and the forecast and exposure tables are also re-checked against that table on every data run. Researched context: Researched from the cited source rather than copied from it by a script, so it is not machine-checked yet. Spot a mistake? Each figure has a “Report an error” link.

Cited forecasts · present → 2035

Will AI replace operations research analysts? What the research says

Each figure is stated by the named source; we publish no forecasts of our own. Where sources disagree, we show the disagreement rather than an average.

Each figure is stated by the named source; we publish no forecasts of our own. Where sources disagree, the spread is the honest signal.

What published forecasts say
Forecast change in the number of people doing this work, as published by each named source. Bars share one scale on every role, centred on zero and reaching the end at ±30%. Grey marks a small change, 3% or less either way.
BLS Employment Projections 2025-35
→ 2035
+11.9%
BLS National Employment Matrix, 2025-35 cycle, line for SOC 15-2031 (Operations research analysts): 113.1 thousand jobs in 2025, projected 126.6 thousand in 2035, a change of +13.5 thousand (+11.9%). Matrix employment counts all jobs in the occupation, including self-employed workers. The average for all occupations in this cycle is +3.5%.
Official statisticReport an error
How exposed is this work to AI (research measures)
Scores as published by each study. Each row says what it measures. These measure what AI could technically do, not forecasts of jobs lost.
Eloundou et al. (2023), "GPTs are GPTs"
2023 study · Share of tasks exposed to LLMs (β, human-rated)
62.9%
of tasks
What this measures

Published occupation-level exposure from the paper's occ_level.csv for O*NET-SOC 15-2031.00 Operations Research Analysts. Shown: human-rated β = 0.629, the share of the occupation's tasks an LLM could do in at least half the time at equal quality, counting tasks that need LLM-powered software at half weight (β = E1 + 0.5 × E2). Other published measures for this occupation: human-rated α (LLM alone) 0.258 and γ (all LLM-assisted) 1; GPT-4-rated β 0.629. This measures how much of the work an LLM could touch, not how many jobs disappear.

Official statisticReport an error
Today, in this role

What's changing day to day for operations research analysts

Three parts of your work where AI is already doing real lifting, and what stays yours.

AI is sitting alongside you hereGenerate first-pass linear and mixed-integer programming model code using Cursor or Claude Code: provide a natural-language problem statement with data schema and constraints

Generate first-pass linear and mixed-integer programming model code using Cursor or Claude Code: provide a natural-language problem statement with data schema and constraints; direct the LLM to scaffold a PuLP, OR-Tools, or Gurobi model; then review, debug, and harden the generated formulation before solving.[7],[6]

Tools picking this up
Where your edge is

The LLM scaffolds the constraint structure but routinely misinterprets integrality requirements, capacity symmetries, or time-coupling constraints in multi-period models. Build a personal checklist of "common LLM formulation errors" and always test generated code on a small toy instance with a known optimal solution before scaling.

AI is sitting alongside you hereDesign and implement network flow and routing optimization for logistics and distribution: use OR-Tools or Gurobi to model vehicle routing problems (VRP) or network flow problems

Design and implement network flow and routing optimization for logistics and distribution: use OR-Tools or Gurobi to model vehicle routing problems (VRP) or network flow problems; validate routes against real-world road constraints, driver hour rules, and customer time-window commitments that the base solver formulation may under-specify.[7],[2]

Tools picking this up
Where your edge is

VRP solvers and their LLM-generated wrappers routinely miss soft constraints: driver preferences, customer relationship accommodations, and last-minute re-optimization windows. Build a constraint-review protocol and maintain a library of real-world edge cases from your domain to systematically test new formulations against.

AI is sitting alongside you hereRun supply-chain scenario planning using Kinaxis Maestro or o9 Solutions: configure digital twin models of procurement, production, and distribution networks

Run supply-chain scenario planning using Kinaxis Maestro or o9 Solutions: configure digital twin models of procurement, production, and distribution networks; trigger AI-generated what-if scenarios (demand shock, supplier failure, tariff change); interpret risk scores and recommended re-plan actions for supply chain directors.[8],[9]

Where your edge is

Digital twin platforms generate scenario options rapidly but the selection logic (which scenario to enact given strategic priorities, relationship constraints with suppliers, and regulatory environment) is an irreducibly human judgment. Build expertise in the "why" behind each scenario recommendation so you can override confidently when the platform's assumptions don't match ground truth.

Where operations research analysts go next

Natural next steps for someone with your foundation: not exits, evolutions.

What each move takes

A direction you could grow

Logisticians

OR analysts who specialize in supply chain and logistics optimization have deep transferable knowledge of inventory models, network flow, and demand variability: the same domain expertise Logisticians apply in day-to-day operations management. As AI absorbs model-construction work, OR analysts who shift into Logistician roles gain broader operational authority, supplier relationship management, and change-management scope. BLS projects growth for Logisticians through 2032, driven by supply-chain resilience investment post-COVID. The transition is natural for OR analysts who prefer operational execution over analytical modeling.

What you'd add
· Warehouse management systems (WMS) and 3PL contract management
· Import/export compliance, trade regulations, and customs procedures
What it takesMost of your skills carry over
Tools of the era

How has the work of operations research analysts changed since 1937?

The tools that defined the work, one line per era. Select an era to see how it reshaped the work.

  • Empirical field observation + probability tables (pre-computing OR)

    The first operational research work used no computers: Blackett's teams at Coastal Command collected combat reports by hand, built frequency tables of U-boat sighting distances and patrol aircraft tracks, and applied classical probability and statistics from paper tables. The tools were slide rules, actuarial tables, and systematic observation forms. The insight was methodological: that disciplined data collection and mathematical analysis of operations in progress could improve outcomes faster than intuition or tradition alone. This era established the fundamental OR discipline of treating operational problems as quantitative decision problems, regardless of whether a computer was available to solve them.

  • Linear programming + mainframe batch computing (Dantzig simplex, IBM 701/7090)

    George Dantzig's simplex algorithm, developed at the Pentagon in 1947, was the first general-purpose computational method for finding optimal solutions to constrained resource allocation problems. It made linear programming tractable for real industrial problems: the Air Force's Project SCOOP (Scientific Computation of Optimal Programs) tested the simplex on IBM mainframes from 1952. By the late 1950s, RAND Corporation and major defense contractors were solving LP problems with hundreds of variables on IBM 701 and 7090 machines. The key constraint was batch computing: an OR analyst would submit a deck of punched cards overnight and receive results the next morning. Model development was slow, debugging was laborious, and computational scale was the binding limit. Airlines (American Airlines' SABRE reservation and yield-management precursors), oil refineries (refinery scheduling was among the earliest commercial LP applications), and defense logistics all benefited from this era.

    Effect on the work

    Linear programming on mainframes enabled problems to be solved that previously required armies of clerks doing iterative manual calculations. A single OR analyst with LP model access could solve scheduling and allocation problems that had previously been either intractable or left to managerial rule-of-thumb. The era grew OR as a profession rather than displacing any existing role.

  • Interactive computing + commercial LP solvers (IBM System/360, LINDO, MPS/360)

    IBM's System/360, introduced in 1964, and the shift toward interactive time-sharing computing in the late 1960s and 1970s fundamentally changed how OR analysts worked. LINDO (Linear Interactive and Discrete Optimizer), developed at the University of Chicago in 1980, democratized LP by running on minicomputers. The OR analyst's role shifted from supervising batch runs to interactively building and testing models. Simulation emerged as a parallel tool set (GPSS, SIMSCRIPT), and network flow algorithms (Ford-Fulkerson, Dijkstra) enabled routing and scheduling problems to be solved at new scale. This era also saw OR expand beyond defense into healthcare scheduling, telecommunications network planning, and early financial optimization.

  • Personal computing + spreadsheet modeling (Lotus 1-2-3 1983, Excel 1985, What's Best! / @RISK)

    The IBM PC and the spreadsheet transformed OR from a specialist mainframe activity into something a manager with a laptop could attempt independently. Lotus 1-2-3 (1983) and Excel (1985) put linear programming add-ins (What's Best! for LP, @RISK for Monte Carlo simulation) into the hands of decision-makers who had never written Fortran. This democratization was a double-edged development for OR professionals: it expanded the market for analytical thinking throughout organizations while simultaneously reducing the barrier to entry for basic optimization and simulation work. The professional OR analyst's comparative advantage shifted toward complex multi-period, multi-constraint, stochastic models that Excel could not handle, and toward the interpretation and deployment work that spreadsheet models left untouched.

  • Commercial solver platforms + supply chain digital twins (Gurobi 2008, CPLEX, SAP APO, Kinaxis)

    The late 1990s and 2000s brought solver technology to its modern form. CPLEX (acquired by IBM in 2009) and Gurobi (founded 2008 by former CPLEX developers) became the benchmark MIP solvers, capable of solving problems with millions of variables in minutes that would have taken days on 1980s hardware. Simultaneously, enterprise supply chain planning platforms (SAP Advanced Planner and Optimizer, Kinaxis RapidResponse, JDA) embedded OR optimization into business processes: an OR analyst at a major manufacturer no longer needed to write solver code from scratch but instead configured and validated platform models and interpreted their outputs for operations teams. Python (SciPy, PuLP) arrived as the coding platform that replaced Fortran and COBOL in custom OR work. The discipline professionalized: the INFORMS Certified Analytics Professional (CAP) credential launched in 2013 to distinguish professional OR practitioners from generalist analysts.

    Effect on the work

    The platform era significantly expanded who could use optimization: supply chain managers without OR training could operate solver platforms as configured tools. This did not reduce OR analyst employment; it expanded the scope of optimization adoption fast enough to grow the workforce substantially. The BLS OEWS series for 15-2031 shows steady employment growth from 2000 onward.

  • Python ML stack + cloud compute (scikit-learn, PyTorch, AWS/Azure, Jupyter notebooks)

    Python's ecosystem for scientific computing matured in the 2013-2016 period (NumPy, SciPy, pandas, scikit-learn, and then PyTorch) and cloud compute made large-scale optimization and simulation economically accessible to organizations that could not afford dedicated HPC clusters. The OR analyst role became a hybrid: traditional prescriptive optimization (LP, MIP, simulation) combined with machine learning inputs (demand forecasting, anomaly detection, price elasticity modeling) that fed optimizer parameters. The job title landscape fragmented: "Data Scientist," "Decision Scientist," "Applied Scientist," "Analytics Engineer," and "Planning Analyst" all described roles that, in an earlier era, would have simply been called operations research. Many practitioners working in logistics, pricing, revenue management, and supply chain did not formally identify as OR analysts even though their work was OR in substance.

  • LLM-augmented optimization (Cursor + Claude Code for PuLP/Gurobi scaffolding, AI supply chain platforms)

    GPT-4 (March 2023) and purpose-built coding assistants like Cursor (2023) and Claude Code (2025) changed how OR analysts build models: a natural-language description of a vehicle routing problem or a workforce scheduling challenge can generate a first-pass PuLP, OR-Tools, or Gurobi formulation in minutes, compared to hours of manual coding. Kinaxis Maestro (launched 2024) and o9 Solutions embedded generative AI into supply chain planning platforms, producing AI-recommended re-plan actions in response to disruption scenarios and generating natural-language explanations of recommended changes. Gurobi documents that LLMs and mathematical solvers are complementary: LLMs contribute fluency and problem articulation while solvers provide the provable precision optimization requires, with human-AI-solver loops emerging as the new standard workflow. The net effect is that junior-tier formulation work is now substantially AI-augmented, while the irreducibly human tasks (problem framing with operating stakeholders, model validation against physical reality, deployment change management) are becoming more rather than less valuable as AI-generated models proliferate and require expert review.

    Effect on the work

    BLS projects employment growth for 15-2031 in the 2024-2034 cycle, the fastest-growing outlook the occupation has ever received. The profession is growing into AI augmentation rather than shrinking from it: organizations that previously could not afford full-time OR staff can now access OR-quality optimization via platforms, while organizations that already had OR capacity are expanding the scope of problems they attack.

Part of Tech & Data · see all 28 roles →
Different role?

See the same long-arc view for your own profession.

Browse the directory by industry, or search by title or SOC code.

Browse all roles

Operations Research Analysts employment and pay by year

On record since1937
Latest US employment108,510 (May 2025)Source: BLS OEWS May 2025Official statisticReport an error
Latest US median pay$88,940 (May 2025)Source: BLS OEWS May 2025Official statisticReport an error
Outlook+11.9% by 2035Source: BLS Employment Projections 2025-35Official statisticReport an error
View all 29 years of cited US data, each linked to its source
YearUS employmentAnnual pay (median unless marked)SourceReport
19522,000n/aEst., INFORMS Researched contextReport
1960n/a$8,500Est., University of Missouri Libraries Researched contextReport
197025,000n/aEst., INFORMS History of O.R Researched contextReport
1985n/a$34,000Est., University of Missouri Libraries Researched contextReport
199057,000n/aBLS CPS 2019 Researched contextReport
200059,820n/aBLS OEWS 2000 Official statisticReport
200358,080$58,300BLS OEWS May 2003 Official statisticReport
200455,030$60,190BLS OEWS May 2004 Official statisticReport
200552,530$62,180BLS OEWS May 2005 Official statisticReport
200656,170$64,650BLS OEWS May 2006 Official statisticReport
200758,750$66,950BLS OEWS May 2007 Official statisticReport
200860,860$69,000BLS OEWS May 2008 Official statisticReport
200960,960$70,070BLS OEWS May 2009 Official statisticReport
201062,210$70,960BLS OEWS May 2010 Official statisticReport
201165,030$71,950BLS OEWS May 2011 Official statisticReport
201269,180$72,100BLS OEWS May 2012 Official statisticReport
201372,680$74,630BLS OEWS May 2013 Official statisticReport
201486,950$76,660BLS OEWS May 2014 Official statisticReport
201595,860$78,630BLS OEWS May 2015 Official statisticReport
2016109,150$79,200BLS OEWS May 2016 Official statisticReport
2017106,050$81,390BLS OEWS May 2017 Official statisticReport
2018104,200$83,390BLS OEWS May 2018 Official statisticReport
201999,680$84,810BLS OEWS May 2019 Official statisticReport
202096,220$86,200BLS OEWS May 2020 Official statisticReport
202198,700$82,360BLS OEWS May 2021 Official statisticReport
2022105,080$85,720BLS OEWS May 2022 Official statisticReport
2023117,880$83,640BLS OEWS May 2023 Official statisticReport
2024107,760$91,290BLS OEWS May 2024 Official statisticReport
2025108,510$88,940BLS OEWS May 2025 Official statisticReport
Embed this timeline on your site

Free for any site. Paste this where the timeline should appear; it stays interactive, every datapoint stays cited, and it sets no cookies on your page. How embedding works

<iframe src="https://futurehistory.earth/embed/15-2031"
  width="100%" height="430" style="border:0"
  title="Operations Research Analysts, a Future History timeline"
  loading="lazy"></iframe>
<p style="font-size:13px;margin:4px 0 0"><a href="https://futurehistory.earth/timeline/15-2031">Operations Research Analysts: jobs and pay over time</a>, from Future History</p>

See all roles in Tech & Data