Sr. Software Engineer

*Native/Bilingual English is required for this role (read/written/spoken) Monthly salary: $5,500 - $6,000 USD Along with our partner, we are looking for a Senior Software Engineer. The Mision Take validated engineering to software a customer will trust running on hardware worth tens of millions of dollars. The question every buyer asks, in some form, is what happens if the software misbehaves. Every answer to that question has to be engineered in rather than argued. That means thinking about failure first. What the safe default is when the software loses visibility into what it is managing. What happens if the process stops unexpectedly. How the system degrades rather than breaks. How an operator can reconstruct, from logs alone, exactly what the software did and why. How it gets installed, upgraded, and rolled back inside a facility with real change-control procedures. This is safety engineering applied to infrastructure software. If that framing is energizing, this is a good role. If it reads as overhead that slows down feature work, it is not. Required: 7+ years of experience shipping and personally owning production software that other people depended on. Deep production Python . Long-running services and daemons, concurrency, subprocess and signal handling, systemd, packaging and distribution, structured logging. This is a systems engineering role, not a data science role. A track record of taking software from prototype to production . Not maintaining a mature system someone else hardened, but doing the hardening: test coverage, failure-mode analysis, observability, safe defaults, graceful degradation, operational documentation. Strong Linux fundamentals. Process and signal semantics, systemd, resource control, kernel and driver-layer troubleshooting. Productive on a remote bare-metal machine over Secure Shell with no graphical interface. Experience with software that operates on physical systems. Device-level software, drivers, embedded systems, telemetry, industrial or process control, robotics, or data center and accelerator infrastructure. Any of these count. Purely web or software-as-a-service backgrounds are not a fit regardless of seniority, because the consequences of failure are different in kind. Written English strong enough to co-author a technical document intended for a customer's engineering team. At least six hours of daily overlap with United States Mountain Time (Phoenix, UTC-7). Strong advantages: Rust . A compact performance-sensitive component is written in Rust and needs an owner. Real-time or latency-sensitive systems, where a missed deadline is a correctness failure rather than a performance issue. A safety-critical background — industrial control, medical device, automotive, or aerospace software — where failure has physical consequences and that discipline was formally practiced. Data center or accelerator infrastructure experience. Packaging and deployment into environments you do not control : installers, agents, restricted or air-gapped networks, customer change-control processes. Production on-call ownership of a system with a meaningful blast radius. Go , and Kubernetes-based deployment tooling. Eligibility to obtain a United States visitor visa for occasional travel to customer sites and industry conferences. Preferred, not required. Not required: Machine learning modeling or research. Data science. Front-end development. An electrical engineering degree. Prior energy sector experience. First 90 days: Own the production service end to end and run it independently. Produce a documented failure-mode analysis, close the gaps it identifies, and cover them with regression tests. Build a packaging and installation path a customer's operations team can execute, review, and roll back. Bring observability to the point where an operator can reconstruct everything the software did, and why, from logs alone. How this team works: Small, senior, and direct. No ticket queue and no product management layer. Daily contact with the founder and full visibility into the system. Evidence discipline is strict and unusual. Every result this company reports traces to a reproducible record carrying the conditions under which it was measured. Nothing is stated externally that cannot be reproduced on demand. Our customers and counterparties require that standard, and the person in this role has to want to work that way too. There is occasional evening work during validation campaigns, because the hardware time involved is expensive and does not wait for business hours. It is not a nightly expectation. All work is covered by a confidentiality and intellectual property assignment agreement executed directly wit AIONTRACKS before the first day. *Please note our partner is only looking for full-time dedicated team members who are eager to fully integrate within their team. A fully remote position with a structured schedule that supports work-life balance. #J-18808-Ljbffr Tecla