Senior Frontend Software Engineer, True Anomaly

• You do not need to have experience building space ground systems or experience in aerospace
• 7+ years of software development experience
• Expert-level command of HTML/CSS and modern TypeScript/JavaScript, including nuanced understanding of performance implications and browser internals
• Deep expertise in modern React, including advanced patterns (compound components, render props, custom hooks architecture), state management strategies, and performance optimization techniques
• Strong testing philosophy and hands-on experience with Vitest, React Testing Library, and end-to-end testing frameworks, you understand what to test, not just how
• Proven experience designing and evolving component libraries, design systems, and CSS architecture at scale
• Fluency with gRPC, RESTful and WebSocket based services, including debugging integration issues and contributing to API design discussions
• Comfort operating across the stack when needed, you can read backend code, understand infrastructure constraints, and collaborate effectively with backend engineers
• Track record of working in Git-based workflows with high standards for commit hygiene, PR quality, and collaborative review processes
• U.S. Citizen and eligible for DoD Secret or TS/SCI clearance

Desirable

• True Anomaly is seeking a dedicated Front End Software Engineer to contribute to the continuing evolution of our complex spacecraft modeling and simulation software
• This is a high-autonomy, high-accountability role
• You'll own entire feature domains from conception to production, drive architectural decisions that affect the entire frontend surface, 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, 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’ll have ownership of challenging, greenfield problems and a chance to fundamentally impact the outcome of future conflict (and the future of the company)
• Own and deliver complex 2D and 3D web-based frontend features end-to-end, from technical design through production deployment and iteration
• Drive architectural direction for frontend systems, establishing patterns and conventions that scale across the team and codebase
• Proactively identify and address technical debt, performance bottlenecks, and opportunities for refactoring
• Set the quality bar through rigorous code review, championing testing practices, 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
• Collaborate as a technical partner with product, design, backend engineers, QA, space operators, and astrodynamics algorithm engineers—contributing to system-wide architectural decisions
• Ship efficiently and iteratively, breaking complex 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 works but violates codebase conventions—you don't just approve it; you take the time to explain the patterns and why they matter
• You notice a component is being copy-pasted across the codebase—you propose and implement an abstraction, then document when and how to use it
• You're assigned a feature and the requirements are ambiguous—you proactively clarify with product and design, propose a technical approach, and share it with the team before diving into implementation
• You see downtime as an opportunity, not a break—you're the kind of engineer who notices the flaky test everyone's been ignoring and decides to finally fix it
• You disagree with an architectural decision—you articulate your concerns constructively, propose alternatives with tradeoffs, and commit fully once a decision is made
• You're thinking beyond your current ticket—you're aware of how your work fits into the broader product roadmap and technical direction, and you surface risks or opportunities early
• The physical demands of the job, including bending, sitting, lifting and driving

• This position will be open until it is successfully filled