Agentic Engineer

Position: Agentic Engineer I
Agentic Engineer — Build, Experiment & Ship Position:
Agentic Engineer I— Multi-Agent Systems:
Build, Connect & Ship At Nexteer, our strength lies in the diversity of our team—each member contributing unique backgrounds, experiences, and aspirations. We believe this diversity fuels our innovation, broadens our perspectives, and propels our collective growth. For over a century, we’ve been innovators in the automotive industry.  Our vision is clear - we are a global leading motion control technology company accelerating mobility to be safe, green and exciting.

Our unwavering commitment to Quality, Collaboration, Integrity, and Accountability guides us as we solve motion control challenges for our global customers. If you’re ready to join a dynamic team that drives change and makes a difference, Nexteer welcomes you!

About the Role:

We're looking for an Agentic Engineer whose core craft is building agents — lots of them, fast. Not one chatbot over a document store: production agent systems that call enterprise tools, hand work to each other, and run where real users depend on them. You'll move quickly, iterate often, and own your work end to end.  Your job is to build on that platform and be fluent in its language: your agents register a manifest, call models and tools through gateways, and emit standard telemetry.

The platform makes the plumbing disappear so you can ship agents at a pace that would be impossible if every project solved auth, deployment, and monitoring from scratch. The fast lane agentic project team mission is to enable a digital and AI-enabled engineering workflow and organization. The fast lane team assignment is targeted to be 18 months as an Agentic-first project team, and then full-time deployment into the engineering organization.  

This is an individual contributor role and the selected candidate will have the opportunity to work a hybrid schedule.  What We're Looking For You're naturally curious and self-directed — you build things because you want to understand how they work. You've containerized, self-hosted, and deployed real projects, and you've watched something behave differently in production than it did locally — and that made you a better engineer.

The clearest signal: you have agents that talk to each other and to tools, running somewhere that isn't your own machine — and ideally an MCP server that someone other than you depends on. You stay current with agent tooling by using it, not just reading about it.

Key Responsibilities As an Agentic Engineer I, you will be responsible to:
Assist with the design, build, and ship production AI agents — many of them — across frameworks (Claude Agent SDK, Microsoft Agent Framework, Lang Graph, or custom harnesses) Assist with the build MCP servers that connect agents to enterprise systems (PLM, MES, ALM, data platform) — business logic only; the platform handles auth, deployment, and registration Assist with the design multi-agent workflows: orchestration, handoffs, and agent-to-agent communication patterns — deciding when one agent should be five, and when five should be one Assist with the build of both the agent and the harness — the agent (model, instructions, tools, memory) and the harness it runs in (the loop: tool dispatch, context management, retries, state).

Know when an off-the-shelf harness like the Claude Agent SDK loop is enough, and when the job calls for a custom one Assist with and run rapid experiments: hypothesis  prototype deploy evaluate iterate — with evals that tell you whether an agent got better Embrace a fail-fast approach — short cycles, quick learning, and moving on with better information Evaluate agent frameworks, models, and tools through hands-on use, not benchmarks alone Document…