Forward Deployed Engineer I/II

About the role

This role connects Giga with enterprise customers to deploy real-time AI agents. You will serve as a technical interface in San Francisco, handling customer engagements and owning agent delivery. The position operates in a voice AI company serving Fortune 500 clients in regulated environments.

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

You will run discovery calls and demos for customer engagements, ensuring clear understanding of requirements. Solutions are built and maintained as world class agents through rapid prototyping and iteration. Communication with customers and documentation of best practices will speed up future projects and support adoption. Feedback from production usage is captured and turned into new features for the platform. Platform strength is improved through collaboration with core teams, benefiting all customers.

Requirements

You know the basics of React, Python, tool calls, and APIs. Experience in customer-facing roles enables effective problem solving with strong interpersonal communication. You prefer contexts where you can switch rapidly and maintain a high bar for quality work. Capacity to work long productive hours supports customer focus and attention to detail. You are obsessive about delivering high-quality work and remain coachable to adapt quickly to feedback. At least 1+ years of experience is required, preferably in computer science, analytics, or consulting. US work authorization is required.

Practical notes

This role is based in San Francisco and requires US work authorization. The position is full_time with standard expectations for availability in fast paced settings. 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

Voice AI systems enable real time interaction between machines and humans. Enterprise automation relies on tools for agent development, monitoring, and continuous iteration. Startups in this space often operate at high pace with strong founder involvement. Teams work across product, engineering, and support to serve regulated industries. Understanding of APIs, Python, and React supports success in modern agent platforms.

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.