Sr. Software Engineer, Full Stack Security Clearance

Position: Sr. Software Engineer, Full Stack with Security Clearance
Space is a war fighting domain. True Anomaly seeks those with the talent and ambition to build the technology that secures it. OUR MISSION True Anomaly delivers decisive capabilities for space superiority. We build autonomous spacecraft, advanced payloads, mission software, and space-based interceptors - enabling the U.S. and its Allies to secure the space environment and counter threats from the ultimate high ground.

OUR VALUES
* Be the offset. We create asymmetric advantages with creativity and ingenuity.
* What would it take? We challenge assumptions to deliver ambitious results.
* It's the people. Our team is our competitive advantage and we are better together. YOUR MISSION Software is the central nervous system for True Anomaly's engineering and product thesis. Software bridges the gap between military objectives, theoretical astrodynamics and the human and autonomous control of spacecraft and ground systems in time and space. True Anomaly is seeking a dedicated Senior Full Stack Software Engineer to drive feature development and architectural decisions across our React/Type Script frontend and Elixir backend, shaping the evolution of our spacecraft modeling, simulation, and ground control software.

This is a high-autonomy, high-accountability role. You'll own entire feature domains from conception to production across the full stack, drive architectural decisions that affect both the frontend experience and backend infrastructure, and set the standard for code quality that junior and mid-level engineers will follow. You won't wait to be assigned work; you'll identify what needs to be done, propose solutions, and drive them to completion.

When you see tech debt on either side of the stack, you'll flag it, scope it, and champion the work to address it. When patterns aren't serving us, you'll propose better ones and lead their adoption. You do not need to have experience building space ground systems or experience in aerospace. You'll have ownership of challenging, greenfield problems and a chance to fundamentally impact the outcome of future conflict (and the future of the company), all while enjoying world-class benefits including platinum healthcare, flexible work hours/location, highly competitive compensation and a generous stock options package.

RESPONSIBILITIES
* Own and deliver complex features end-to-end across the full stack, from 2D and 3D web-based frontend interfaces through distributed Elixir backend services, from technical design through production deployment and iteration
* Drive architectural direction across frontend and backend systems, establishing patterns and conventions that scale across the team and codebase, with particular attention to the boundaries and contracts between layers
* Proactively identify and address technical debt, performance bottlenecks, and reliability risks across the stack
* Set the quality bar through rigorous code review, championing testing practices in both React and Elixir, and writing code that serves as a reference implementation for the team
* Mentor and elevate junior and mid-level engineers through pairing, design discussions, and constructive code review that teaches, not just approves, helping engineers grow their skills on whichever side of the stack they're less experienced in
* Collaborate as a technical partner with product, design, QA, space operators, and astrodynamics algorithm engineers, contributing to system-wide architectural decisions with a perspective that spans the full stack
* Ship efficiently and iteratively, breaking complex cross-stack work into well-scoped increments while maintaining a bias toward completion over perfection
* Document decisions and patterns, ensuring the team's collective knowledge grows and onboarding becomes easier over time WHAT SUCCESS LOOKS LIKE IN THIS ROLE
* You see a PR from a junior engineer that implements a feature on the frontend but introduces an inefficient API call pattern; you don't just fix the frontend; you suggest a backend change that solves the problem at its root and explain the tradeoffs
* You notice the same data transformation happening in both the Elixir backend and…