The problem I solve
Research code works on a laptop. Then it has to run at scale, get handed to another team, or survive production - and it falls apart. Not because the scientist erred: research code and production software optimize for different things.
I've lived on both sides of that line - physics at CERN, HPC at a defense lab, and now systems running millions of tasks at 99.99%+ uptime in aerospace.
What I bring
HPC & Computing
Physics Domain
Modernization
Production
Good fit for
- Research labs or universities with prototype code that needs to scale or survive a handoff
- Teams stuck on legacy MATLAB or Fortran that needs modernizing without breaking the science
- Startups running simulations too slow to iterate on
- Anyone who needs a physicist who can also ship software
How we'd start
- 01 You email me what you're stuck on. A slow simulation, a handoff that keeps breaking, legacy code no one wants to touch.
- 02 A 30-minute call to see if it's a fit. No pitch deck - I'll tell you straight whether I'm the right person for it.
- 03 We start with a small, scoped piece. Something concrete with a clear outcome, so you can judge the work before committing to more.
Questions
Are you taking on work right now?
Yes - a project or two at a time, so I stay hands-on. If timing is tight, say so and I'll be straight about whether I can do it justice.
Remote or on-site?
Remote by default. I can travel for a kickoff or for work that has to happen on-site.
How do you price?
No rate cards yet. We scope a small first piece, agree on it, and go from there - hourly or fixed, whatever fits the work.
Can you handle sensitive work?
I've worked in defense and aerospace under NDA and compliance regimes (NIST 800-53, NASA NPR 7123). Happy to sign an NDA before we get into specifics.
Tell me what you're working on and where it's stuck. If it's a fit, we'll start small; if not, I'll point you the right way. Either way, I reply within a day.