Description:
You will be our founding ML engineer — the engineering hire of the lab. You'll work directly with the founder to harden, extend, and scale the agentic systems already in production, and to build the next generation of them for customers beyond our anchor. This is a role for someone who wants ownership of real systems with real consequences, not a research sandbox.
What you'll do
- Own the core agentic architecture: multi-step agent workflows for quoting, bidding, pricing, and compliance
- Iterate our autonomous bidding/pricing logic toward measurable operational impact — better decisions, tighter reasoning traces, stronger evaluation
- Design and run evaluation pipelines for agent behavior: offline evals, regression suites, and production monitoring for long-running agent workflows
- Build and maintain retrieval and knowledge infrastructure (knowledge graphs, vector retrieval) over messy, real-world logistics data: rate sheets, customs schedules, carrier contracts
- Ship to production continuously — you'll deploy, observe, and fix systems that operations teams depend on daily
- Help shape engineering culture, tooling, and hiring as the team grows
Our stack
Python / FastAPI · LangGraph · Claude (Anthropic API) · MCP servers · Neo4j · pgvector · Supabase · DigitalOcean · local inference (Ollama) for sensitive workloads
What we're looking for
- 4+ years of software/ML engineering experience, with at least 1–2 years building LLM-powered systems that shipped to production
- Hands-on experience with agent frameworks (LangGraph, or equivalent orchestration you can defend), tool use / MCP, and structured retrieval (vector and/or graph)
- Strong Python and production engineering fundamentals: APIs, observability, testing, deployment — you've been on call for something that mattered
- Pragmatic evaluation mindset: you know how to tell whether an agent is actually good, not just impressive in a demo
- Comfort with ambiguity and ownership — you'll often be the only engineer in the room
- Bonus: experience in logistics, supply chain, fintech pricing, marketplaces, or other domains where automated decisions carry direct financial consequences
- Bonus: experience with knowledge graphs (Neo4j), self-hosted/local inference, or compliance-heavy domains