Urban Sky operates reusable Microballoon stratospheric systems—rapidly deployable, navigable balloons with recoverable descent, custom payloads (optical, NIR, LWIR), autonomous control, and forecasting for high-resolution Earth observation and monitoring.
<div class="content-intro"><p><strong>About Urban Sky: </strong></p> <p>Urban Sky is a venture-backed aerospace startup that pioneers utilization of the stratosphere and reimagines the way humans view and analyze the earth. We design, build, operate, and sell stratospheric balloon systems, and the data we collect supports a wide range of applications, from real-time wildfire monitoring to urban mapping. Our technology is also employed by government customers including the Department of Defense (DoD), NASA, and others. Urban Sky sends flight vehicles to the stratosphere on a weekly basis. </p> <p>Our team consists of engineers, makers, developers, and doers who believe in the power of human potential when passion meets utility within a small, supportive team. At Urban Sky we strive to create a team culture grounded in candor, inclusion, respect and empowerment. </p> <p>We aim to build the next chapter of stratospheric history in Denver and are seeking self-starting, open-minded, and hard-working team members. </p></div><p><span style="font-size: 12pt;"><strong><span data-contrast="auto">About The Role:</span></strong><span data-ccp-props="{}"> </span></span></p> <ul> <li>We're looking for a Staff Software Engineer who wants real ownership in a fast-moving environment. </li> <li>You'll help design, build, deploy, and operate the software that runs Urban Sky's manufacturing operation—a full-stack MRP system that tracks inventory, work orders, bills of materials, quality holds, and serialized parts from receiving through final integration. It's the operational backbone of how we actually build balloons. Because the company is growing quickly, the scope of the role will evolve over time, and you'll have meaningful influence over what we build next and how we build it. </li> <li>You'll work shoulder-to-shoulder with the people using the software every day—manufacturing technicians, logistics coordinators, quality inspectors, and finance. There's no product manager between you and them. You'll learn how parts flow through the building, what makes a quarantine workflow painful at 3pm on a Friday, and how a missed traceability record turns into a compliance problem. Translating messy physical processes into clean software is most of the job. </li> <li>The interfaces you build are for operators, not consumers. A shop-floor tech holding a tablet, scanning a barcode, working through a multi-step assembly procedure—that's your user. Touch targets, scanner integration, and drag-and-drop work instructions matter more than landing-page polish. </li> <li>We operate in an aerospace-regulated environment (AS9100). Every mutation needs an audit trail. Serialized parts need end-to-end traceability. "Move fast and break things" doesn't apply to production data. We still move fast—but with the discipline that comes from knowing a corrupted record can ground a flight. </li> <li>You don't need prior MRP or manufacturing experience. You do need to be excited—or at least not intimidated—by learning a complex business domain alongside the code. </li> <li>If you enjoy small teams and solving ambiguous problems, this role is likely a great fit. </li> </ul> <p><span style="font-size: 12pt;"><strong><span data-contrast="auto">What You'll Do</span></strong><span data-ccp-props="{}"> </span></span></p> <ul> <li>Our overall software team is roughly 7 people, and this team will be just 2 people, everyone works across the stack. That's not aspirational—it's required. A small team with real ownership only works if everyone can contribute quickly and adapt as the company and product evolve. </li> <li>Senior engineers here build trust by shipping early and expanding their scope through demonstrated ownership. </li> </ul> <p><span style="font-size: 12pt;"><strong><span data-contrast="auto">What we need you to do right away</span></strong></span></p> <ul> <li>We expect senior engineers to become productive almost immediately. </li> <li>In your first days and weeks, you will: <ul> <li>Set up your environment and start committing code within your first day or two </li> <li>Learn existing systems by improving them, not by watching from the sidelines </li> <li>Fix bugs, tighten rough edges, and ship small enhancements to production </li> <li>Participate in deployments, debugging, and operational workflows </li> <li>Use AI tools from the start to understand the codebase and accelerate contributions </li> <li>Ask questions, propose improvements, and engage in technical decisions </li> </ul> </li> <li>You won't be waiting for a long ramp period. </li> <li>You'll build context by doing real work that ships. </li> </ul> <p><span style="font-size: 12pt;"><strong><span data-contrast="auto">What you will grow quickly into</span></strong></span></p> <ul> <li>As you gain context, scope expands fast. </li> <li>Within your first couple of months, you'll be expected to: <ul> <li>Own meaningful areas of our stack across backend, frontend, and infrastructure </li> <li>Lead design and implementation of projects that may span quarters </li> <li>Make architectural decisions with an eye toward reliability, operability, and future change </li> <li>Work directly with operators and stakeholders—often non-engineers—to refine solutions </li> <li>Drive systems from concept → implementation → production → iteration → support </li> <li>Continuously simplify, improve, and evolve what you own </li> <li>Help the team move faster by raising technical quality and reducing friction </li> </ul> </li> <li>By this point, you're not just contributing—you're a primary owner. </li> <li>There are no lanes to stay in and no handoffs to hide behind. </li> <li>If something feels confusing to an operator, that's an engineering problem. </li> <li>If a system is brittle, slow, or overbuilt, tha