Skip to main content

1X

Software Engineer - Product

San Carlos, CA$200k–$280kfulltimemidAdded 1 month ago

About this role

1X is hiring a full-stack Software Engineer to build the cloud platform that operates their humanoid robot fleet. You'll own features across Go backends, TypeScript/React frontends, and Kubernetes infrastructure, directly supporting robots deployed in real homes at scale.

What you'll do

  • Develop and maintain Go backend services and TypeScript/React frontends for the robot fleet operations platform
  • Extend the robot cloud protocol and operator tooling to support growing hardware capabilities
  • Improve system reliability and observability through instrumentation, logging, and incident response
  • Build internal and customer-facing platforms for fleet management, logistics, and service operations
  • Own features end-to-end across the full stack without handoffs, from design to production deployment
  • Manage Kubernetes deployments, CI/CD pipelines, and AWS infrastructure supporting live robot operations

What they're looking for

  • Go backend development with concurrency and WebSockets
  • TypeScript and React with production experience in modern frameworks
  • Kubernetes and AWS (ECS, EKS, RDS, S3)
  • Database design, migrations, and query optimization
  • Real-time system architecture and observability practices
  • OpenAPI/API-first development
  • AI/LLM application development (preferred)
  • WebRTC or real-time video infrastructure (preferred)
Apply with Autofill

Opens the application — the Jobs AI extension fills it for you. Set up autofill

Opens the official application on the employer’s site. No login required.

1X

1X builds humanoid robots for home use, with its NEO robot requiring sophisticated hardware, firmware, and cloud systems. The company is hiring across compliance testing, audio systems, embedded firmware, cloud platform development, and supplier engineering to bring its robots to production and scale.

View all jobs at 1X

Likely interview questions

  • Walk us through a full-stack feature you've shipped end-to-end in Go and TypeScript/React. How did you handle the handoff between backend and frontend, and what went wrong?
  • Tell us about your experience with WebSockets at scale. How have you handled reconnection logic, backpressure, or auth challenges in production?