Requirements
Must-Have3+ years in a software engineering role with direct client- or field-facing exposure (solutions engineering, implementation engineering, or technical consulting)Full-stack or backend proficiency with hands-on production code experience — reading and writing code, not configuration-only workDemonstrated experience building custom integrations, scripts, or internal tooling to connect a core product with external client systemsTrack record of owning technical implementations end-to-end: scoping, building, shipping, and supportingExperience running technical discovery sessions or live debugging with client stakeholdersC1+ English (CEFR) — primary technical contact for US-based client accountsNice-to-HaveExperience with API integrations, webhooks, and common auth patterns (OAuth, SSO)Background in a startup or agency environment with rapidly shifting client requirementsFamiliarity with data pipelines, ETL, or scripting (Python preferred)Prior role blending sales engineering or customer success with hands-on coding
Description
Work From AnywhereWork Schedule: 9:00 AM–6:00 PM ETAbout Pearl TalentPearl works with the top 1% of candidates from around the world and connects them with the best startups in the US and EU. Our clients have raised over $5B in aggregate and are backed by companies like OpenAI, a16z, and Founders Fund.Hear why we exist, what we believe in, and who we're building for: Watch hereAbout the Role The Forward Deployed Engineer sits at the intersection of engineering and client success — embedded directly with customers to implement, customize, and scale the product in their environment. This isn’t a back-office engineering role: the FDE owns the outcome of deployment, from technical integration through adoption, and is often the primary technical voice the client interacts with post-sale.What You’ll Own: Deployment & IntegrationLead technical onboarding and implementation for new clients, configuring the product to fit their workflows, data, and systemsBuild custom integrations, scripts, or lightweight tools to bridge gaps between the core product and each client's existing stackTranslate ambiguous client requirements into a scoped technical plan and execute it independentlyClient-Facing Technical OwnershipServe as the primary technical point of contact for assigned accounts during and after rolloutRun technical discovery calls and debug issues live with client stakeholdersCommunicate solutions in terms non-technical audiences can act onIdentify recurring friction points across clients and feed them back to product and engineering as structured inputIteration & ScaleMonitor deployed solutions for reliability and performance, fixing or flagging issues before the client noticesDocument deployment patterns and reusable components so future rollouts move fasterBalance delivery speed against long-term durability of deployed solutions