Careers

Work where the analysis is the product.

We're a small team of senior engineers and operators who left industry to write honestly about the tools we used. No VC pressure. No pageview targets. Just the work.

How we work

01

Fully remote

Distributed across multiple time zones. Async-first, no mandatory standups.

02

Operator background required

Every writer has shipped production software or sat in the buying seat. We don't hire from journalism.

03

Output over hours

Evaluated on the quality of analysis, not hours logged. Most contributors work part-time alongside industry roles.

Open roles

Senior Editor, AI Infrastructure

Remote  ·  Part-time or full-time  ·  editorial@gaxonline.com

Open

We're looking for someone who has run production ML infrastructure: training pipelines, inference at scale, GPU procurement. You'll cover the hardware and cloud layer — H100/A100 spot markets, vLLM vs TGI benchmarks, inference API pricing. Background: 5+ years in ML infrastructure, MLOps, or AI platform engineering.

ML Infrastructure GPU Systems Distributed Systems Technical Writing

Senior Editor, SaaS & Pricing

Remote  ·  Part-time or full-time  ·  editorial@gaxonline.com

Open

We're looking for someone who has sat in finance ops, RevOps, or procurement at a Series A–D company. You understand the difference between list price and what companies actually pay. You'll cover enterprise SaaS pricing analysis, contract structures, and vendor lock-in economics.

SaaS Pricing RevOps Procurement Finance

What we look for

We look for

  • Direct industry experience in what you cover
  • Opinions backed by data
  • Ability to explain complex technical decisions in plain language
  • Comfort with public methodology and being cited or challenged

We don't need

  • Journalism degree or media background
  • Social media presence
  • Ability to write fast or at high volume
  • Experience with SEO or content marketing

The application

No CV required.

Send three things to editorial@gaxonline.com:

  1. 01 One piece of writing — your own or a ghost-written sample — that analyses a technical product decision.
  2. 02 A specific claim from our existing rankings that you think is wrong, and why.
  3. 03 One sentence on your production background.

We read every application. We don't use automated screening.

Contributors

Not looking for a full role? We work with independent contributors on a per-piece basis. If you have direct operator experience in a coverage area we don't yet have, pitch us.

Pitch us →