PurPassionSky

Theoretical / Computational Astrophysicist

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 anywhereMostly remote, but you show up sometimes
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
  • Manipulating variables, testing, seeing what happens.
  • Proposing what might be true and designing ways to find out.
  • Systematic, methodical pursuit of understanding.
  • Constructing explanations for why things work the way they do.
Also present
  • Seeing structure or signal in what looks like noise.
  • Working through a problem to its resolution.

In words

Theoretical astrophysics tries to explain why the universe behaves the way it does, using mathematics and computation rather than telescopes. The work spans a spectrum. At one end is pencil-and-paper theory — deriving how matter behaves near a black hole, or how structure grew in the early universe. At the other is large-scale computational astrophysics — building and running simulations of galaxy formation, stellar explosions, or planetary system dynamics on some of the world's most powerful computers, then mining the output for understanding. In practice most modern astrophysicists live somewhere in the middle, combining analytic insight with serious software.

The distinctive intellectual move is that the experiment is usually a simulation. Nobody can rerun the formation of a galaxy, so a model universe is built inside a computer, evolved under the laws of physics, and compared against what telescopes actually see. When model and observation disagree, something has been learned — either the physics in the model is incomplete or the observation is showing something new. That loop is the engine of the field, and it is why Discovery, not Creation, is the primary pull: the simulation is a tool for finding out, not an end in itself.

Explanation sits close underneath, because a theory that cannot be communicated — to observers, to students, to the wider field — does not travel. The best theoretical astrophysicists are often unusually good at making the abstract graspable.

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 code is the science, and the software engineering is real. Some of the field's most important simulation codes have been developed continuously for decades, and a large part of the job is reading, understanding, extending, and debugging large scientific codebases. People who imagine theory as pure mathematics are often surprised by how much of the day is spent programming.

A negative or null result is common and rarely publishable, which is demoralising in a way the field does not advertise. Months can go into a model that simply does not work, with little to show for it externally. Tolerance for that kind of ambiguity is an occupational requirement.

Physics, astrophysics, or maths degree, then a PhD in theoretical or computational astrophysics — STFC-funded in the UK [STFC/UKRI 2025-26] — followed by postdoctoral positions on the same pay scale as the rest of the field [from salary and job-posting data, Prospects/PayScale 2025-26]. Heavy programming skill (Python, often C/C++ or Fortran for performance, and experience with high-performance computing) is essential and is also exactly what makes this the easiest astrophysics specialism to convert into a high-paying data or software career later.

Before you go