Software Engineer
Most AI initiatives inside companies fail the same way: compelling demos, no production systems.
Why This Role Exists
Most AI initiatives inside companies fail the same way: compelling demos, no production systems. The gap is not the AI. It is the last mile — getting powerful models into the actual workflows that run the business.
That is what this role is built to solve.
Luxer One is embedding Forward Deployed Agentic AI Engineers directly inside business units across the organization. These engineers do not sit in a central platform team waiting for tickets. They embed with GMs, sales leaders, operations teams, and customer success functions. They learn the work, find the highest-leverage opportunities, and ship agentic AI systems that change how the business operates — measured by outcomes, not activity.
This is the fastest-growing engineering archetype in the industry. Palantir built a category-defining company around it. OpenAI, Anthropic, Google, AWS, and Microsoft are each building internal versions at scale. We are doing it from the inside, deploying this model across our own divisions. If you have ever looked at a broken sales workflow, a high-volume support queue, or a manual operations process and thought "I could build an AI system that eliminates this" — and then actually built it — read on.
Who You Are
You are an engineer who is equally at home debugging an integration and presenting ROI to a GM. You move fast, operate independently, and measure your work by what changed in the business — not by lines of code shipped.
Specifically, you are:
An engineer first — you design and ship complete production systems from scratch, across the full stack: data integration, agent orchestration, prompt and context engineering, evaluation, deployment, and monitoring
Business-fluent — you can walk into a sales standup, a field operations review, or a GM strategy session and come out with a clear list of the highest-ROI AI opportunities in the room, without anyone handing you a brief
Self-directed — you do not need a spec, a PM, or a fully defined sprint to get started; you get handed a business outcome and you figure out how to build the system that delivers it
Adaptive — every business unit runs a different stack; you learn the tools, find the integration points, and build on what exists — whether that is Zoho CRM, Microsoft Outlook, Slack, Meta Ads Manager, or something you have never touched before
Outcome-obsessed — you define what success looks like before you build, and you measure it in production; ROI on your agentic systems is your scorecard, not technical throughput
An effective communicator across roles — you can explain what you are building to a GM, a frontline sales rep, and a backend engineer using three completely different vocabularies, all in the same week
Posted October 2, 2026