Elan is a platform for building, deploying and scaling AI agents. A developer writes an agent, and the platform provides everything else needed to run it as a product. Much of that value comes from the apps an agent can plug into: observability, billing, evaluation, authentication, and third-party tools.
As Product Engineer you build those integrations and own each one independently, from first design to production and its users.
What you will own
Integrations. Connectors between the platform and auxiliary apps, both our own and third-party services, built against their APIs, webhooks and event streams.
Each integration as a product. Its scope, its developer-facing configuration, its releases, its documentation, and its health in production.
Platform fit. Working with the Platform Engineer to wire each integration into the platform's runtime, identity, usage metering and policy layers, so it works the same way as everything else.
Quality. Tests, versioning, backwards compatibility, and monitoring for every integration you ship.
Developer feedback. Talking to the developers who use your integrations, and deciding what to build next from what they need.
How you will work
You report to the head of product and technology.
You work closely with the Platform Engineer, who owns the runtime and the shared services your integrations plug into.
You are based in Noida with a hybrid working arrangement. Compensation is 30 to 70 LPA.
We hire for four things: ownership, curiosity, developer obsession and delivering results.
Minimum requirements
4 to 8 years of software engineering, with at least 2 building integrations against third-party APIs in production.
Strong in Python or TypeScript on Node.js, and comfortable in the other.
REST and GraphQL APIs, webhooks, OAuth 2.0 and API keys, rate limits, retries and idempotency.
Has owned a feature or product end to end, including its users and its production issues.
Event-driven systems on Pub/Sub, SNS/SQS or Kafka.
Writes tests as part of the change, and versions what others depend on without breaking them.
Works independently, and writes clear documentation for other developers.
Good to have
Built integrations for observability, billing, payments, authentication or evaluation tools.
Experience with MCP (Model Context Protocol) servers or LLM tool calling.
Kubernetes and containerised deployment.
Experience as an early engineer at a startup.
