Mechanical Engineer III
Job description
About the role
The engineer supports high-stakes programs that push technical frontiers and protect critical assets.
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
Complex testing capabilities are established through component and subsystem integration, data acquisition, statistical analysis, and measurement instrument operation to validate system performance.
Communication adaptability is demonstrated across technical presentations, detailed reports, and user documentation to serve diverse audiences and manage challenging inquiries.
Technical reports and user manuals are produced with precision to convey solutions, constraints, and operational guidance clearly to stakeholders.
Performance is evaluated through structural, dynamic, and thermal analysis, enabling optimization of hot gas valves, thrusters, and control systems for reliability.
Trade studies are conducted to compare alternatives, analyze options, and deliver data-driven design recommendations that align with program objectives.
Detailed 2D and 3D designs are created using CAD tools, and complex assemblies and technical drawings are produced following strict tolerances and geometric dimensioning standards.
Basic simulations are performed using CFD software, with results interpreted and analyzed to apply engineering judgment and refine system behavior predictions.
Structural and dynamic models are developed and assessed to evaluate performance under varied conditions, informing design decisions and verification activities.
Results from analysis and simulation are interpreted and validated to optimize designs, ensure compliance, and guide informed decision-making.
Program plans are developed under systems engineering guidance, aligning with acquisition life cycles and coordinating technical and risk activities.
Requirements analysis, risk management, and strategy development are conducted to ensure reliable execution and mitigation of technical and program risks.
Small teams are led with direction, and operations research principles support complex procurement, vendor evaluation, and contract management practices.
Procurement strategies, supplier performance analysis, and contract management practices are implemented to control cost, schedule, and technical outcomes.
Requirements
Four (4) to seven (7) years of mechanical engineering experience.
Bachelor of Science in mechanical engineering, aerospace engineering, or other relevant engineering discipline from an accredited university; equivalent experience may substitute for degree.
U.S. Security Clearance at the appropriate level obtainable through U.S. Citizenship.
Ability to travel approximately 10% of the time.
Practical notes
citizenship to meet ITAR/EAR export control regulations and security eligibility. Frequent interaction with defense and national security programs is expected. 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.
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.