runpoint.home
Command Palette
Type to search. Press Enter for the top match.

Careers at Runpoint

Work with people who ship with AI.

Runpoint hires people who can turn ambiguous business problems into working systems. Every role builds in some form. Every role demands business acumen, technical judgment, and an AI-native workflow.

Setup

Fully remote

Path

Contract to full-time

Open roles

9 active

Cadence

Rolling

Open roles · 09

Nine ways to join.

01 / 09
Core· Remote· AI-native· Client-facing

Operator-Engineer

The core Runpoint role. Business taste, technical judgment, and AI-native delivery in one person.

Read role →
02 / 09
Specialist· Remote

AI Security Expert

For someone fully AI-pilled who still has real security judgment. Useful paranoia, not compliance cosplay.

Read role →
03 / 09
Builder· Remote

Cracked Engineer

For the engineer already living in Claude Code and Codex, generating nearly all code with LLMs, and still keeping quality high.

Read role →
04 / 09
Enablement· Remote

Developer Enablement

Help client engineering teams get more from AI across tools, workflows, deployment, infrastructure, and DevOps.

Read role →
05 / 09
Deployment· Remote

Hermes Deployment Expert

Install, configure, adapt, train, and support Hermes inside real companies with messy workflows.

Read role →
06 / 09
Client workshop· Remote

Fractional Chief AI Officer

This is a client-facing fractional role. Workshops, executive alignment, use-case selection, and practical handoff to builders.

Read role →
07 / 09
Operations· Remote

Maintenance Program Manager

Own the ongoing maintenance layer across clients after systems ship.

Read role →
08 / 09
Contract· Remote

Interaction Designer-Operator

An evolution of the IXD role: build the working interaction first, then refine it with a designer's eye until it fits the client's job.

Read role →
09 / 09
Contract· Remote

Quality Assurance Specialist

Contract QA work for AI systems, internal tools, automations, and client workflows that need sharper testing before they ship.

Read role →

What we hire for

Three things, every time.

01

Real work first

One paid project tells us more than a long interview loop. The work is the signal.

02

AI-native judgment

Claude Code, Codex, Hermes, custom agents, whatever comes next. Speed matters. Judgment matters more.

03

Context carriers

Hold the client, the workflow, the technical constraint, and the adoption problem at once.

Application process

Fewer interviews. More evidence.

We usually start with paid contractor work on individual projects before moving anyone into a full-time role. It gives both sides a cleaner read.

Step 01

Apply

Send the basics and show us how you work. A portfolio, a repo, a memo, or a short video beats a polished resume.

Step 02

Small project

When there is a fit, we start with paid project work. Real work is the cleanest interview.

Step 03

Expand

Strong fits get more responsibility, longer engagements, and full-time conversations when the timing makes sense.

Don't see a fit?

Send us your work anyway.

If you build with AI in interesting ways and the listed roles do not quite match, tell us what you would want to do. The bench is bigger than the board.