Elm AI
See if you qualify before applying
Get your match score and detailed fit analysis in 10 seconds.
At Elm AI, we’re rebuilding supplier operations for an agent-first world.
We believe the next generation of enterprise software will not be passive systems of record. It will be made up of agents that stay live inside important workflows: understanding context, coordinating action, and keeping critical work moving even when teams are offline.
Our agents operate across responsible sourcing and supplier operations, helping companies manage audit review, corrective actions, supplier follow-through, remediation, and the broader execution layer around supplier relationships. Rather than waiting for someone to log in and push a process forward, Elm’s agents keep workflows active, current, and in motion.
This is not a future concept. Elm’s systems are already running in production with major consumer brands, supporting supplier programs that span thousands of factories and some of the most operationally complex environments in the market.
Our customers include multi-billion-dollar global brands. Our ambition is much larger: to build the agent-first operating layer for how global supplier work gets done.
We’re hiring a Senior Product Engineer to help build Elm AI's core product and agent workflows.
This is a high-ownership role for someone who is both deeply technical and strongly product-minded — someone who can move from architecture to implementation to UX decisions, and who cares about building software that is not only powerful, but clear, fast, and durable.
You should be highly fluent in modern software engineering, but also opinionated about what great engineering looks like in an AI-native world: how to design systems that work well with agents, how to build fast feedback loops, how to use AI tools meaningfully in development, and how to keep quality high while moving quickly.
We’re looking for someone who can help us shape both the product and the way we build it.
The people who thrive here are usually already building long before anyone asks them to.
They often have side projects, experiments, prototypes, writing, open-source work, or some corner of the internet where they develop a point of view. They tend to try new models and tools early, build things for fun, and care deeply about both product quality and technical depth.
They usually don’t stop at what was explicitly asked. They notice what could be more useful, more reusable, more elegant, or more leveraged — and they move toward that.
They care about speed, but not at the expense of craft. They care about quality, but don’t confuse complexity with excellence. They’re energized by ownership, ambiguity, and the chance to help invent a new category with other sharp, ambitious people.
This role is remote, but it requires overlap with U.S. Eastern Time.
We want to be upfront about this so expectations are clear.
Originally posted on Himalayas