Senior Product Engineer — Platform & Enterprise

Engineering is moving quickly. What the team needs next is not another layer of management; it is a senior product-minded engineer who can keep building while improving the decisions, reviews, and cross-functional conversations around the work.

Today too much product ownership still sits with the founder. Customer context, interface decisions, technical tradeoffs, and delivery sequencing often meet in the same conversation. You will help carry that context, make it legible to the team, and keep milestones moving without turning the company into a ticket factory.

This role can grow with the team, but it is intentionally senior rather than a premature head-of title. The first mandate is to contribute, lead through the work, and create leverage for the engineers around you.

• Hands-on product delivery. Roughly half your time will go into building and improving the core workspace across the interface, application logic, and data paths behind it.
• Product ownership. Turn ambiguous customer and company needs into a coherent sequence of product decisions, with clear tradeoffs and a high quality bar.
• Technical leadership and review. Review consequential work, improve plans before code is written, and help less-experienced engineers develop stronger product judgement.
• Enterprise readiness. Work directly with customers and support resources on onboarding, access, reliability, and deployment constraints, then turn recurring needs into durable product capabilities.
• Frontline problem solving. Join important conversations when technical context matters, diagnose what is actually blocking progress, and carry the answer back through delivery.
• Milestone ownership. Keep the product plan honest, surface risk early, and close the space between a verbal commitment and a shipped result.

The Infrastructure & Release Engineer owns the systems that make delivery safe: verification, deployments, migration mechanics, access foundations, and production reliability.

You own the customer-facing product decisions and the technical work that follows from them. The two roles meet where enterprise needs cross product, security, and operations, but they have distinct centers of gravity.

• Senior product engineering experience. You have owned meaningful product decisions before, not only implemented specifications written by someone else.
• Strong full-stack judgement. You can move from a dense interface to the data path behind it and know where a problem actually belongs.
• Evidence of hands-on leadership. You raise the quality of plans and reviews while continuing to ship substantial work yourself.
• Clear cross-domain communication. You can work with a user, an operator, and an engineer without losing the important context between them.
• Comfort with enterprise delivery. You understand that onboarding, access, reliability, support, and product design become one system for larger customers.
• You are based in the United States or Canada. The role is remote, with meaningful overlap for domestic customer and partner work.

• You have made a dense interface — an inbox, table, editor, timeline, or operational workspace — feel fast and considered at scale.
• You have led an enterprise rollout where the product, support process, and technical constraints all had to move together.
• You have mentored an early-career engineer into stronger ownership without taking the work away from them.
• You have worked through a live migration or reliability problem while protecting the customer experience.
• You can show a product you materially shaped and explain both the technical decisions and the choices you deliberately did not make.

We are a very small, distributed, engineering-led team. We ship continuously, use AI tooling heavily, and expect people to work from problems rather than wait for complete specifications.

The rough split for this role is 50% direct contribution and 50% product ownership, review, technical leadership, and frontline problem solving. That split will move week to week, but neither half is optional.

You will report to the founder and work closely with operations, engineering, and support resources. You will have significant context and direct access; the expectation is that you turn that access into better decisions and a team that needs less founder intervention over time.

The package will combine competitive cash compensation and meaningful equity. We will align on expectations early rather than carry an obvious mismatch through a long process.

The process is short and centered on real work:

1. A conversation with the founder about your background, product judgement, and the mandate.
2. A walkthrough of a product you helped shape, including the technical and customer tradeoffs.
3. A paid, scoped working session against a realistic cross-functional problem.
4. A final conversation on how we work, compensation, and your questions.

We do not do unpaid take-homes or surprise algorithm rounds.