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.