Forward Deployed AI Engineer (TypeScript) - Remote - USA

<strong>About FullStack<br><br></strong>FullStack is your AI-native engineering partner, built to turn AI capability into certainty. Most companies can demo AI; few can get it to production and prove what it produced. We close that gap with three capabilities, AI built into your products from the start, elite vetted talent who apply it, and transparent execution that shows value every step of the way. With now over 600 customers in North America, FullStack is one integrated partner for all your AI engineering needs. With FullStack, you move forward with confidence.<br><br><strong>We’re Most Proud Of<br><br></strong><ul><li>Offering life-changing career opportunities to talented software professionals across the Americas.</li><li>Building highly-skilled software development teams for hundreds of the world’s greatest companies.</li><li>Having delivered hundreds of successful custom software solutions, which have positively impacted the lives and careers of millions of users.</li><li>Our 4.1-star rating on GlassDoor.</li><li>Our client Net Promoter Score of 68, twice the industry average.<br><br></li></ul><strong>The Position<br><br></strong>Forward Deployed Engineers sit inside the client’s problem, not next to it. You embed with an enterprise team, find the work that actually warrants AI, architect the system, build it, and make it hold up in the real environment.<br><br>This is a three-way role:<strong> consultant, operator, engineer</strong>. You should be as comfortable pressure-testing a business case with a COO or VP of Engineering as you are debugging why an agent’s tool-calling loop degraded after a context change. The people who succeed here can hold a discovery conversation on Monday and ship what they scoped on Thursday.<br><br>On this track, your edge is application engineering: you make agents real inside the client’s actual systems, workflows, and delivery pipelines.<br><br>We work with regulated industries and Fortune 500 clients who have AI mandates, real constraints, and low tolerance for demos that don’t hold up.<br><br><strong>How We Approach The Work<br><br></strong>FDEs are trusted to shape the solution, not only deliver it. Every engagement calls for architect-level judgment:<br><br><ul><li>Reframes the request. Treats “we need an agent for X” as a hypothesis, not a spec.</li><li>Decomposes the problem. Outcome → process → decisions → data → systems → actors → constraints — before choosing technology.</li><li>Chooses the intervention. Remove, simplify, traditional software, automation, LLM, RAG, agent, or multi-agent — and defends why.</li><li>Owns the architecture decision. Documents trade-offs (ADRs), sets success metrics, pushes back on scope that won’t deliver value.<br><br></li></ul><strong>Consultative Discovery<br><br></strong>Clients rarely arrive with a fully formed problem, and the FDE’s first contribution is helping them see it clearly. You lead discovery with genuine curiosity, moving the conversation from stated requirements to underlying needs, and you build credibility through the depth of your understanding rather than the breadth of your pitch.<br><br><ul><li>Uncovers business drivers. What outcome matters, what it’s worth, why now, and what happens if nothing changes.</li><li>Uncovers personal drivers. What each stakeholder is measured on, what they’re worried about, and what a win looks like for them individually.</li><li>Surfaces constraints early. Security, compliance, data access, budget, skills, politics, timelines — the things that kill projects in month two.</li><li>Aligns stakeholders. Spots conflicting goals between business, engineering, and risk, and brings them to a shared definition of success.</li><li>Asks strategic questions. Follows the answer with “why,” “how do you know,” and “what happens today when…” — without interrogating. Clients leave the conversation understanding their own problem better.</li><li>Earns authority through depth. Credibility comes from the quality of the questions and the insight in the playback, not from pitching technology.<br><br></li></ul><strong>What You'll Do<br><br></strong><ul><li>Discover. Run workshops and process discovery with business and engineering stakeholders. Separate genuine AI problems from workflow problems wearing an AI costume. Come back with a scoped, defensible point of view.</li><li>Structure the process and the spec. For any business or engineering process being automated, map the current state, decision points, and exceptions, then turn it into specifications that both people and AI systems can execute against reliably.</li><li>Architect & design. Design agentic systems end to end — orchestration, context and retrieval architecture, tool and MCP integration, guardrails, human-in-the-loop checkpoints, and the boundaries between deterministic and non-deterministic components.</li><li>Build. Ship working systems — agents, multi-step automations, internal tooling, integration layers. You are hands-on. Prototypes that prove value in weeks, not slideware.</li><li>Engineer the delivery system. Own CI/CD for what you build: build, test, release, environments.</li><li>Consult. Present to and defend decisions in front of CTOs, VPs of Engineering, and business leadership. Quantify impact in their terms. Support pre-sales scoping and proposal work when the deal calls for it.<br><br></li></ul><strong>What We're Looking For<br><br></strong><strong>Engineering foundation<br><br></strong><ul><li>8–10+ years of professional software development; back-end-heavy, full-stack capable.</li><li>Primary production experience in one of our core ecosystems: TypeScript / Node + React, Python, .NET / C#, or Java.</li><li>Strong in APIs, service design, event-driven / distributed systems, and data modeling.</li><li>Track record as a Solution Architect, Principal Engineer, or Tech Lead — can assess a current-state environment and define a credible roadmap.</li><li>Has designed and owned CI/CD — build, test, release, environments — not just used someone else’s pipeline.<br><br></li></ul><strong>Applied AI<br><br></strong><ul><li>Has built and shipped LLM and agent systems beyond a demo.</li><li>Deep fluency with agentic tooling: Claude Code, agent frameworks, MCP, tool/function calling, multi-agent orchestration.</li><li>Context and spec engineering: structures codebases, specifications, process definitions, and context to produce reliable, context-efficient AI output.</li><li>Integration literacy: understands integration methods and options — APIs, webhooks, event streams, iPaaS (n8n, MuleSoft, etc.), MCP — and the constraints and strategies behind connecting AI to systems of record. Doesn’t need to own every integration, but can design around them and guide the team that does.<br><br></li></ul><strong>Consulting & business<br><br></strong><ul><li>Demonstrates the discovery behaviors above: business and personal drivers, constraints, stakeholder alignment, strategic questioning.</li><li>Runs client conversations without an account manager in the room: workshops, proposal walkthroughs, hard questions, pushback.</li><li>Translates technical decisions into business outcomes — cycle time, cost per transaction, throughput, risk reduction, ROI.</li><li>Exceptional written and verbal communication; credible in front of senior stakeholders.<br><br></li></ul><strong>Strong Plus<br><br></strong><ul><li>Production AI operations (Day 2): eval harnesses, observability and tracing, cost and token economics, drift, debugging non-deterministic systems.</li><li>Prompt- and eval-level regression testing running in CI and gating releases.</li><li>Delivery in regulated environments (financial services, healthcare, insurance, manufacturing).</li><li>Pre-sales support: discovery calls, SOW and estimate shaping, technical proposal defense.</li><li>Process mining, operations analysis, or transformation consulting background.</li><li>Client enablement and training — building the client team’s capability, not just the system.</li><li>Prior consulting or agency environment; comfort with ambiguity and multiple accounts.<br><br></li></ul><strong>Work Authorization Requirements<br><br></strong><ul><li>Applicants must be currently authorized to work in the United States on a full-time basis.</li><li>FullStack will not sponsor applicants for work visas now or in the future.<br><br></li></ul><strong>What We Offer<br><br></strong><ul><li>Competitive Salary.</li><li>Paid Time Off (vacation, sick leave, parental leave, holidays).</li><li>100% remote work.</li><li>The ability to work with leading startups and Fortune 500 companies.</li><li>Health, dental, and vision insurance.</li><li>401(k) w/ 4% match.</li><li>Ample opportunity for career advancement.</li><li>Continuing education opportunities.<br><br></li></ul>FullStack is proud to be an equal opportunity workplace. We are committed to equal employment opportunity regardless of race, color, ancestry, religion, sex, national origin, sexual orientation, age, citizenship, marital status, disability, gender identity, or Veteran status.<br><br>Learn more about our Applicants Privacy Notice.

Back to blog

Other Jobs To Apply

Common Interview Questions And Answers

1. HOW DO YOU PLAN YOUR DAY?

This is what this question poses: When do you focus and start working seriously? What are the hours you work optimally? Are you a night owl? A morning bird? Remote teams can be made up of people working on different shifts and around the world, so you won't necessarily be stuck in the 9-5 schedule if it's not for you...

2. HOW DO YOU USE THE DIFFERENT COMMUNICATION TOOLS IN DIFFERENT SITUATIONS?

When you're working on a remote team, there's no way to chat in the hallway between meetings or catch up on the latest project during an office carpool. Therefore, virtual communication will be absolutely essential to get your work done...

3. WHAT IS "WORKING REMOTE" REALLY FOR YOU?

Many people want to work remotely because of the flexibility it allows. You can work anywhere and at any time of the day...

4. WHAT DO YOU NEED IN YOUR PHYSICAL WORKSPACE TO SUCCEED IN YOUR WORK?

With this question, companies are looking to see what equipment they may need to provide you with and to verify how aware you are of what remote working could mean for you physically and logistically...

5. HOW DO YOU PROCESS INFORMATION?

Several years ago, I was working in a team to plan a big event. My supervisor made us all work as a team before the big day. One of our activities has been to find out how each of us processes information...

6. HOW DO YOU MANAGE THE CALENDAR AND THE PROGRAM? WHICH APPLICATIONS / SYSTEM DO YOU USE?

Or you may receive even more specific questions, such as: What's on your calendar? Do you plan blocks of time to do certain types of work? Do you have an open calendar that everyone can see?...

7. HOW DO YOU ORGANIZE FILES, LINKS, AND TABS ON YOUR COMPUTER?

Just like your schedule, how you track files and other information is very important. After all, everything is digital!...

8. HOW TO PRIORITIZE WORK?

The day I watched Marie Forleo's film separating the important from the urgent, my life changed. Not all remote jobs start fast, but most of them are...

9. HOW DO YOU PREPARE FOR A MEETING AND PREPARE A MEETING? WHAT DO YOU SEE HAPPENING DURING THE MEETING?

Just as communication is essential when working remotely, so is organization. Because you won't have those opportunities in the elevator or a casual conversation in the lunchroom, you should take advantage of the little time you have in a video or phone conference...

10. HOW DO YOU USE TECHNOLOGY ON A DAILY BASIS, IN YOUR WORK AND FOR YOUR PLEASURE?

This is a great question because it shows your comfort level with technology, which is very important for a remote worker because you will be working with technology over time...