ZipRecruiter

Log In

2

Remote Forward Deployed Software Engineer Jobs in California

Tread

AI Native Forward Deployed Engineer

San Francisco, CA · On-site +1

$120K - $160K/yr

To scale from $XM to $XXM+ ARR, we need Forward Deployed Engineers who can live at the intersection of customer operations and our codebase-turning what they see in the field into shipped software ...

FloQast

Senior Forward Deployed Accountant

San Francisco, CA · On-site +1

$87K - $109K/yr

Previous roles similar to Forward Deployed Engineer, Resident Consultant, or Embedded Solutions ... remote #BI-remote The base pay range for this position is $132,000- $198,000. This position is ...

Mantari

Head of Software

Torrance, CA · On-site +1

$141K - $189K/yr

... and Forward Deployed Engineers(who integrate customer systems). Your job: turn the full-stack ... Experience integrating multi-modal data (satellite, sensor, remote sensing, IoT) * Knowledge of ...

OpenPlay

Software Engineer

Santa Monica, CA · On-site +1

You'll work with us to design, develop, and deploy new application features for one of the world ... This is a full-time position that can be local (Los Angeles) or fully remote. What's an OpenPlay? W ...

First American

Senior Software Engineer

Santa Ana, CA · On-site +1

$127K - $168K/yr

What We Do Remote Work Welcome Be part of a transformative team that is shaping the way First ... We are looking for forward-thinking engineers who will envision, design, build, and deploy AI ...

DocuSign

Software Engineer

San Francisco, CA · On-site +1

You will design, build, test, deploy, and operate scalable, highly available backend services and ... Employee divides their time between in-office and remote work. Access to an office location is ...

Vannevar

Senior Software Engineer - ATO

San Diego, CA · On-site +1

$150K - $215K/yr

Experience deploying software into a government-authorized environment (IL6, JWICS) * Full-stack ... Remote friendly with WeWork access * Unlimited PTO, shared downtime during the federal holiday ...

Britive

Software Engineer

San Francisco, CA · On-site +1

Our patent-pending technology is deployed at companies of all sizes around the world, including ... We are fully remote (US only, other areas are subject to review). * Competitive compensation and ...

GCX Healthcare Solutions

Software Engineer

Petaluma, CA · Remote

$125K - $150K/hr

Build and deploy containerized applications using Docker and CI/CD pipelines * Contribute to system ... remote management, and operational insights. You'll join a small, high-impact team (3-4 engineers ...

previous page

Showing results 41-60

All JobsForward Deployed Software Engineer JobsRemote Forward Deployed Software Engineer JobsRemote Forward Deployed Software Engineer Jobs in California

Remote Forward Deployed Software Engineer information

What are the key skills and qualifications needed to thrive as a remote forward deployed software engineer?

To excel as a Remote Forward Deployed Software Engineer, you need strong programming skills, experience in software deployment, and a bachelor's degree in computer science or a related field. Familiarity with cloud platforms, version control systems like Git, and continuous integration/continuous deployment (CI/CD) tools is typically required. Exceptional problem-solving, communication, and self-management skills help you collaborate with clients and distributed teams effectively. These abilities ensure you can deliver tailored technical solutions efficiently and adapt to the unique challenges of remote and client-facing environments.

What is a remote forward deployed software engineer?

A Remote Forward Deployed Software Engineer is a software engineer who works offsite (remotely) and is embedded directly with a client or customer team to help implement, customize, and integrate technical solutions. They often serve as both technical experts and liaisons, working closely with clients to understand their needs and deliver tailored software products. Their role typically involves travel or virtual collaboration with client teams, rapid problem-solving, and adapting existing software to unique business requirements. This position requires strong communication skills, technical proficiency, and the ability to work independently from a remote location.

How does a remote forward deployed software engineer typically collaborate with client teams and internal stakeholders?

As a Remote Forward Deployed Software Engineer, you'll work closely with client teams to understand their unique technical needs and integrate solutions directly into their environments. Collaboration often happens through regular video calls, shared documentation, and agile project management tools. You'll also coordinate with internal engineering, product, and support teams to ensure that client requirements are met while maintaining high code quality. Building strong communication channels is key to success in this role, as you'll often act as the primary technical liaison between your company and the client.

What is the difference between Remote Forward Deployed Software Engineer vs Remote Software Engineer?

AspectRemote Forward Deployed Software EngineerRemote Software Engineer
FocusDirectly interacts with clients and deploys solutions on-site or close to the customerDevelops software primarily in a remote environment without direct client deployment responsibilities
Work EnvironmentHybrid or on-site with client engagementFully remote, often within a development team
ResponsibilitiesCustomizing, deploying, and maintaining solutions at client locationsDesigning, coding, and testing software applications
Skills & CertificationsStrong communication, deployment, and client-facing skills; relevant certifications varyProgramming, software development, and possibly cloud certifications

The main difference is that Remote Forward Deployed Software Engineers work closely with clients, deploying solutions on-site or near the customer, while Remote Software Engineers focus on developing software remotely without direct deployment duties. Both roles require technical expertise, but their work environments and responsibilities differ significantly.

What are the most commonly searched types of Forward Deployed Software Engineer jobs in California? The most popular types of Forward Deployed Software Engineer jobs in California are:
What are popular job titles related to Remote Forward Deployed Software Engineer jobs in California? For Remote Forward Deployed Software Engineer jobs in California, the most frequently searched job titles are:
What job categories do people searching Remote Forward Deployed Software Engineer jobs in California look for? The top searched job categories for Remote Forward Deployed Software Engineer jobs in California are:
What cities in California are hiring for Remote Forward Deployed Software Engineer jobs? Cities in California with the most Remote Forward Deployed Software Engineer job openings:
Remote Forward Deployed Software Engineer jobs near you
Infographic showing various Remote Forward Deployed Software Engineer job openings in California as of August 2026, with employment types broken down into 1% Internship, 85% Full Time, 9% Part Time, 2% Temporary, and 3% Contract. Highlights an 87% Physical, 4% Hybrid, and 9% Remote job distribution.

AI Native Forward Deployed Engineer

Tread

San Francisco, CA • On-site, Remote

$120K - $160K/yr

Full-time

Re-posted 26 days ago

Job description

About Tread
Tread is an AI-native vertical SaaS platform transforming construction materials logistics-a massive, essential industry that moves the aggregate, asphalt, and concrete behind every road, bridge, and building. In March 2026, we crossed $1Bn in monthly delivered load value on the platform, and we're at ~$XM ARR and growing fast.
Our AI-powered platform serves Haulers, Producers, and Contractors-optimizing truck routing, loaded-mile delivery, and project planning while delivering exceptional customer service through personalized AI agents.
We're a Series A company backed by Mucker Capital, and we're building the team that will take us from $XM to $XXM+ ARR.
Why This Role Exists
Tread's customers are construction companies, materials producers, and hauling fleets. Their operations are complex, messy, and high-stakes. Dispatchers are moving hundreds of trucks a day. Scale operators are weighing thousands of loads. Back-office teams are reconciling millions of dollars in freight.
We can't build the right product from a desk. This role exists to close the gap between our customers and our codebase. You'll be in the field learning how these operations actually work, then back at your machine shipping solutions the same day. The feedback loop is measured in hours, not sprints.
Today, technical implementation and field-driven product development is run by the founding team and a small engineering group. To scale from $XM to $XXM+ ARR, we need Forward Deployed Engineers who can live at the intersection of customer operations and our codebase-turning what they see in the field into shipped software before the next site visit.
What You Own
You are the technical bridge between our customers and our product. You'll own the end-to-end technical relationship for your accounts, from first integration through long-term expansion, across four core areas:
Customer Implementation & Technical Delivery Lead technical implementation for new customers: API integrations, data mapping, workflow configuration, and scale house connectivity. Build custom integrations, data pipelines, and automation for customers with complex requirements. Debug and resolve technical issues in the field, often on the same day they surface. Own the technical relationship with assigned accounts-you are their go-to when something is broken or needs to be built.
Product Development from the Field Turn customer pain points into shipped features. You have the context and the ability to build. Contribute directly to Tread's codebase (Rails API, GraphQL, React) based on what you learn in the field. Prototype and validate solutions with customers before they become full product investments. Feed structured, prioritized insights to Product and Engineering. Our model: 45 minutes with the customer, 45 minutes building.
Scaled Enablement & Documentation Build technical onboarding materials, API documentation, and integration guides for customers. Develop self-serve tools and content that reduce the need for hands-on support as we scale. Plan and facilitate QBRs with strategic accounts. Bring data. Bring insights. Bring the roadmap.
Expansion & Retention Through Technical Depth Identify what makes Tread sticky and execute relentlessly to deliver that value. Expand revenue with existing customers by uncovering problems and solving them before they're asked. Help turn our data moat into self-reinforcing product loops that get smarter the longer a customer is on the platform. Own the technical health of your portfolio.
What Success Looks Like
First 90 Days
  • Visited at least 3 customer sites. You can describe their dispatch workflow, scale house operations, and back-office processes from memory.
  • Shipped at least 2 customer-facing improvements based on direct field observations.
  • Taken ownership of the technical implementation for at least 1 new customer.
  • Built relationships with key users at your assigned accounts. They know your name and they call you directly.
  • Established a baseline view of open technical debt and integration gaps across your portfolio.

First 6 Months
  • Embedded with customers. Learning the codebase while in the field. Shipping fast alongside a team of under 20 people where your impact is immediate and visible.
  • Established a repeatable pattern: customer meeting to shipped outcome in under a week.
  • Contributed meaningfully to at least 1 product initiative that originated from your field work.
  • Technical training content and integration guides shipped and in use by customers.
  • At least 1 expansion opportunity identified and influenced by your work.
  • Time-to-first-value for new implementations trending down measurably.

First Year
  • Customers in your portfolio have measurably higher adoption and satisfaction than baseline.
  • You've become the connective tissue between what customers need and what we build.
  • Multiple product features in production trace back to your field insights.
  • You've helped define the FDE playbook that the next hire will use.
  • You are the person customers call when something is broken, and the person Engineering trusts to represent the field in any roadmap conversation.

What We're Looking For
  • 2+ years of software engineering experience. You can write production code in at least one of: Ruby/Rails, JavaScript/React, Python, or equivalent.
  • Comfort with APIs, databases, and data pipelines. You can read a GraphQL schema, debug an integration, and write a migration.
  • Customer-facing instincts. You can sit in a room with a VP of Operations at a trucking company and earn their trust.
  • Bias toward action. You see a problem, you fix it. You don't wait for a ticket.
  • Strong written and verbal communication. You can translate a messy customer conversation into a clear problem statement and a proposed solution.
  • Willingness to travel. You'll be on-site with customers regularly, especially early on.
  • High ownership, low ego. You'll do support tickets, write docs, build features, and present at QBRs. Whatever the customer needs.
  • Analytical mindset. You instrument what you ship, track adoption, and use data to decide what to build next.
  • Builder mentality. You'll personally debug a scale house integration in the morning and prototype a new dispatcher workflow in the afternoon.

Bonus Points
  • Experience in construction technology, heavy civil, logistics, supply chain, or field services.
  • Familiarity with our stack: Rails, GraphQL, React, Intercom, Linear, PostHog, Omni.
  • Experience with AI/ML product development or leveraging LLMs in customer-facing workflows (AI-assisted integrations, automated onboarding, intelligent ticket deflection).
  • You've worked at a Series A-C company with under 50 people and thrived in the ambiguity.
  • Experience with e-ticketing, scale house systems, ERP integrations, or DOT compliance.
  • You've shipped a feature that originated from a single customer conversation and watched it scale across an entire book of business.

Apply