Lead Software Engineer, Frontend

• Build modeling interfaces where users define, configure, and compose complex system models

• Develop data visualizations and analysis tools that help users explore simulation results across thousands of scenarios

• Contribute to workflow and job management UIs that let users schedule and monitor simulation runs

• Extend and maintain our design system and component libraries

Do you have experience in UI implementation?, Do you have a Bachelor's degree?, * Bachelor's degree in computer science or equivalent experience

• 3+ years of professional experience in software engineering

• Proficiency with React and TypeScript

• Experience with frontend automated testing

• Experience contributing to component libraries or design systems

Pulled from the full job description

• 401(k) 4% Match

• Parental leave

• Health insurance

• 401(k) matching

• Unlimited paid time off

• Flexible schedule, * Equity

• Unlimited PTO

• 401(k) with 4% match

• 100% premium payment for medical insurance

• Parental Leave

• Flexible work schedule with core hours

• Company provided lunches 3 days a week

• Industry-leading career development opportunities

Sedaro is a simulation platform company. Customers use our cloud platform to simulate satellite constellations and connected fleets, enabling the design and operation of systems at unprecedented scale. Enabling customers to playback and visualize multiple constellations, drill down into individual spacecraft sub-systems, and then compare thousands of variations of a simulation is a significant challenge, all built on Cesium, React, and TypeScript. We're an early-stage company with serious traction, partnering with the Space Force and Shield AI to deliver next-gen systems, and we're growing the team to match. Who You Are * You build power tools for power users. You're drawn to interfaces where depth and efficiency matter more than onboarding simplicity. * You're energized by novel problems where there isn't a ready-made answer. * You'd rather ship and learn than polish in isolation. You're comfortable with scrappy prototypes and iterating in the open. * You focus on impact. You care more about what your work enables than about how it was tracked.