Forward Deployed Engineer

About the role

This role operates within the Solutions team, guiding enterprise customers through complex GTM implementations and integrations. Success depends on technical fluency, sharp judgment, and deep customer empathy to convert intricate use cases into working outcomes. The team translates onboarding momentum into lasting platform value and shapes product thinking.

Software engineers turn product ideas into working code. Engineers work in small teams, review each other's work, and ship in small batches. Most teams follow agile practices such as sprints and daily standups. Engineers also write tests, fix bugs, and improve performance. The field values clear communication as much as technical skill. Engineers spend part of every week on planning, code review, and debugging, not just writing new code. The ability to explain a technical decision in plain words separates strong engineers from the rest.

Key facts

What you'll do

Architect a best-in-class GTM stack centered on Attio for Attio's highest-value customers, defining the strategic guidance and deployment approach. Synthesize customer insight and feed it directly to the Product team, creating a direct line from high-value customers to the roadmap.

Requirements

Bring 2+ years of experience as a developer, GTM engineer, or in a technical solutions role to apply context to customer environments. Demonstrate deep hands-on experience with GTM tooling and understand what sales, CS, and marketing teams need to operate effectively in live settings. Architect API integrations live in customer meetings while maintaining a high standard of technical design and clarity. Use AI coding platforms such as Claude Code and Cursor to build JavaScript and create reusable internal tooling for efficiency. Experiment early with the AI landscape instead of waiting for use cases to become obvious to accelerate solution design. Master the no-code/low-code integration stack including N8n, Zapier, and Make, and form credible opinions on unfamiliar tools quickly to adapt to stack variations. Comfort with data infrastructure concepts such as ETL, reverse ETL, CDPs, and tools like Segment, Rudderstack, and Polytomic to enable reliable data flows.

Nice to have

Experience designing and running expert referral programs and self-serve playbooks that scale across customer segments.

Skills & tools

Attio, GTM stacks, API integrations, no-code automation, data infrastructure, CRM platforms.

Practical notes

This role is based in New York and requires onsite presence. The team operates with a high bar for craft, clarity, and customer outcomes. Travel may be required for customer work. Typical interview steps

Hiring for engineering roles usually starts with a recruiter screen, followed by one or two technical rounds. Candidates often solve a coding problem, discuss past projects, and answer system design questions. Some loops include a take-home task. Final rounds typically cover team fit and give candidates a chance to ask questions. Interviewers look for how you break down an unfamiliar problem, not just whether you reach the answer. Practicing a few problems aloud and reviewing your own past projects are the best preparation.

Good to know

Questions to ask

Useful questions for the interview: what a typical week looks like, how work is assigned, what tools the team uses, and how feedback works. Asking how the role has changed recently and what the team wishes it had known when joining is also reasonable. Questions about the manager's priorities are especially valued.

Career growth

Engineering careers usually progress from individual contributor to senior, staff, and principal levels. Some engineers move into management and lead teams of five to twenty people. Others stay on the technical track. Growth follows demonstrated impact, not tenure alone. A typical engineering ladder has clear levels with defined expectations for scope, quality, and mentorship. Moving up usually requires owning outcomes end to end rather than completing assigned tickets.