Software Engineer, Engineering Applications
Job description
Software Engineer, Engineering Applications at Astro Mechanica.
About the role
This role builds and maintains core analysis tools and databases that enable multidisciplinary design for aerospace hardware. Success depends on translating physics into scalable, reliable code.
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
General numerical templates for composite plate buckling, classical laminate theory, and composite failure theory are implemented in Python to accelerate design iteration. Custom loads analysis tools execute aeroelastic solution sequences to streamline simulation workflows and improve turnaround time. Reusable, well-documented libraries are built to enable multidisciplinary design optimization workflows across aircraft disciplines. Analysis methods are converted into production-quality software through close partnership with mechanical and aerospace engineers. Internal engineering toolchains performance, reliability, and automation are enhanced to reduce manual effort and accelerate decision-making. Flight dynamics simulation tools are developed, and interfaces are designed to help analysts in GNC, loads, and flight dynamics execute analyses efficiently.
Requirements
Software engineers bring 5+ years of experience in software engineering or a related development field to manage complex engineering workflows. Engineers demonstrate substantial experience in Python while building engineering or scientific computing tools, and familiarity with Fortran is a plus. A background or familiarity in mechanical engineering, aerospace engineering, or a related technical discipline is required to understand analysis context. Professionals show ambition to operate effectively in a fast-paced, deadline-driven environment.
Practical notes
Work is primarily office-based, with an expectation of five days per week onsite to sustain close collaboration and team culture. Astro Mechanica is an equal opportunity employer that recruits a diverse workforce. 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
Python is a commonly used language for engineering software tools in this field. Fortran often appears in performance-critical simulations where computational efficiency matters. Teams typically work closely across mechanical, aerospace, and systems engineering functions. General engineering software practices emphasize performance, reliability, and clear documentation for critical analysis workflows.
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.