> Markdown version of [/jobs/ext/2718430-forward-deployed-engineer](https://www.wearedevelopers.com/jobs/ext/2718430-forward-deployed-engineer). Every page supports `.md` or `Accept: text/markdown`. Links point to the HTML versions so they work for humans too. Agent guide: [/agents.md](https://www.wearedevelopers.com/agents.md). --- # Forward Deployed Engineer - **Company:** TaskRabbit - **Location:** San Francisco, United States - **Experience:** Experienced - **Salary:** $175,000.0 - $225,000.0 - **Contract:** Permanent contract - **Skills:** Application Programming Interfaces (APIs), Artificial Intelligence, System Configuration, Software Debugging, Automation of Marketing, Large Language Models, Model Validation, Zapier, Production Code, Data Analytics, Low-code, Marketplace, Software Version Control - **Published:** September 4, 2026 - **Apply:** https://startup.jobs/forward-deployed-engineer-taskrabbit-7954740 ## About the Role * Production Claude experience (required): 2+ years hands-on building AI agents, automations, or internal tools professionally, with direct, independent, code-level work in Claude Code, the Claude API, Claude Skills/Agent SDK, or an agentic framework built on top of Claude. You should be able to walk us through a system you built, why you made the architecture choices you did, and what broke in production. * Software engineering fundamentals: Comfortable writing and owning real code - not exclusively configuring no-code/automation platforms. You should be fluent in things like API integration, MCP, version control, testing, and debugging a system you didn't just prototype but actually run. * Technical judgment: You surface model selection tradeoffs, caching and cost strategy, reliability/failure modes, and human-in-the-loop design without being asked - because you've had to make those calls before and lived with the consequences. You also know when a workflow's data sensitivity should change the build: what a system can safely touch, and what needs scoping, redaction, or a human review step before it does. * Business partnership: Track record embedding with non-technical teams, running discovery, and converting workflows into scoped builds - including the judgment to say no to AI when it's not the right fix. * Enablement mindset: You've built capability in other people, not just built things for them. * High empathy: Adept at sitting with a skeptical or overwhelmed team member long enough to actually understand their workflows, not just extract requirements * Stakeholder influence: Comfortable presenting to and moving senior leaders and frontline teams alike. * Impact measurement: Data-driven by default - you define baselines and metrics from scratch and translate results into business terms. * Builder mindset: Scrappy, self-directed, comfortable operating without dedicated engineering support in a fast-paced, resource-constrained environment. * Industry (preferred): Marketplace or gig-economy company (e.g., Airbnb, Lyft, DoorDash) or high-growth startup. ## Description Every business function at Taskrabbit - Marketing, Customer Support, Finance, Operations - is a "customer" with real workflows, real data, and real friction. Your job is to embed with them, scope their use cases, and build the Claude-powered agent, automation, or tool that solves them. This is an internal-facing role - there is no external customer or product work. Reporting to the Director of AI Strategy and Enablement, you'll operate the way an FDE operates at a high-growth AI company: full ownership of a deployment from discovery through production and direct accountability for whether what you ship actually changes a metric. In most cases you'll own a build end-to-end solo; in some functions you may partner with that team's own subject-matter expert to pair domain depth with technical execution. We are hiring for engineering depth first. This is not a role for someone whose experience is limited to no-code/low-code automation platforms (Zapier, Make, n8n) without underlying software engineering fundamentals. The bar is: you have personally written, tested, and shipped production code that calls an LLM - ideally Claude - as part of an agent, pipeline, or internal tool, and you can speak fluently to the engineering decisions (not just the workflow decisions) behind it. What You'll Do * Discover & scope: Embed with a business function, run structured technical discovery, and turn an ambiguous use case idea into a scoped build. Build in production: Independently design, write, test, and deploy Claude-powered agents, automations, and internal tools (Claude Code, Claude Cowork, Claude API/Agent SDK, or agentic frameworks built on Claude) - owning the full lifecycle from first commit to something running unattended in production. * Engineer for reliability, not demos: Make and defend real engineering decisions - model selection, context/caching strategy, evals, human-in-the-loop checkpoints, error handling, cost forecasting - the difference between a working prototype and something that survives contact with real data and real users. * Measure: Establish a baseline before every build; define the metric that proves impact (time saved, error rate, throughput) and instrument for it from day one. * Enable: Leave each function more capable than you found it - train non-technical teams to identify and eventually build their own lightweight automations, without creating dependency on this role. * Influence: Translate between business problems and technical tradeoffs; move skeptical stakeholders from "prove it" to adoption; align priorities with senior leaders and company OKRs. * Scale patterns: Turn what works in one function into a reusable playbook other teams - and other builders - can pick up. ## Related Videos - [Launching a marketplace on-time: A lesson in taking shortcuts using spreadsheets!](https://www.wearedevelopers.com/videos/477-launching-a-marketplace-on-time-a-lesson-in-taking-shortcuts-using-spreadsheets) - [Reimagining app development with Low-code and AI](https://www.wearedevelopers.com/videos/1651-reimagining-app-development-with-low-code-and-ai) - [HR ROBO SAPIENS: Decoding AI Agents and Workflow Automation for Modern Recruitment](https://www.wearedevelopers.com/videos/1470-hr-robo-sapiens-decoding-ai-agents-and-workflow-automation-for-modern-recruitment) - [Agentic employees in world's most downloaded FinTech app](https://www.wearedevelopers.com/videos/100123-agentic-employees-in-world-s-most-downloaded-fintech-app) - [How to Monetize Your APIs](https://www.wearedevelopers.com/videos/749-how-to-monetize-your-apis) - [What If Apps Built Themselves? AI-Powered Low-Code for the Industrial Enterprise](https://www.wearedevelopers.com/videos/2079-what-if-apps-built-themselves-ai-powered-low-code-for-the-industrial-enterprise) ## Related Articles - [9 Claude Code Skills to Speed Up Your Workflow](https://www.wearedevelopers.com/magazine/740-9-claude-code-skills-to-speed-up-your-workflow) - [Navigating the AI Shift](https://www.wearedevelopers.com/magazine/629-navigating-the-ai-shift) - [Dev Digest 120 - Apple and peers](https://www.wearedevelopers.com/magazine/455-dev-digest-120-apple-and-peers) - [Dev Digest 137 - AI'm not sure about this](https://www.wearedevelopers.com/magazine/485-dev-digest-137-ai-m-not-sure-about-this) - [Dev Digest 121 - AI goes offline](https://www.wearedevelopers.com/magazine/456-dev-digest-121-ai-goes-offline) - [What is Agentic Programming and Why Should Developers Care?](https://www.wearedevelopers.com/magazine/625-what-is-agentic-programming-and-why-should-developers-care)