Transmission Planning Software Engineer
Pitch Aeronautics Inc. · Boise, ID
—
Jul 28, 2026
Boise, ID
Jul 29, 2026
What this job asks for AI summary
This role sits at the intersection of transmission planning expertise and software engineering, supporting a Dynamic Line Rating forecast product used in interconnection studies and power flow workflows. The primary focus is leading and owning power flow studies (DC/AC, N-1/N-2 contingency, PTDF/LODF, generator interconnection capacity), contributing Python and Julia/Sienna code, and engaging directly with RTO/ISO planners and utilities. Strongest candidates will have deep transmission planning backgrounds and either existing coding skills or a clear willingness to develop them.
Senior level · 4+ years · Remote
“or” means any one of them counts — you don't need all of them.
We read this from the posting text with AI. Skim the description below before ruling yourself out.
How this req sits in the market our data
Roughly 177,000 people nationally plausibly meet what this posting asks for (software developers). range 106,000–265,500
Applicant volume Heavy — This req sits in a large pool with little in its requirements to thin it, and auto-apply tools fire at everything in the occupation. Applying early and leading with the rare skills below is what gets read.
Most people in this occupation already list these. Still required — just not what gets you shortlisted.
What the occupation pays Median $138,970 (middle half $107,524–$175,762).
Estimated from BLS employment for this occupation and area, per-skill prevalence across our listing corpus, and published wage benchmarks — as of Jul 29, 2026. It is a model, not a headcount.
Why we read it this way (7)
This role is genuinely difficult to classify by SOC: the primary day-to-day work is transmission planning analysis (power flow studies, contingency screening, interconnection studies) with a secondary but real software-engineering component (Python pipelines, Julia/Sienna service code). It could reasonably map to 15-2031 (Operations Research Analysts, for the engineering-analysis work) or 15-1252 (Software Developers, for the code-contribution and product-building framing). 15-1252 was chosen as primary because the posting explicitly frames this as a 'hands-on engineering role' that ships code and builds new study types into a software product, but confidence is Low given the heavy domain-analysis emphasis.
No work location or metro area is stated in the posting. The flexible work schedule benefit and absence of any office reference suggest remote or flexible arrangements, but this is not explicitly confirmed as fully remote.
The 4–6 years experience requirement is stated specifically for transmission planning at an RTO/ISO or utility, not as a general role-level requirement; it is treated as the overall experience floor.
PSS/E, PSLF, PowerWorld, TARA, PROMOD, and GridView are listed together under Desired Qualifications as interchangeable options — emitted as a single preferred skill with alternatives.
Sienna and PowerSystems.jl refer to the same Julia-based power systems library and are combined into one preferred skill.
Flutter and React appear under Desired Qualifications explicitly noted as 'not required, but useful' — marked preferred accordingly.
IEEE 738, FERC Order 881/AAR, LGIA/cluster/affected-system studies in WECC or MISO, NERC TPL-001/MOD-032/FAC standards, and reporting/visualization experience are named in Desired Qualifications but are domain knowledge or regulatory frameworks rather than concrete named tools — omitted from the skills list per extraction rules, except where a specific tool (Plotly) was named.
Read the full posting
The employer publishes the full description on their own site — read it there ↗. Or sign in to read it here — it's free, and it also lets you track this application.