Forward Deployed Engineer
Forward Deployed Engineer at Bold AI: you embed with clients to scope, build, and run production AI integrations connecting their CRMs, ticketing, Slack, and internal tools using Python/TypeScript, REST/webhooks, and LLM APIs. Roughly 50% integrations, 25% coding, 25% client-facing, and you own what ships in production.
- Compensation
- Not disclosed
- Location
- Not listed
- Work setup
- Hybrid
- Seniority
- Not specified
- Employment
- Not specified
- Experience
- Not specified
- Category
- Solutions engineering
- Posted
Skills
Must have
- Production experience: shipped systems real users depended on, including handling outages/failures
- Integration fluency: REST APIs, webhooks, OAuth flows, rate limiting, retries, idempotency, queues
- Solid coding in Python or TypeScript
- Working infrastructure knowledge: Linux, containers, environment management, secrets handling, basic CI/CD
- Client-ready communication: clear written English, confident on calls
- Composure under pressure with shifting timelines and requirements
Nice to have
- AI/LLM integration experience: model APIs, tool/function calling, MCP, RAG fundamentals
- Prior agency, consulting, or forward-deployed experience
- Experience inside enterprise client environments: SSO, VPNs, security reviews, procurement-grade documentation
Full description
The Role
You are the engineer Bold AI sends into a client's business to make things work. Not a prototype that dies in a demo, not a proof of concept. Production systems that run inside the client's real environment, connected to their real tools, used by their real staff. You spend most of your time wiring systems together, a quarter of it writing code, and a quarter of it in front of the client. If any of those three make you uncomfortable, this is not your role.
What You Will Actually Do
- Take a loosely defined client brief and turn it into a scoped, buildable plan within the first week of an engagement.
- Build and ship integrations into live client environments: their data, their access controls, their uptime expectations.
- Deploy to production and stand behind it. Monitoring, error handling, rollback plans, and runbooks are part of the deliverable, not extras.
- Run your own engagement: timeline, risks, client communication.
- Demo working software to clients weekly. Progress is shown, not reported.
- Hand off cleanly at the end: documentation, credentials transferred, a named client-side owner who can run what you built.
- Turn what you learn into reusable templates and playbooks so the next engagement starts faster.
What to Expect
This job has pressure, and you should know that walking in.
- Deadlines are client deadlines. They are tied to launches, events, and budgets. They move rarely and never because the work was harder than expected.
- You will work in unfamiliar territory constantly. A stack you have never touched, an API with no documentation, a legacy system nobody at the client fully understands. Figuring it out is the job.
- Production means production. When something you shipped breaks at a client, you are the first call. You fix it, then you fix the reason it broke.
- Scope will shift mid-engagement. Clients discover what they actually need once they see working software. You adapt without losing the timeline or your composure.
- You represent Bold. On-site and on calls, you are the company. Prepared, direct, and calm, especially when things go wrong.
In exchange: no layers of management, direct access to leadership, real ownership of real outcomes, and work that lands with clients in weeks. You will compress years of experience into each engagement.
Skills NeededRequired:
- Production experience. You have shipped systems that real users depended on, and you have been on the hook when they broke. You can talk specifically about an outage or failure you handled and what you changed after.