About zaimler AI agents can't reason over data they don't understand. Enterprise data today is fragmented across dozens of systems with no shared context, meaning, or structure, and that's why most enterprise AI is failing. The shift from copilots to autonomous agents is creating an entirely new infrastructure layer, and we're building it. zaimler is the context infrastructure for the agentic era: a platform that automatically discovers domain knowledge, maps relationships, and gives AI agents the semantic understanding to operate with precision at scale. Imagine knowledge graphs that support real-time inference, built for systems that need to reason, not just retrieve. zaimler was founded by Biswajit Das (ex-VP Engineering, Truera), a Data Infra veteran and former Chief Architect at Visa, and Sofus Macskassy (ex-Director of Engineering, LinkedIn), who built one of the largest knowledge graphs in production in the industry at LinkedIn. We're growing and deploying with major enterprises across insurance, travel, and technology. If you want to build infrastructure that the next decade of enterprise AI runs on, we'd love to talk. Why this role exists
Our platform is used by engineers, and engineers judge infrastructure by how fast it stops confusing them.
We have a hard system underneath: graphs, real-time inference, agent behavior in production. Today, understanding it takes a conversation with us. That's a ceiling on how fast we grow. This role exists to remove it, by owning the surface where customers actually meet the product and making it obvious. The role
You'll own product surface end to end: the interfaces, the APIs behind them, and the data models underneath.
The hard part isn't the CRUD. It's making genuinely complex system behavior legible and fast for the people using it. That takes taste as much as it takes engineering.
The split is roughly [60% frontend and API layer, 40% backend services]. You will not be handed a design file, and you will not be handed a spec. If you want to go deep on distributed systems and never touch a UI, this is the wrong role. If you can't hold your own on the backend either, it's also the wrong role.
We're small and senior. You'll pick the architecture, ship it, watch it in production, and fix what's wrong.