You have opted out of job matches in .
To undo this, go to the 'Skills and Interests' section of your preferences.
Shared by 
2 months ago
warning
Heads-up
Requirements and responsibilities
About this roleDatum’s mission is to help 1k clouds thrive in the AI era by unlocking internet superpowers for every builder. We’re working in the open to bring the foundational capabilities that all the big guys use (private networking, peering, direct interconnection, etc) into the hands of builders and modern “alt clouds” — no network team required.One of Datum’s core values is to be connectors: of applications, services, networks, and people. As such, this role will work directly with users, customers, partners, and the broader community.Another key value is to be open by default, from how we license our code (AGPLv3) to how we communicate, engage with, and document our work. We believe this engenders trust from our customers and community because open is the best way to build: it’s more secure, more operable, and even more enjoyable.What you’ll doLead agentic experience (AX)Own the design philosophy for how agents discover, understand, and get value from Datum, all without reading a marketing site, without a human in the loop, and without surprisesDrive our investment in CLIs, declarative configs, and APIs as the primary surface area, more than everDefine and ship our approach to agent-parseable manifests (agent skills and beyond), MCP, and other canonical information agents need to act with confidencePush the platform toward deterministic, composable, well-typed primitives from first touch to final invoiceMake “time to first successful tool call” a metric that the whole team is proud ofLead developer experience (DX)Own the developer experience end-to-end, from the browser to the command linePartner to keep documentation accurate, opinionated, and treated as a first-class deliverable (for humans and for the models that will read it)Maximize dopamine, minimize frictionStand up forward-deployed engineeringBuild out a small forward-deployed engineering function that works directly with AI-native providers, alt clouds, and partners on real production workloadsRun those workloads yourself; find the friction firsthand; feed it back into the productAdvocate for the governance, security, and control surfaces that make an agent-ready network cloud something enterprises and regulated industries can actually adoptDemonstrate engineering leadershipDrive your roadmap by modeling Datum’s values every dayDistill customer and partner needs into clear problem statements that align prioritiesMake timely decisions; create structure where none exists; improve processes as you goWork in the open: we make money through our network and infra, not our softwareWho you areBackgroundOperator at heart. You don’t tolerate manual deployments or slow builds. You can implement the right glue no matter the language, and you have strong opinions about public and alt cloud experience from regular use.Builder for agents. You’ve built something an LLM or agent had to operate against, and you understand what makes it work or fall flat. You’ve worked with MCP or similar protocols and have opinions about where the ecosystem is breaking down.API and CLI taste. You’ve used a lot of CLIs, SDKs, or declarative APIs and you know what people (and now agents) actually love.Kubernetes is your jam. You know, love and hate Kubernetes as much as we do.Open source track record. Use, build, and contribute. This is the way.Non-negotiablesLogistics: Overlap with NYC business hours and ability to travel to NYC, SF, etcHigh EQ: You read rooms, understand people, and navigate complexity with graceHunger: You’re driven by impact and energized by building something meaningfulHumility: You check your ego, give credit freely, and focus on collective successCore attributesHold the agent’s perspective and the operator’s perspective in your head at the same time. You have the taste to know what to build and shipThrive in an async environmentSimplify technical complexity through writing, demos, and the occasional talkToggle between 30,000-foot vision and ground-level executionGenuinely passionate about digital infrastructure and the future of the industryWhat success looks likeFor DatumAn agent can go from zero to a working Datum integration without a human in the loopRock-solid APIs, squeaky-clean docs, and a developer experience that holds up at AI-native scaleA forward-deployed engineering function that turns customer signal into product velocityReal traction with AI-native providers, alt clouds, and the ecosystems forming around themFor youA platform to define what agentic infra should feel like, before the patterns are setThe chance to keep the internet open, neutral, and operable for next gen cloudsStrategic and operational leadership at a company that takes both seriouslyNote: this isn’t a DevRel role. It isn’t a PM role. It isn’t a solutions engineering gig. It’s an engineering leadership role for someone with strong opinions about what good infrastructure tooling looks like, who is energized by ambiguity, and who believes the most important design challenge right now is the interface between autonomous systems and the humans responsible for them.We believe in openness, clarity, and collaboration. To learn more about how Datum aims to operate, please review our public handbook.
Optionally, you can add more information later (benefits, pre-screening questions, etc.)