PurPassionDigital / Everywhere

Atmospheric Modeler

Unexpected

The pull to understand what isn't yet understood

Discovery · Unknown → Known

The shape of the work

Pace
  • A steady rhythm with room to breathe
  • A hard push you keep up for a long stretch
What your week looks likeQuiet stretches, then deadline storms
How much you move around at workScreen and chair, almost all day
Whether you can work from anywhereSome days in, some days wherever you want
How quickly you receive feedback on your workTakes a season or a project cycle
What you're actually working withNumbers, measurements, records — things you read on a screen / Concepts, theories, designs, stories — things you think up

Behaviours this work is made of

Core
  • Breaking something into its real components.
  • Applying systematic problem-solving to make things work reliably.
  • Building a simplified version of a system — a climate, a river, a city's traffic — to test what might happen.
  • Working through a problem to its resolution.
Also present
  • Taking something that works and making it work better.
  • Seeing structure or signal in what looks like noise.
  • Systematic, methodical pursuit of understanding.

In words

The object of the work is the model itself — the numerical code that produces weather forecasts, climate projections, and atmospheric research simulations, built, improved, and maintained over years. It sits at the intersection of atmospheric physics, applied mathematics, and scientific computing. What is known about how the atmosphere behaves — equations governing fluid motion, radiation transfer, cloud microphysics, boundary layer turbulence, chemical reactions — gets encoded into software that runs on some of the most powerful computers on the planet.

The modeling challenge is both scientific and computational. The atmosphere operates across scales that span nine orders of magnitude — from molecular-scale cloud droplet formation to planetary-scale circulation patterns. No computer can resolve all of these scales simultaneously, so every model involves parameterizations — simplified representations of processes that happen at scales the model can't resolve. Getting these parameterizations right is one of the most consequential scientific challenges in the field, because every forecast and every climate projection depends on them.

This is one of the most computationally intensive scientific endeavors that exists. Global weather models run on supercomputers that rank among the world's fastest. The code bases are large, complex, and often written in Fortran — a language that is unfashionable in the broader software world but remains dominant in atmospheric modeling because of its performance characteristics on high-performance computing architectures.

There's a guide here if you want one

Kitsune can talk through anything on this page — whether it might suit you, what to do next, questions this page doesn't answer. Everything here is yours to read either way.

The connection to "weather" in the public sense is more distant than the job title implies. An atmospheric modeler might go months without looking at an actual weather forecast in a professional context. The work is about the model — its physics, its numerics, its performance characteristics — not about today's weather. Forecasting tomorrow's weather is the operational forecaster's job; building the tool that makes tomorrow's forecast possible is this one.

The legacy code challenge is real. Some of the world's most important weather and climate models contain code that has been continuously developed for decades. Working with, understanding, and improving legacy scientific code is a significant part of the job. Modern software engineering practices are penetrating the field, but slowly.

The career sits at a strange intersection of scientific prestige and public invisibility. The models these people build underpin every weather forecast in the world and every climate projection that informs policy. The modelers themselves are almost entirely unknown outside the field. Recognition is not among the things this role supplies.

Bachelor's in physics, mathematics, computer science, atmospheric science, or engineering, followed by a graduate degree (master's or PhD) with a focus on numerical modeling, computational atmospheric science, or a related area. Strong programming skills are essential — Python, Fortran, C/C++, and experience with high-performance computing environments. Positions at national weather modeling centers (NCEP, ECMWF, Met Office), research labs (NCAR, GFDL, NASA GSFC), and universities. The field also employs people with backgrounds in applied mathematics and computational fluid dynamics who develop expertise in atmospheric applications.

Before you go