1

Director Software Development Jobs in Fremont, CA

The Director, Software Engineering leads the execution and delivery of complex software and AI/ML ... This role oversees the full development lifecycle, champions DevOps practices, and drives cloud ...

The Director, Software Engineering leads the execution and delivery of complex software and AI/ML ... This role oversees the full development lifecycle, champions DevOps practices, and drives cloud ...

The Director, Software Engineering leads the execution and delivery of complex software and AI/ML ... This role oversees the full development lifecycle, champions DevOps practices, and drives cloud ...

The Director, Software Engineering leads the execution and delivery of complex software and AI/ML ... This role oversees the full development lifecycle, champions DevOps practices, and drives cloud ...

The Director, Software Engineering leads the execution and delivery of complex software and AI/ML ... This role oversees the full development lifecycle, champions DevOps practices, and drives cloud ...

The Director, Software Engineering leads the execution and delivery of complex software and AI/ML ... This role oversees the full development lifecycle, champions DevOps practices, and drives cloud ...

The Director, Software Engineering leads the execution and delivery of complex software and AI/ML ... This role oversees the full development lifecycle, champions DevOps practices, and drives cloud ...

As the Director of Software Engineering, you are a hands‑on, "rock star" Java developer and ... Feature Development & Architecture: You will build and launch enterprise‑grade SaaS/PaaS ...

Director, Software Manufacturing

San Jose, CA · On-site

$296K/yr

Position Overview Lumilens is seeking a Director of Software Manufacturing to lead the strategy, development, and execution of software systems that enable high-volume manufacturing of next ...

Position Overview Lumilens is seeking a Director of Software Manufacturing to lead the strategy, development, and execution of software systems that enable high‑volume manufacturing of ...

Director, Software Engineering

San Mateo, CA · On-site

$288K/yr

As the Director of Software Engineering, you are a hands-on, "rock star" Java developer and ... Feature Development & Architecture: You will build and launch enterprise-grade SaaS/PaaS ...

As the Director of Software Engineering, you are a hands‑on, "rock star" Java developer and ... Feature Development & Architecture: You will build and launch enterprise‑grade SaaS/PaaS ...

Showing results 21-40

Director Software Development information

See Fremont, CA salary details

$114.4K

$194.8K

$263.8K

How much do director software development jobs pay per year?

As of Aug 23, 2026, the average yearly pay for director software development in Fremont, CA is $194,828.00, according to ZipRecruiter salary data. Most workers in this role earn between $167,500.00 and $226,000.00 per year, depending on experience, location, and employer.

What is the difference between Director Software Development vs Software Engineering Manager?

AspectDirector Software DevelopmentSoftware Engineering Manager
ResponsibilitiesOversees multiple teams, strategic planning, and long-term goalsManages day-to-day team operations, project delivery, and technical guidance
FocusHigh-level leadership, cross-team coordination, and business alignmentTeam management, technical mentorship, and project execution
Required CredentialsBachelor’s or Master’s in CS or related, extensive experience, leadership skillsBachelor’s or Master’s in CS or related, strong technical background, leadership experience

The main difference is that the Director Software Development focuses on strategic leadership and overseeing multiple teams, while the Software Engineering Manager concentrates on managing individual teams and project execution. Both roles require technical expertise and leadership skills, but the director role involves broader organizational responsibilities.

What are the most commonly searched types of Software Development jobs in Fremont, CA?

The most popular types of Software Development jobs in Fremont, CA are:

What cities near Fremont, CA are hiring for Director Software Development jobs?

Cities near Fremont, CA with the most Director Software Development job openings:

Infographic showing various Director Software Development job openings in Fremont, CA as of August 2026, with employment types broken down into 1% As Needed, 83% Full Time, 13% Part Time, and 3% Contract. Highlights an 91% Physical, 3% Hybrid, and 6% Remote job distribution, with an average salary of $194,828 per year, or $93.7 per hour.

Senior Director, Software Development, Test Automation

Lila Sciences

San Francisco, CA • On-site

Full-time

Re-posted 15 days ago


Job description

Your Impact at LILA

The Role

We're hiring a Senior Director, Software Development, Test Automation Systems to architect and build Lila's test automation platform and quality engineering practice for our AI-powered scientific and lab automation products. Reporting to the VP of Engineering, you'll own the test automation system, CI/CD test infrastructure, AI-driven test tooling, and the eval discipline that hold the bar across our SDLC.

This is a builder-leader role. You will drive the quality vision, write requirements, make sharp build-vs-buy calls, drive execution, and build and lead a small (3-5 person) team that delivers leverage. The operating model is federated: you own the platform, standards, and metrics; engineering teams own test execution. You scale through tooling and influence.

As you scale into this role, you'll also stand up the QC framework for our lab automation system - the validation patterns, harnesses, and contracts that science operations teams will operate day-to-day. Data integrity and ALCOA+ compliance are foundational to everything you build.

What You'll Be Building

What You'll Do

Architect and ship the test automation platform

  • Design and build the test automation platform - frameworks, fixtures, golden datasets, test orchestration, and reporting - that the engineering org adopts by default
  • Set standards across unit, integration, contract, end-to-end, regression, performance, and chaos testing for backend services, the frontend monorepo, and data pipelines
  • Treat platform adoption, flake rate, and time-to-signal as first-class engineering metrics

Make build-vs-buy decisions with conviction

  • Own the buy/build/borrow strategy across test infrastructure, eval platforms, browser/device clouds, observability, and lab QC tooling
  • Justify every choice with TCO, signal quality, integration cost, and time-to-leverage - and revisit decisions as the org and tech landscape evolve
  • Bias toward leverage: buy commodity capabilities, build the differentiators (Lila-specific AI evals, lab QC, scientific data integrity)

Modernize CI/CD for fast, reliable signal

  • Own the test execution layer of CI/CD: parallelization, caching, hermetic environments, ephemeral preview envs, and affected-only test selection across our Nx monorepo/microservices.
  • Build retry, quarantine, and impact-analysis systems so signal stays sharp as the org scales
  • Drive change-failure rate, MTTR, Test effectiveness, pipeline efficiency, coverage, and PR-to-prod lead time as outcomes

Drive AI-driven test automation

  • Apply LLMs across the full test lifecycle: test generation from specs and PRs, self-healing UI tests, synthesis, visual regression with vision models, and AI-assisted failure triage
  • Validate every AI-generated test through evals - no LLM-authored test ships without proof it doesn't degrade signal
  • Establish the eval discipline for Lila's AI/agent stack: golden datasets, rubrics, regression suites, offline + online evaluation pipelines

Define and operate the quality metrics system

  • Define quality SLOs and adoption metrics by team and service: coverage, escape rate, MTTR, change-failure rate, eval pass rate, lab QC violation rate
  • Build dashboards that make quality visible from PR to executive review
  • Apply Google SRE practices to prioritize where investment goes

Mid-long term - Stand up the QC framework for lab automation

  • Design the validation framework, harnesses, and contracts that lab and Science Ops teams will operate
  • Embed ALCOA+ principles: data integrity, audit trails, lineage from sample instrument output
  • Partner with Research Ops on pre-flight, in-flight, and post-flight validation patterns for autonomous lab execution

Lead and coach across the engineering org

  • Build a 3-5 person team of test automation engineers focused on platform leverage, not on writing tests for other teams
  • Coach engineering teams on test design, quality investments, and adoption - make it cheaper to test well than to ship blind
  • Translate UX and customer issues into testable contracts and platform improvements

First 6-12 Month Outcomes

  • First 90 days: Establish baselines - flake rate, time-to-signal, change-failure rate, coverage, and current build-vs-buy footprint - and publish a quality scorecard with the first set of SLOs. Hire or onboard the initial 1-2 platform engineers.
  • By 6 months: Ship v1 of the test automation platform adopted by at least one flagship engineering team by default; land CI/CD test-execution improvements (parallelization, affected-only selection, flake quarantine) with measurable time-to-signal reduction. Stand up the eval discipline (golden datasets, rubrics, regression suites) for the AI/agent stack.
  • By 12 months: Drive default platform adoption across the engineering org; demonstrate AI-driven test automation in production with eval-gated rollout. Deliver the first operating version of the lab automation QC framework with ALCOA+ audit trails, validated end-to-end with Science Ops. Quality is visible from PR to executive review via live dashboards.

What You'll Need to Succeed

Required Qualifications

  • 10+ years in software engineering, with 5+ years leading test automation, quality engineering, or platform/SRE-adjacent functions
  • 3+ years managing engineers, including building or scaling a team
  • Strong software architect/engineer. You write designs your team wants to read and review. Python and/or Typescript hands on expertise is highly desirable.
  • Deep CI/CD expertise. GitHub Actions or equivalent at scale, monorepo build/test orchestration (Nx, Turborepo, or Bazel), test parallelization and caching, hermetic environments, ephemeral preview envs, flake quarantine, and test impact analysis
  • Demonstrated build-vs-buy judgment. You've made and defended decisions on test infra, eval platforms, browser/device clouds, and observability - and can articulate the TCO and signal trade-offs that drove them
  • Hands-on AI-driven test automation experience. Using LLMs to generate, maintain, or triage tests in production, with rigorous eval validation. Fluency with eval frameworks
  • Track record of standing up a test automation platform that engineering teams adopted - not one bolted on
  • Working knowledge of Google's SRE practices and a point of view on when they apply to pre-production quality
  • Metrics-driven leader who drives outcomes through platform leverage and influence, not gatekeeping
  • Customer- and UX-first instincts: treats test automation as a vehicle for user experience, not a cost center

Bonus Points For

Nice to Have

  • Experience in GxP-regulated environments or scientific data integrity programs
  • Experience with lab automation, LIMS, or other instrument-driven systems
  • Multi-tenant SaaS quality at scale
  • Exposure to event-driven systems, agent orchestration frameworks, or MCP
  • Performance/load testing or chaos engineering background