Position details
Agentic Systems Engineer
Melbourne, FL or Remote
Full-time position
Open to software engineers, systems engineers, IV&V engineers, and architects. We care what you build, not what your last title was.
Apply for this role
Send your CV and anything you've built — a repo, a demo, a write-up — to careers@skymantics.com.
Apply now01
About the role
Skymantics is building a Semantic Intelligence platform — a layer that lets AI systems reason over live, structured, and unstructured data in mission-critical domains. We're not bolting a chatbot onto existing software. We're rearchitecting how systems understand context, make decisions, and work alongside the people operating them.
You'll work across engagements from aerospace to financial services — different domains, same architecture: agentic systems that reason, act, and improve through tight iteration loops, built to the standard those industries demand.
This isn't vibe coding. It's spec-driven, enterprise-grade engineering.
02
What you'll build
—
Multi-provider AI orchestration that stays vendor-agnostic
—
MCP servers, clients, and RAG pipelines connecting AI systems to real data, tools, and workflows
—
Agentic workflows — multi-step reasoning, tool use, evaluation loops, human-in-the-loop checkpoints
—
Specifications that drive implementation and evaluation, not documentation written after the fact
—
AgentOps: observability, evaluation harnesses, and guardrails for systems that act on their own
You'll do this directly with domain experts in regulated environments, validating that the system behaves correctly in their world, not just in a demo.
03
Who we're looking for
The bar to clear
Ideal candidates exhibit:
—
Production credibility. You've shipped software other people depend on, and you know what it takes to keep it running.
—
Hands-on AI. You've built something with LLM APIs — even a weekend project — and you know where they shine and where they fall apart.
—
Systems thinking. You reason about how components interact, not just how one function works. IV&V and systems engineers already do this every day.
—
Comfort with incomplete requirements. You'd rather ask the client a hard question than wait for a perfect spec.
—
Ship, learn, ship again. You treat iteration as the method, not a fallback.
What excites us
Exceptional candidates exhibit:
—
Proof, not claims. A repo, a demo, a write-up — something you built with agents or MCP because you wanted to see if it would work.
—
Agents in production. Multi-step orchestration, tool-calling, and evaluation loops, plus the failure modes those taught you.
—
MCP fluency. You've implemented or extended a server or client, not just read the spec.
—
Rigor where it counts. Spec-driven development, evaluation harnesses, or AgentOps you've run in a regulated or safety-critical environment.
—
Early by habit. You were building with these tools before there was a job title for it.
Let's talk about your future.
The systems we build carry real weight. That's what makes the work worth doing. If you'd rather create than maintain, this is that role. Title on your last badge doesn't matter. What you can create does.