> Markdown version of [/jobs/ext/3640464-forward-deployed-engineer](https://www.wearedevelopers.com/jobs/ext/3640464-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:** Opinr, Inc. - **Location:** San Francisco, CA, United States (Remote available) - **Experience:** Experienced - **Contract:** Permanent contract - **Skills:** JavaScript (Programming Language), Data Mapping, Software Debugging, RAID, JSON, Python (Programming Language), Regression Testing, Large Language Models, Restful APIs, Webhooks - **Published:** October 8, 2026 - **Apply:** https://www.builtincolorado.com/job/forward-deployed-engineer/11550411?handler=ApplyRedirect ## About the Role * Experience: 3+ years in customer-facing technical delivery - forward deployed engineering, solutions architecture, implementation consulting, or technical professional services. * Hands-on technical skills: Comfortable with REST APIs, JSON, webhooks, and data mapping; able to script in Python or JavaScript and debug a failure across two systems you didn't build. * Production LLM experience: You've worked with LLMs in production rather than in demos - prompts, retrieval, agent workflows, and evaluating output systematically rather than by vibes. * Product-centric & shipping-biased: You think about the user in front of the screen, not the requirement in the document, and favor shipping something usable and iterating over shipping something perfect and late. * Delivery fluency: You've carried a go-live date in front of a customer, so project plans, RAID logs, phase gates, test scenarios and cases, SIT, UAT, and regression testing are familiar ground. * Communication: Thoughtful and streamlined - you listen first, hold your own with a Chief Procurement Officer, privacy counsel, and security architect in the same room, and can say no to a customer and keep the relationship stronger for it. * Domain knowledge (a plus): Third-party risk, procurement, or compliance experience helps - we'll teach you the rest. ## Description * Document & optimize it: Map the current state and agree a target state against the metrics customers actually care about - onboarding cycle time, assessment turnaround, reviewer effort, audit readiness. You're not there to digitize a bad process faithfully, and a workflow that's technically correct but painful to use won't get adopted - so reviewer effort and drop-off are your problem, not theirs. * Configure & automate it in Certa: Build the workflows, forms, logic, risk scoring, and approvals in Studio using Vibe Configuration - live in the room wherever possible - plus the integrations and data flows into existing systems, and debug them when they break. * Own the delivery: Own the plan, governance, and test cycle (scenarios and cases, SIT, UAT with the customer's own testers, sanity and regression), then cutover, go-live, hypercare, and a clean handover - accountable for the date and the success metrics behind it. * Bring learning back from the front lines: Find the platform's real limits before anyone else does and bring them to Product with evidence - the customer, the frequency, the cost of the workaround - and turn what you built into templates and accelerators, so the next deployment starts ahead of where yours did.