Temporal Technologies logo

Temporal Technologies

More roles at Temporal Technologies

Staff Product Manager, Self-Hosted and Connected Temporal

Region Restricted

Remote work allowed only within certain countries or regions.

Employer listed it 6 days ago · Added 2 months ago

Been open since 2 months ago. Long-running listings are sometimes left up after the role is filled.

Salary

$160k to $263k per year

Location

Timezone

US East

Contract

Full-time

Experience

Lead

Category

Product

Published by the employer

What the advert says

Quoted word for word from the employer's advert. Where it says nothing, we say so.

Working hours
Not mentioned in the advert
Where you can work from
Align Engineering, Resident Architects, Dev Success, Security, and go-to-market teams, including when their incentives conflict.
Contract
Not mentioned in the advert
Experience asked for
Not mentioned in the advert
Pay
Not mentioned in the advert

Remote flexibility

Region Restricted

Remote work is allowed, but only for candidates based in United States, Canada.

What the employer says

  • Source listing states candidate location: "United States (Remote), Vancouver, British Columbia, Toronto, Ontario, Ottawa, Ontario, Remote"

What Nomaders makes of it

  • Applications outside the listed area are usually rejected
  • Timezone overlap with the listed area is often expected

The quotes above are the employer's own words; the reading is ours. Always check the original listing and employment terms before working from another country.

Before you apply

Questions worth asking: Nomaders interpretation

  • The advert does not say whether this is employment or a contractor arrangement. Ask, as it affects tax and benefits.

Produced automatically from this advert's text; not reviewed by a person. The employer's own page is the final word.

About the role

Role Summary

Temporal is used by a lot of companies in a wide variety of contexts. Many use Temporal Cloud. Many others users don’t yet know about Temporal Cloud, believe self-hosting is cheaper, and/or just don’t yet see a need to move. Still others (often happily using Temporal Cloud at large scale) also operate environments where a managed service isn't an option today and may never be, like:

AI and application companies embedding Temporal inside software their own customers run in isolated, air-gapped environments, or offering a remote management BYOA posture

Large enterprises keeping operational control of critical systems in-house by policy

Companies operating in sovereign clouds and similar contexts where legal or organizational requirements make outside management difficult or impossible

This role owns understanding the world of Temporal usage outside Cloud, what the different contexts demand, and where Temporal should (and shouldn't) engage. That includes what we build, what we support, what we charge for, and what we leave alone. You'll shape which offerings we pursue and how they make money or contribute to the larger business. Then you'll take the ones we commit to through launch and adoption.

Open source Temporal is central to this. We’re investing heavily in OSS, from performance improvements to easier management to clearer guidance on compatibility and cost. When companies write their apps on Temporal, they’re making a huge bet on us, and that trust is sacred. A large part of this role is improving and shepherding how we keep making OSS better.

What You’ll Do

Map usage outside Temporal Cloud. Build the company's clearest picture of where Temporal runs outside Cloud and why. Separate structural constraints (air gaps, regulation, owning operational risk) from cost, inertia, and/or other factors. Turn that into segments and use cases leadership can make decisions with.

Decide what we pursue. Recommend which needs deserve new offerings, which Temporal Cloud should cover, and which we deliberately leave alone. Write the case, defend it, and revisit it when the evidence changes.

Define the line between open source and paid. Set clear guidelines for which improvements and support go into open source Temporal, and where paid offerings take over. Keep the open source experience strong, and make the line easy for users and internal teams to understand.

Define the business model. Work with leadership, Sales, and Finance on packaging, pricing, and how we sell offerings that run outside our infrastructure. Know what customers will pay for and what it costs us to support it.

Help Cloud win where it should. Work with other PMs so workloads that can run on Cloud move there more easily, with a clear value and TCO case.

Lead without authority. Align Engineering, Resident Architects, Dev Success, Security, and go-to-market teams, including when their incentives conflict.

Own outcomes. Define success in terms of adoption, revenue, and retention. Use the results to steer further investment.

What You’ll Bring

A track record of setting product strategy, not only executing it. You've spotted a new offering or market, made the case for it, and seen it through to revenue.

Experience with infrastructure or platform products that customers operate themselves: open source, on-prem, or hybrid.

Commercial judgment. You can connect a customer problem to willingness to pay, pricing, and the cost of delivering and supporting the product.

Technical depth in distributed systems and operations: Kubernetes, databases, replication, upgrades, and failure recovery. You can go deep with engineers and turn the tradeoffs into product decisions.

Comfort saying "not this" and backing it with evidence. You change course when the facts change.

Clear writing. You can turn messy evidence from customers and the field into a recommendation leaders can act on.

Nice to Haves

Experience making money from open source or open-core products

Requirements

  • ·A track record of setting product strategy, not only executing it. You've spotted a new offering or market, made the case for it, and seen it through to revenue.
  • ·Experience with infrastructure or platform products that customers operate themselves: open source, on-prem, or hybrid.
  • ·Commercial judgment. You can connect a customer problem to willingness to pay, pricing, and the cost of delivering and supporting the product.
  • ·Technical depth in distributed systems and operations: Kubernetes, databases, replication, upgrades, and failure recovery. You can go deep with engineers and turn the tradeoffs into product decisions.
  • ·Comfort saying "not this" and backing it with evidence. You change course when the facts change.

Benefits

No benefits package published with this listing. Ask about it at first interview.

How to apply

  1. 1Check the flexibility label above, region restricted, matches where you plan to live and work.
  2. 2Tailor your CV to the role at Temporal Technologies, mentioning your remote working experience and working hours (US East).
  3. 3Apply directly on the employer's careers page using the button below. Nomaders never handles your application.

Found 2mo ago. Last checked 17 Nov. Always confirm the details on the original posting, salary and location can change after publication.

Listing sourced from Company boards.

$160k to $263k per year · You'll be taken to the employer's careers page.