Remote, United States (or overlap with US hours). Full-time.

About the role

This is a forward deployed seat. You embed with a design-partner team, stand Certus up on a real safety-evidence workflow, and turn one subsystem change cycle into a working packet in about a week. You write what you learn back to the founding team, and you help that account go from the first wedge to a paid seat. The job is customer-facing and hands-on: TypeScript and Python, repo and document ingestion, and debugging the workflow when a real packet does not line up. You own the account with the founders.

What you'll do

• Sit with a design-partner safety or hardware team and learn how they run a change cycle today.
• Stand Certus up beside Jama and IBM DOORS on one subsystem.
• Get that change cycle to a working evidence packet in about a week.
• Debug ingestion, drafts, and checks in the product when the packet stalls.
• Send concrete product feedback to the founding team so the next account is easier.
• Help the account move from the wedge to a paid seat once the workflow holds.

What we're looking for

• You have shipped production software.
• You are comfortable with ambiguous customer problems and can pick a path without a perfect spec.
• You can write and debug code in a modern web stack. TypeScript or Python is enough to start.
• You can explain technical tradeoffs to a safety or hardware engineer who is not a software specialist.
• You are willing to travel to a design partner sometimes.
• You are US-based, or you can overlap US hours. Founders are in Portland, New York, and Seattle.