> Markdown version of [/jobs/ext/4152315-principal-operations-engineer-application-software](https://www.wearedevelopers.com/jobs/ext/4152315-principal-operations-engineer-application-software). Every page supports `.md` or `Accept: text/markdown`. Links point to the HTML versions so they work for humans too. Agent guide: [/agents.md](https://www.wearedevelopers.com/agents.md).

---

# Principal Operations Engineer (Application Software)

- **Company:** Space Exploration Technologies Corp.
- **Location:** Hawthorne, CA, United States
- **Experience:** Expert
- **Salary:** $180,000.0 - $275,000.0
- **Contract:** Permanent contract
- **Skills:** Microsoft Excel, Artificial Intelligence, Software Applications, Python (Programming Language), SQL Databases, Systems Integration, Graphics Processing Unit (GPU), Information Technology, Network Server
- **Published:** October 12, 2026
- **Apply:** https://www.indeed.com/viewjob?jk=0903f7d8b8a100ff

## About the Role

* Bachelor's degree in operations, engineering, computer science, mathematics, physics, or a related technical field
 * 7+ years of experience or education in management science and engineering, operations engineering, operations research, industrial engineering, or equivalent quantitative operations work
 * 5+ years of experience in operations, strategy, program management, or technical leadership in a high-rate engineering or software environment, * Master's degree in management science & engineering, operations research, industrial engineering, or similar
 * Track record of owning or heavily contributing to an AOP / annual budget (headcount + opex + capex) for a technical org
 * Experience forecasting and standing up compute capacity: servers, GPUs, storage, server racks, power/cooling, hardware BOM, and vendor lead times
 * Experience standing up operations at new sites and/or running M&A diligence and post-merger integration for software, IT, or technical teams
 * Proven ability to take an undefined, cross-functional problem and produce a durable strategy - not just a short-term workaround
 * Ability to contribute directly to software (scripting, services, internal tools, integrations) and/or hardware builds (racks, servers, networking, site bring-up) rather than only coordinating them
 * Comfort with ambiguous executive problems; strong quantitative chops (SQL, Excel, Python, AI) without over-instrumenting; can write a one-pager leadership will actually read
 * Ability to influence without authority across engineering, recruiting, finance, IT, facilities, and site leadership
 * Bias for action; willing to walk a rack row, a factory floor, or a finance deck when that is what the problem requires

ADDITIONAL REQUIREMENTS:

 * Must be willing to work extended hours and weekends as needed
 * Must be willing to travel frequently to SpaceX sites, * To conform to U.S. Government export regulations, applicant must be a (i) U.S. citizen or national, (ii) U.S. lawful, permanent resident (aka green card holder), (iii) Refugee under 8 U.S.C. § 1157, or (iv) Asylee under 8 U.S.C. § 1158, or be eligible to obtain the required authorizations from the U.S. Department of State. Learn more about the ITAR here.

## Description

* Run the Application Software (ASW) operating cadence with the director and leadership team: weekly/monthly rhythm, decision log, and the staff plan that matches company demand to teams
 * Own the ASW AOP (headcount, opex, capex, vendors) from bottoms-up inputs through Finance review, in-year change control, and AOP-vs-actuals
 * Own the M&A playbook and execute integrations: diligence on people, software, vendors, and data; day-1 / 30 / 100 cutover; keep vs. rewrite vs. retire; where acquired teams land
 * Own site activation for ASW: coverage model, local intake/support, hiring, a go-live plan aligned to first hardware, first shift, or first customer
 * Own compute and hardware capacity: CPU/GPU/storage forecast; server-rack layout, power, cooling, and floor space with IT/facilities
 * Redesign intake, prioritization, and SLAs so work enters ASW through one process - not a different path per team, site, or acquired org
 * Tackle nebulous, multi-org problems with no playbook yet; pull a future-looking ASW growth strategy (org, sites, platforms, compute) out of ambiguity and drive it to a decision
 * Get hands-on where it unblocks the plan: write software, land an integration, rack and cable hardware, bring up a server row, or join a site/hardware build until it is actually live
 * Lead a team of 2-3 engineers/analysts; hold a short metric set and use it to change behavior