> Markdown version of [/jobs/ext/2863827-software-engineer-asw-launch-ops](https://www.wearedevelopers.com/jobs/ext/2863827-software-engineer-asw-launch-ops). Every page supports `.md` or `Accept: text/markdown`. Links point to the HTML versions so they work for humans too. Agent guide: [/agents.md](https://www.wearedevelopers.com/agents.md). --- # Software Engineer, ASW Launch Ops - **Company:** Zipline - **Location:** South San Francisco, CA, United States (Remote available) - **Experience:** Expert - **Contract:** Permanent contract - **Skills:** Geographic Information Systems, Application Programming Interfaces (APIs), Artificial Intelligence, Amazon Web Services, Architectural Patterns, Automation of Tests, Code Review, Continuous Integration, Software Debugging, Document Management Systems, Distributed Systems, Python (Programming Language), PostgreSQL, Software Engineering, Systems Integration, Enterprise Software Applications, ReactJS, Grafana, Backend, Production Code, Apache Kafka, Operational Systems, Front End Software Development, Restful APIs, Grpc, Golang - **Published:** September 12, 2026 - **Apply:** https://startup.jobs/senior-software-engineer-asw-launch-ops-zipline-10027152 ## About the Role * Senior individual contribution. At least 5 years of professional experience developing and maintaining full-stack production systems at scale, or demonstrated equivalent technical mastery. * Product-minded engineering. You understand user needs, identify root causes, and design pragmatic solutions that balance business value, usability, technical simplicity, and long-term maintainability. * Systems perspective. You can break down ambiguous operational problems, collaborate with stakeholders to define the right solution, and deliver software that improves real-world processes. * Strong technical fundamentals. You design maintainable systems, model data thoughtfully, create robust APIs, and make sound tradeoffs across frontend applications, backend services, distributed systems, and infrastructure. * Complex workflow experience. You have modeled long-running workflows, external dependencies, physical assets, and complex state transitions with strong auditability, observability, and failure recovery. * Integration experience. You have built reliable integrations between internal services and external or enterprise systems. Experience with ERP, GIS, document management, construction, permitting, or asset management systems is valuable but not required. * Modern technology mindset. You are comfortable learning and working across technologies such as Python, Go, PostgreSQL, React, Kafka, gRPC, AWS, Grafana, and Honeycomb. We value engineers who learn new tools quickly over experience with every specific technology. * Effective use of AI. You use AI thoughtfully throughout the development lifecycle-including design, implementation, testing, debugging, and code review-while maintaining strong engineering judgment and quality. * Operational excellence. You define meaningful service-health metrics and reliability goals, create actionable runbooks, participate in on-call rotations, and drive improvements through incident reviews. * Quantifiable results. You have shipped high-impact capabilities that reduce manual intervention, shorten cycle times, increase predictability, improve throughput, or strengthen reliability-and can demonstrate the results with concrete metrics. * Cross-functional leadership. You communicate clearly under ambiguity, prioritize decisively, and influence stakeholders across engineering and operational organizations without relying on formal authority. * Owner's mindset. You balance speed with correctness and understand the real operational consequences of software used to deploy physical infrastructure and support safety-critical operations. ## Description * Drive core product domains. Serve as a technical owner for critical capabilities across site acquisition, permitting, infrastructure design, construction execution, deployment tracking, and launch readiness-ensuring their long-term technical health and strategic direction. * Deliver measurable impact. Reduce manual coordination, shorten site-launch timelines, improve launch-date predictability, and give cross-functional leaders clear visibility into execution, dependencies, and risk. * Lead technical design. Define the APIs, data models, service boundaries, and architectural patterns that power the platform, with a focus on maintainability, auditability, observability, and pragmatic evolution. * Build durable operational workflows. Translate complex real-world processes into software that supports long-running workflows, government and vendor interactions, physical assets, documents and permits, approvals, dependencies, state transitions, and exception handling. * Create a unified operational source of truth. Build resilient integrations across ERP, GIS, document management, permitting, construction and project management, asset management, and internal operational systems. * Design for the people doing the work. Partner directly with users to turn fragmented processes and data into intuitive tools for planning and execution. Prototype workflows, validate them in real operating environments, and drive adoption. * Own production excellence. Build and operate business-critical services with meaningful health metrics, SLOs, observability, runbooks, and recovery mechanisms. Participate in on-call, lead incident response when needed, and improve systems through thoughtful postmortems. * Remain deeply hands-on. Ship production code, review critical changes, troubleshoot complex system behavior, and follow major capabilities from discovery through deployment and operation. * Lead through influence. Create clarity in ambiguous problem spaces, identify systemic risks and cross-team dependencies, and drive alignment across technical and operational stakeholders. * Elevate the team. Mentor peers, raise engineering standards, and strengthen practices in system design, automated testing, CI/CD, operational reliability, and pragmatic delivery., This role can be based in South San Francisco or remotely within the United States. Regular travel is expected so that you can work closely with stakeholders, understand operational challenges firsthand, and build software grounded in real-world workflows. Travel may include visits to Zipline headquarters, operating sites, and new-market launches. Remote team members should expect more frequent travel-typically a few days at a time, potentially once per month. ## Related Videos - [Exploring the Power of gRPC-Gateway for Writing RESTful Services](https://www.wearedevelopers.com/videos/2072-exploring-the-power-of-grpc-gateway-for-writing-restful-services) - [Go with the Flow: Stop the Leaks Before Your Memory's a Waterfall!](https://www.wearedevelopers.com/videos/100073-go-with-the-flow-stop-the-leaks-before-your-memory-s-a-waterfall) - [Developing the Backend with Stefan Lingler, CTO at Shpock](https://www.wearedevelopers.com/videos/100360-developing-the-backend-with-stefan-lingler-cto-at-shpock) - [Remote Driving on Plant Grounds with State-of-the-Art Cloud Technologies](https://www.wearedevelopers.com/videos/251-remote-driving-on-plant-grounds-with-state-of-the-art-cloud-technologies) - [Boosting OpenSearch Performance: gRPC Search in Action](https://www.wearedevelopers.com/videos/1964-boosting-opensearch-performance-grpc-search-in-action) - [Throwing off the burdens of scale in engineering](https://www.wearedevelopers.com/videos/608-throwing-off-the-burdens-of-scale-in-engineering) ## Related Articles - [Highest Paying Tech Companies for Developers](https://www.wearedevelopers.com/magazine/220-highest-paying-tech-companies-for-developers) - [What is Software Engineering?](https://www.wearedevelopers.com/magazine/289-what-is-software-engineering) - [Top Characteristics of a Software Engineer](https://www.wearedevelopers.com/magazine/166-top-characteristics-of-a-software-engineer) - [How We Built a Worry-Free System That Runs for 10+ Years – And What We’d Do Again](https://www.wearedevelopers.com/magazine/751-how-we-built-a-worry-free-system-that-runs-for-10-years-and-what-we-d-do-again) - [Is Software Engineering Over-Saturated?](https://www.wearedevelopers.com/magazine/418-is-software-engineering-over-saturated) - [How to Answer the Interview Question: “Why Do You Want to Be a Software Engineer?”](https://www.wearedevelopers.com/magazine/392-how-to-answer-the-interview-question-why-do-you-want-to-be-a-software-engineer)