Strategy and Engagement Lead

Runs our client projects from the first interview to the finished build. You set the strategy, plan the work and make the first working versions with AI.

Location

Remote, some client travelUS-friendly hours

Structure

Contract to hireFull-time when the fit is clear

Start

Week of October 19Full-time work for the first month

Apply now →

Pay, classification, weekly hours, first-project duration, and travel expectations vary by role and client. We share those terms before asking a candidate to accept paid project work. A full-time path is discussed only after both sides have worked together.

TLDR

You run our client projects end to end: the strategy, the plan, the people and the first working versions.
Most projects start with discovery. You learn the business, decide what is worth building, and stand behind the call.
You build prototypes and plans with Claude Code and direct the engineers who build the rest. You don't need to be an engineer.
You have years in consulting, an agency or a similar seat, and you run a project without anyone telling you what to do next.
Contract to hire, with full-time work from the week of October 19. Remote, with some trips to client sites.

Runpoint is growing, and we need more people who can lead a client project from the first conversation to the finished build.

Most of our projects start with a few weeks of discovery. You spend the first two listening: to the owner, the operations lead and the people doing the work, and to whatever systems and code the company already has. Then you decide what to build, what to buy and what to leave alone, and you stand behind it.

You make your work with Claude Code and tools like it. You build prototypes, plans and working drafts, and you direct the engineers who build the real thing. You won't write production code, and nobody here wants a sixty-page report.

The role is contract to hire. We start on contract and plan to bring you on full-time.

What you will do

Run the engagement yourself: the schedule, the people and the next step. Nobody hands you a task list.
Run discovery: interviews, process reviews, and a careful read of the client's existing systems and code.
Weigh risks by what matters, including what happens two steps later, instead of listing every risk you can think of.
Recommend what to build, buy or replace, including large calls like a new ERP, and defend the choice.
Build prototypes and plans with Claude Code, and brief the engineers who build the production version.
Stay close to the build after handoff, so it still matches what the client needs in week two and later.
Help win the next project. Clients who trust your judgment ask for more work.

What we need

Years of consulting, agency or operating experience with real clients and real budgets.
You use AI tools every day, have opinions about the models, and have built apps of your own.
Enough technical depth to read an architecture diagram, question a vendor and think through build versus buy.
You can sit with an owner, an operations lead and an engineer and earn the trust of all three.
You can start on contract the week of October 19.

Strong signals

If any of these describe you, the conversation will move quickly.

You have run workshops or trainings and people asked you back.
You have sold work because a client trusted your judgment.
You build things on weekends with Claude Code or Codex because you can't leave a problem alone.
You can tell when AI output is right and when it only sounds right.