Why This Job is Featured on The SaaS Jobs
Parallel Domain’s platform work sits squarely in a modern SaaS pattern: a self-serve, customer-facing product layer backed by APIs, data pipelines, and operationally critical services. The remit spans web applications, centralized backend services, and a simulation-as-a-service offering, which is a useful example of SaaS expanding beyond traditional business software into technical, usage-driven products.
For a senior engineer building a long-term SaaS career, this kind of role strengthens the skills that tend to compound across companies: designing external-facing APIs that other teams and customers depend on, shaping data models that survive product iteration, and owning reliability after release. The emphasis on observability, incident response, and deployment in containerized environments maps closely to how SaaS products are run at scale, where operational maturity is part of the product experience.
This position fits engineers who prefer end-to-end accountability, moving from requirements to design to production support without handing off the hard parts. It also suits those who enjoy working across product and SRE interfaces, and who want their technical decisions to show up directly in customer workflows through dashboards, integrations, and service behavior.
The section above is editorial commentary from The SaaS Jobs, provided to help SaaS professionals understand the role in a broader industry context.
Job Description
About the Role
Parallel Domain builds synthetic data and simulation platforms for autonomous vehicle and robotics teams. The Product Engineering team owns the customer-facing product and service layer: the self-serve platform for productizing ML reconstruction pipelines, our high-fidelity simulation-as-a-service product, the web applications and dashboards customers interact with directly, and the centralized backend services and APIs that connect them.
We're hiring a Senior Software Engineer to own delivery across this stack. You'll design and build features and services end to end - from API design through to production - and take real ownership of the reliability and quality of what you ship. Our stack spans Python backend services, RESTful and gRPC APIs, relational databases, React frontends, and data pipelines. Engineers who thrive here are comfortable across multiple layers of the stack, move well from a requirement to a design, and take operational ownership of what they build.
\n
Responsibilities
-
Expand and maintain customer-facing services and APIs. You'll build and improve the services customers interact with directly: interactive services and async processing pipelines, web app integrations, and APIs that connect them.
-
Design and implement APIs and data models. You'll architect and implement RESTful API endpoints that cleanly separate data from business logic, are well-documented, and are built to the standards customers and field engineers depend on.
-
Collaborate across product, SRE, and field engineering. You collaborate with product managers and technical stakeholders to understand requirements and clarify interface design. You partner with SRE on deployment and operational concerns.
-
Debug production issues and improve service reliability. You'll contribute to observability, alerting, and the ongoing health of the services your team operates. You participate in incident response and drive root-cause improvements.
-
Uphold and contribute to engineering standards. You follow and help shape team standards around testing, code quality, API documentation, dependency management, and service structure. You leave the codebase better than you found it.
What You Need to Succeed
-
API design experience. You're comfortable designing RESTful APIs: resource modeling, separation of data and business logic, authentication, versioning, and documentation. You understand what makes an external-facing API maintainable.
-
Production service ownership. You've owned services in production: monitoring, alerting, on-call response, and the follow-through after an incident.
-
Requirement gathering and collaboration. You can work with product and customer-facing stakeholders to clarify requirements, surface interface design questions early, and produce concrete designs before implementation starts.
Skills
-
Languages and Frameworks. Python, FastAPI, Flask, PostgreSQL, React, TypeScript
-
Systems & Infrastructure. AWS (S3, RDS, Lambda, EKS), Docker, Kubernetes, GitHub Actions, Jenkins, gRPC, Proto
-
Domain Experience. RESTful API design and documentation. Production service ownership. Data pipeline operation. Observability tooling (Prometheus, Grafana). Experience in simulation, ML pipelines, or autonomous systems is an advantage.
Bonus Points
-
Experience with event-driven systems and message brokers (e.g., Redis, SQS, RabbitMQ)
-
Experience with workflow orchestration tools (e.g., Apache Airflow)
-
Familiarity with load balancers, HTTP proxies, or service mesh patterns
-
Experience with ORMs such as SQLAlchemy
-
Background supporting production monitoring databases and alerting infrastructure
-
Primary ownership of a production React web application, including architecture, state management, and deployment
-
Experience with frontend testing, build tooling, or performance optimization
What Makes a Great CandidateYou take ownership of what you build and stay engaged with it after it ships. You move well from a stakeholder conversation to a design doc to working code. You follow best practices not because you're told to but because you understand why they matter. You're invested in outcomes - you think past the spec to whether what you're building is actually the right solution, you push back when it isn't, and you make the systems and people around you more effective as a result.
\n
$155,000 - $175,000 a year
\n
