Senior Propulsion Test Engineer
Job description
Senior Propulsion Test Engineer at Astro Mechanica.
About the role
This role defines and executes test infrastructure for propulsion hardware and integrated systems. The position advances test capability and reliability for aerospace development. The work supports government programs that close aircraft performance gaps using dual-use propulsion technology.
Software engineers turn product ideas into working code. Engineers work in small teams, review each other's work, and ship in small batches. Most teams follow agile practices such as sprints and daily standups. Engineers also write tests, fix bugs, and improve performance. The field values clear communication as much as technical skill. Engineers spend part of every week on planning, code review, and debugging, not just writing new code. The ability to explain a technical decision in plain words separates strong engineers from the rest.
Key facts
What you'll do
Maintain test facility operations, perform troubleshooting, and uphold site cleanliness so that tests run reliably. Analyze data to verify equipment activation, calibration, and operation against expected behavior. Diagnose stand problems efficiently and execute corrective actions to restore test capability. Harness assembly skills, such as crimping and soldering terminals, cable lacing, and troubleshooting, to prepare test interfaces. Operate manual machine shop equipment, including drills, cutting tools, mills, and lathes, to support test hardware fabrication. Embody the test-like-you-fly philosophy in all test activities.
Requirements
The posting states a bachelor's degree requirement. Bring 5+ years of hands-on experience with fluidic and mechanical systems and test operations. Have experience with hazardous environments, including flammables, high voltage, and pressurized systems, and apply safety mitigations. Demonstrate knowledge of fluid systems hardware and instrumentation, such as pressure, temperature, load cells, relays, solenoids, and pneumatics. Show familiarity with data acquisition and control systems, PLC hardware, computer networking, and software interfaces. Use proficiency with PLC and data processing software, including Python, MATLAB, and LabVIEW. Take initiative for continuous improvement beyond assigned tasks. Adapt to a fast-paced environment while maintaining flexibility. Attend to detail and maintain a high level of quality in all work.
Practical notes
Typical interview steps
Hiring for engineering roles usually starts with a recruiter screen, followed by one or two technical rounds. Candidates often solve a coding problem, discuss past projects, and answer system design questions. Some loops include a take-home task. Final rounds typically cover team fit and give candidates a chance to ask questions. Interviewers look for how you break down an unfamiliar problem, not just whether you reach the answer. Practicing a few problems aloud and reviewing your own past projects are the best preparation.
Good to know
The role focuses on propulsion testing and hardware development in an aerospace context. The team uses tools such as data acquisition systems, PLC hardware, and programming environments like Python, MATLAB, and LabVIEW. The position emphasizes safety in hazardous environments and strict quality standards for test operations.
Questions to ask
Worth asking in any interview: how the team measures success, who the role works with daily, what the onboarding looks like, and what the company is trying to achieve this year. Asking what past hires did well is a strong final question. Keep the list short and pick the questions that matter most to you.
Career growth
Engineering careers usually progress from individual contributor to senior, staff, and principal levels. Some engineers move into management and lead teams of five to twenty people. Others stay on the technical track. Growth follows demonstrated impact, not tenure alone. A typical engineering ladder has clear levels with defined expectations for scope, quality, and mentorship. Moving up usually requires owning outcomes end to end rather than completing assigned tickets.