Reliable Robotics jobs: what your CV needs in 2026

What does the $115M raise mean if you want a Reliable Robotics job?

Reliable Robotics announced $115 million in new capital on 20 October 2026 — $90 million in equity led by returning investor Nimble Partners, plus a $25 million term loan from Silicon Valley Bank — upsizing its Series D to $275 million and lifting the company past a $1 billion valuation. For a job seeker, the headline number matters less than where the money goes. The company said it will expand its aircraft fleet and production facilities, scale production of its Reliable Autonomy System, grow the engineering team, and advance FAA certification for uncrewed commercial cargo flights. Each of those four lines maps to a hiring plan, and each one hints at what the next CV screen will reward.

Some background is worth having before you apply. Reliable Robotics was founded in 2017 in Mountain View by veterans of SpaceX and Tesla, with co-founder Robert Rose as CEO, and has raised more than $380 million in equity to date. It retrofits existing aircraft — most visibly the Cessna 208 Caravan — rather than building a new airframe, and its system goes after the two accident causes that dominate fatalities in that class of flying: controlled flight into terrain and loss of control. The company holds a US Air Force contract worth roughly $17.4 million, reports more than 200 commitments from commercial and military customers, and says headcount has nearly tripled since its previous round.

Read that last fact again, because it changes how you should apply. A team that nearly tripled is a team still writing its own hiring bar as it goes, and it leans hard on the job description to do the filtering. Postings at this stage tend to be unusually literal: the words in the ad really are the words the screen looks for. That's good news for you. You don't have to guess what an autonomy company values when the ad already spells out deterministic bare-metal C++, DO-178C, and working with flight hardware in the lab and on the plane. Your task is making sure a recruiter and a parser both find those words, backed by evidence, high on page one.

Which roles are open, and what do the ads actually ask for?

The openings cluster tightly around flight software: Flight Software Engineer and Sr. Flight Software Engineer, Embedded Software Engineer, Sr. Flight Software Verification Engineer, DevOps Engineer for Flight Software, Flight Guidance Engineer on the GNC team, Flight Control Law Engineer, Displays Software Engineer and Sr. FPGA Verification Engineer. Posted annual ranges run roughly $136,000 to $230,000 depending on level, role and location, with most positions based in Mountain View and some in San Diego. Experience asks are explicit rather than vague — two or more years of professional C/C++ for the mid-level flight software role, seven or more for the senior one, three or more for embedded. That specificity is a gift to anyone tailoring a CV.

The scope is unusually concrete for a startup. Flight software engineers write highly deterministic C++ in a bare-metal environment that talks to sensors and control systems, handle system faults, integrate with vehicle subsystems, drive requirements, write unit tests, then work with flight hardware in the lab and on the aircraft and help plan flight testing. The embedded posting goes lower still: OS and hardware initialization, networking, protocol drivers, memory interfaces, unit tests written against DO-178C, plus Python integration tests and CI infrastructure. Verification sits in its own dedicated role. Senior postings mention travel up to around 10% of the time, and the positions require access to information subject to US export controls.

So write the CV the ad asks for, not the one you already have. If a bullet says "developed software for embedded platforms," rewrite it to name the processor, the toolchain, whether you ran without an operating system, and the fault you couldn't afford to miss. Swap "tested extensively" for the test level, the coverage target and the standard you tested against. Keep the stack in a plain single-column list a parser reads cleanly: C, C++17, Python, RTOS names, GDB, Jenkins or GitHub Actions, AWS, and the bus protocols you've genuinely touched. If formatting is your weak spot, this walkthrough of getting an engineer's CV through the first screen covers the traps in detail.

What certification evidence does an autonomous aviation CV have to show?

Certification evidence is the biggest differentiator on an autonomous aviation engineer resume, and the senior flight software ad says so outright by listing DO-178C and safety-critical work as preferred. Show where you sat in the DO-178C lifecycle and at which design assurance level — Level A for catastrophic failure conditions down to Level E for no effect. Name the artifacts you produced or reviewed: the Plan for Software Aspects of Certification, the software configuration index, the software accomplishment summary, low-level requirements, bidirectional trace data, structural coverage reports. If you achieved modified condition/decision coverage on DAL A code, write that in plain words. One honest acronym carries more weight here than a paragraph of adjectives.

Systems and safety candidates have a parallel vocabulary, and it belongs on the page with revision letters attached. ARP4754A governs civil aircraft and system development; ARP4761A, published in December 2023, carries the safety assessment methods used to show compliance with 14 CFR 25.1309. If you've run a functional hazard assessment, a preliminary system safety assessment or a full SSA, built fault trees, written FMEAs, assigned FDAL and IDAL, or assembled the safety case that ties the evidence chain together, say which one and on what system. The habit of naming standards with their version years reads as fluency to anyone who has sat across the table from a regulator.

The mistake almost everyone makes is treating "DO-178C" as a keyword rather than a claim. A skills line listing DO-178C, DO-254 and DO-330 with nothing underneath it invites an awkward interview question within ninety seconds. Put the standard inside the bullet instead: "Wrote and traced 340 low-level requirements for a DAL B navigation component; closed 22 review findings before the stage-of-involvement audit." That sentence survives scrutiny. If you're rebuilding from an old file, a chat-based tool that turns your raw history into an ATS-friendly draft saves hours — you can build a flight-software CV from your existing one and export it as PDF or Word in six templates.

How do pilots, defense and aerospace engineers reposition for autonomy?

You reposition by translating what you already did into the autonomy stack's own language, not by claiming new skills. A flight test engineer who wrote test cards and flew envelope expansion has done requirements-based verification; say it that way. A pilot with Part 135 cargo hours in a Caravan understands exactly the operation this system is certifying, including the taxi, takeoff, cruise, landing, braking and rollout phases the company's supplemental type certificate covers with continuous autopilot engagement. Lead with the operational judgment and the written evidence trail — test plans, anomaly reports, dispatch decisions, hours by aircraft type — and the gap between "operator" and "engineer" narrows fast.

Defense candidates usually hold more relevant material than they realize. A company with a US Air Force contract reads MIL-STD work, UAS ground control station experience, airworthiness releases and classified-adjacent process discipline as directly transferable. Spell out the platform, the number of sorties or test events you supported, the subsystem you owned and the review gates you cleared. Automotive and robotics engineers have a different bridge: hardware-in-the-loop rigs, sensor fusion, deterministic real-time control and sim-to-real validation all carry over. The way strong self-driving stacks get written up with validation metrics maps almost one-to-one onto aviation autonomy, minus the certification paperwork you'll need to learn.

Here's the opinion I'll defend: in safety-critical aviation, your GitHub matters less than your traceability. A tidy portfolio of weekend drone projects is worth less on this screen than a single line proving you wrote low-level requirements that survived an independent review. Hobby work earns its place when it's genuinely close to the job — a real-time controller on a microcontroller with measured jitter numbers, a HIL bench you built yourself, a fault-injection harness. Otherwise, spend that page space on the certification chain and the flight hardware you've actually put your hands on. Hiring engineers in this field are trained to ask for evidence, and they will.

How do you tailor your CV to one specific job ad?

Tailor against the ad itself, one role at a time. Copy the job description text into a CV analysis, let it surface the skills your document is missing, then rewrite the top third of page one so the gaps close. Paste the text rather than a link — LinkedIn and Indeed block fetching, so the URL often returns nothing useful. Pick the posting you're genuinely closest to, usually by the years-of-C/C++ line, and resist the urge to send one generic file to five openings. Companies at this stage of growth hire against the exact requirement they wrote, and a near-miss CV reads as a different candidate entirely.

Then make the file itself boring in the way parsers like. Single column, no text boxes, no icons standing in for section headings, real dates in a consistent format, your stack as plain text rather than a graphic skill meter. Put certification work under experience, not in a sidebar. One page is fine for a junior; two is normal once you have a decade of programs behind you. The same discipline that makes component-level robotics proof legible on a CV applies here: concrete nouns, measured outcomes, no hype. And note the export-control line in the ad — have your eligibility answer ready before you apply.

Before you hit send, get a second read you can't give yourself. A free analysis returns a score out of 100, five category scores covering experience, tech stack, impact and ownership, clarity and structure, and ATS compatibility, plus your strengths and a visual layout check — enough to tell you whether a parser can read the document at all. The paid full analysis adds the fix list and the blunt "why you might be rejected" view. If you're applying to an aviation startup hiring hard in 2026, run your CV through a free check first, fix what it flags, then apply once and properly.

Frequently asked questions