Forward Deployed Engineer
Posted 18 days ago
The role in short
Embed with clients to design, build, and deploy production AI systems and integrations using TypeScript and Python.
PRESHai is hiring Forward Deployed Engineers to build, deploy, and stand up AI systems directly inside client environments across the IT channel.
This is a hands-on delivery role. You will sit at the edge of PRESHai, embedded with MSPs, solution providers, distributors, and manufacturers, turning their business problems into working AI systems that ship in weeks, not quarters. You will be the engineer the client sees, the engineer who writes the code, and the engineer who owns the outcome.
The right person for this role is not a back-office software engineer and not a solutions consultant. This is an operator-engineer who can frame a problem with a senior client stakeholder in the morning, design the solution by lunch, ship a working prototype that afternoon, and harden it into a production system the next day. You move with judgment, not with tickets.
Assignments vary: some FDEs will embed deeply with large enterprise client(s); others will run a portfolio of mid-market engagements. We will determine placement based on fit during the interview process.
You will report directly to the CEO. PRESHai runs a deliberately flat structure: no middle management, high autonomy, and shared context through the systems we build internally on PRESHos. You will pull from the platform, patterns, and tooling built by our Core Engineering team, and you will push reusable patterns back so the next engagement is faster.
Responsibilities
Client Delivery
- Embed with assigned clients and own the technical execution of PRESHos and AI implementation engagements end to end.
- Translate client workflows, systems of record, and operational pain points into working AI systems. Avoid building things that should not be built.
- Write production code in TypeScript and Python across agents, integrations, workflow orchestration, RAG, and voice interfaces.
- Build and maintain integrations with client CRMs, PSAs, ITSMs, ERPs, communication platforms, databases, and custom internal systems.
- Configure environments, manage credentials safely, and deploy into client or PRESHai-managed infrastructure.
- Drive adoption inside the client. A system that nobody uses is a failed engagement.
Client-Facing Work
- Lead working sessions with client engineering, IT, operations, and business stakeholders.
- Surface blockers, scope creep, and integration risks early and directly.
- Communicate technical decisions and tradeoffs clearly to non-technical stakeholders.
- Train client teams to operate, extend, and trust the systems you ship.
Technical Execution
- Build with the architecture, patterns, and tooling defined by Core Engineering; push fixes, missing primitives, and reusable patterns back.
- Maintain observability, error handling, and human-in-the-loop escalation in everything you ship.
Required Qualifications
- 3+ years shipping production software, with at least 1 year shipping LLM-powered, automation, or integration systems in production.
- Strong production coding ability in TypeScript and/or Python.
- Practical experience with APIs, databases, OAuth flows, third-party integrations, webhooks, and system-to-system data movement.
- Experience with LLM application patterns: tool/function calling, RAG, prompt architecture, structured outputs, workflow automation.
- Fluency in at least one major cloud ecosystem (Azure/Microsoft 365, AWS, or GCP).
- Experience with PostgreSQL and production observability.
- Comfort sitting in front of senior client stakeholders and owning the outcome, in a fast-moving environment with multiple active workstreams.
Preferred Qualifications
- Agentic AI systems, tool-calling systems, MCP servers, or multi-step AI workflows in production.
- AI, automation, or integration implementation in MSP, VAR, distributor, vendor, professional services, legal, or complex B2B environments.
- Microsoft 365 and Azure depth: Graph API, Teams, Entra ID, Bot Service.
- Production voice AI (Twilio, ElevenLabs, OpenAI Realtime API, or similar).
- Workflow orchestration platforms (Inngest, Temporal, or comparable).
- Consulting, agency, or implementation services background.
What Success Looks Like
- Clients see working AI inside their environment within weeks of kickoff.
- Engagements convert from pilot to production to expansion.
- Client engineering and operations teams trust PRESHai because they trust you.
- The patterns you push back to Core Engineering make the next engagement faster.
- Clients describe PRESHai as the team that actually ships.
Compensation And Benefits
- $125,000–$175,000 base salary.
- Medical, dental, and vision coverage.
- 401(k), unlimited PTO, and a professional development budget.
- Downtown Tampa office with a four-days-in-office, one-day-remote schedule.
- Travel approximately 10-20% for client engagements and on-site sessions.
- Direct exposure to production AI deployment across MSPs, solution providers, distributors, and manufacturers.
Prep for this interview
5 questions likely to come up at PRESHai, each matched to a line in this posting.
- 1Integrations and APIs
They wrote: “Practical experience with APIs, databases, OAuth flows, third-party integrations, webhooks, and system-to-system data movement.”
Walk me through connecting our product to a customer's internal system that has no documentation.
How to answer
Why they ask: This happens weekly in the job. They want a calm, step-by-step method.
- Find who owns the system and get read access to a test environment
- Watch real traffic or logs to learn the data shapes
- Build a thin adapter with logging around every call
- Agree on how failures get reported, and who fixes what
Tip: Talk about finding the owner of the system first. The code is the easy part.
- 2LLMs, RAG and agents
They wrote: “Experience with LLM application patterns: tool/function calling, RAG, prompt architecture, structured outputs, workflow automation.”
A customer wants a chatbot over their internal documents. How do you build it?
How to answer
Why they ask: RAG is the most common first project. They want the whole path, from messy files to answers people trust.
- Collect and clean the documents; handle permissions per user
- Split them into chunks, embed, and store with source links
- Retrieve, then answer with citations; say “I don't know” when retrieval is weak
- Build a test set of real questions with expected answers before launch
Tip: Spend more time on the data and on testing than on the model.
- 3Cloud, deployment and security
They wrote: “Fluency in at least one major cloud ecosystem (Azure/Microsoft 365, AWS, or GCP).”
How would you debug a deployment that works in staging but fails at the customer's site?
How to answer
Why they ask: Customer environments differ in ways you can't see. This tests method under pressure.
- Compare versions, config and environment variables
- Check network rules, proxies and certificates (common in enterprise)
- Look at resource limits and permissions
- Add the missing check to your install steps afterwards
Tip: List the usual suspects and how you'd check each without full access.
- 4Coding
They wrote: “Write production code in TypeScript and Python across agents, integrations, workflow orchestration, RAG, and voice interfaces.”
Here's a CSV export from a customer. Write a script that cleans it and loads it into our API.
How to answer
Why they ask: Very close to real FDE work. They watch how you handle bad rows and failures.
- Read with a proper CSV parser; check the header first
- Validate each row and collect errors, not crash on the first one
- Send in batches with retries and a clear report at the end
- Write one or two quick tests for the parsing
Tip: Talk through edge cases out loud: encodings, missing fields, duplicates, rate limits.
- 5Discovery and scoping
They wrote: “Lead working sessions with client engineering, IT, operations, and business stakeholders.”
A customer says “we want AI in our claims process.” What do you ask in the first meeting?
How to answer
Why they ask: Most FDE work starts this vague. They want to hear you find the real problem before you pick a tool.
- Map the current process: who touches a claim, in what order, with which systems
- Find the slowest or most error-prone step and ask what it costs them
- Agree on one measurable goal (for example time per claim, or error rate)
- Ask what data you can access, and who signs off on security
Tip: Ask about the work, not the technology. Who does it today, how long it takes, what a mistake costs, and how they'd know it got better.
Not the one? Get the next one by email
New roles land here every day. Pick what you want to hear about.
Want the job, not just the posting? Learn how FDEs work.
FDE Info is our free weekly newsletter for forward deployed engineers: tools, field notes from real deployments, and how FDE teams hire and pay.
Free. One email a week. Unsubscribe in one click.