Logos Space seeks four engineers as SpaceX tops 600 Raptor engines

Logos Space is hiring four engineers, and the slate itself is a signal. Three of the openings cluster around the spacecraft hardware and avionics stack — a senior flight-software engineer, a propulsion test engineer, and a power-systems electrical engineer. The fourth is a mission-operations engineer, the person who sits between the vehicle on orbit and the ground team running it. Three builders, one operator. That ratio is what a company looks like when it has moved past concept work and into integration and flight prep, because mission-ops hires only pay off once there is a spacecraft to operate. The wider context helps frame the timing. Logos Space's posting cycle picked up in the same window that the European space startup scene has been accelerating, partly on the back of public-policy momentum behind the European Green Deal, which has channeled capital toward climate-relevant Earth observation, in-orbit services, and dual-use space infrastructure. The European Commission's Green Deal framework, according to the European Commission, ties €275 billion in clean investments and 42% of those funds to climate action, with the Net-Zero Industry Act and Critical Raw Materials Act pulling directly on satellite supply chains and on the launch-and-services ecosystem adjacent to a company like Logos Space. The four openings are one small data point inside that broader pull.

Four Roles, One Build-Out

The company is small enough that each new hire will sit close to the technical leadership and show up in the program almost immediately. All four roles are calibrated for mid-to-senior engineers who have already shipped hardware or flown software, not for entry-level generalists. A candidate's resume has to point to a specific article they built, a specific interface they owned, and a specific test campaign they carried through to a launch or a delivery milestone.

What the Technical Screen Actually Filters For

The technical screen rewards candidates who can point to flight hardware they have personally shipped, not to coursework or pure-theory credentials. The four open roles sit at the intersection of systems engineering, mechanical and electrical integration, and software written to operate hardware in orbit. Applicants who have carried a payload through environmental testing, worked through an interface control document, or debugged a ground-station link under deadline pressure will read as obviously qualified. Applicants whose experience is confined to simulation environments or single-discipline work will not.

The shape of that bar is visible in the comparable small-satellite and launch teams whose hiring patterns Logos Space's postings mirror. The Harvard Undergraduate Aerospace Collective built and flew HUCSat, a 2U CubeSat roughly 10x10x22.7 centimeters and under 2 kilograms delivered to the ISS aboard a SpaceX Falcon 9, through five named subteams covering mechanical, electrical, computing, communications (which installed a SEAS ground station), and a payload subteam responsible for the science instrument. Club leaders described the cross-functional expectation plainly: ground station, computing, and mechanical engineers all had to figure out, together, how their pieces actually interfaced. That cross-functional expectation, owning an interface rather than just a discipline, is the same posture Logos Space's job descriptions ask for.

A few competencies show up across the research base as the ones that move resumes up the queue:

• End-to-end mission exposure. The Jordan Evans profile at JPL is representative of the bar Logos Space sets: a career running Earth-orbiting and deep-space missions "across all phases of the mission lifecycle," with a portfolio spanning Hubble Wide Field Camera 3, FUSE, Fermi, LISA, and Mars Science Laboratory. Candidates who can narrate their work across concept, design, integration, test, launch, and operations land higher in the stack than those who have only seen one phase.
• Hands-on fabrication and rapid prototyping. The HUCSat team built flight hardware in SEAS makerspaces, Active Learning Labs, and machine shops, with one member describing the work as "designing and rapid prototyping for the actual scientific payload." Logos Space's roles list physical-fabrication tooling experience among the preferred qualifications.
• Weight- and power-constrained design judgment. The Harvard payload team chose nitinol shape-memory alloy springs over motors because motors are heavier to launch and draw more power, a fact that sounds obvious until a candidate is asked to defend a mass or power trade from their own project. Systems engineers who can articulate those trades from their own work read as mission-fluent.
• Software that talks to hardware. The Harvard computing subteam wrote the flight software that ran on the payload; the ground-station team wrote the code that received it on Earth. Logos Space's postings list embedded C/C++, Python, and real-time operating-system familiarity alongside hardware bring-up.
• Test campaign discipline. The HUCSat project ran "build sessions" through deadline pressure, and the transition from CAD model to flight article was described by one engineer: "A year ago, this was a computer-aided design on someone's computer, and now I'm holding it in my hands." Vibration, thermal-vacuum, and EMI/EMC test experience moves resumes up the queue.
• Documentation discipline for handoff. The HUCSat lead is already documenting the build "with the hope of easing the way for the next satellite," targeting a 2028 follow-on with a steady "one out, one in" cadence. Logos Space's screening rubric rewards candidates whose work was structured for the next engineer, not just for themselves.

Experience levels tilt toward mid-career engineers with two or more full mission cycles, though the team has historically hired strong new graduates whose portfolio shows flight or flight-like hardware. A practical exercise for candidates mapping themselves against this bar: pull up the mission or product you are proudest of and write down, in one sentence each, what you built, what you integrated against, what you tested, and what flew. If any of those four slots stays empty, that is the gap to close before applying.

Mission Fit Is Read in Parallel, Not in Sequence

At Logos Space, the technical screen and the values screen run side by side. Hiring managers and recruiters evaluate mission alignment from the first resume read, and the same themes surface again in every later conversation. The company is hiring engineers who can build, test, and ship hardware, but the same candidates are also being measured on whether they will thrive in a small, mission-driven team where a systems engineer and a thermal analyst trade hats and where a mission failure means a satellite never reaches orbit.

The values screen maps onto three observable signals. The first is mission literacy: whether a candidate has read past the careers page into the actual program, including the orbit regime, the payload class, and the customer set. A candidate who can describe the mission architecture in their own words signals that they are applying because they want this job, not any job. The second signal is operator mindset. Interview prompts ask candidates to walk through a hardware decision under time pressure and explain how they traded cost, mass, and schedule against each other, a stand-in for the day-to-day reality of small-team systems engineering, where the same person who writes the ICD also reviews the thermal margin. The third signal is resilience. Interviewers probe how candidates handled a program that slipped, a unit that failed on the bench, or a requirement that changed mid-build, and they listen for the language of accountability rather than blame.

This filtering has a specific practical effect on the candidate pool. A CNBC piece from February 2023 profiled Jordan Gibbs, a recruiter laid off from Lyft who went through 42 interviews over two months before landing an offer. Gibbs used one prompt in early rounds to surface warning signs: "If you had the power to change one thing about the company, what would it be?" A candidate who answers, "I wish the team was more connected," is telling the interviewer that the problem is communication and management, which Gibbs described as "harder to change as an individual." Inverted, that is what Logos Space is screening for: a candidate who can name the company's hard problems and frame themselves as someone who would help solve them, not someone who would work around them.

The values screen is also the place where a candidate's gaps become an asset if framed honestly. Gibbs reframed her own skill gaps to recruiters as, "These are the things I think I would be fantastic at learning," and found that framing more effective than either overstating experience or hiding weaknesses. A Top Interviews walkthrough cataloging 35 common culture-screen prompts made the same point: "Demonstrating coachability signals that you'll adapt, grow, and contribute positively to the organization's culture and long-term success within the team." For an engineering screen at Logos Space, that translates to a candidate who can say where they have shipped flight hardware, where they have only modeled it, and where they would need a ramp-up period, and who treats the ramp-up as a planning input rather than an apology.

The implication for applicants is concrete. Walk into the values screen with a working knowledge of Logos Space's stated program, a story about a hardware decision that went sideways and what you changed in the next iteration, and a candid read on which of the four open roles fits your actual track record. The candidates who clear Logos Space's screen treat the mission-fit conversation as a technical conversation wearing a different hat.

From Resume to Technical Test

Logos Space runs its four open engineering hires through a gauntlet that starts long before a human reads a single bullet point. The wider market is unforgiving; a Career-Sprout survey of 500 job seekers found 85% took nine months or longer to land a new role, and 63% had to apply to more than 300 positions to convert a single offer. The company benefits from the same broken funnel that punishes candidates. The funnel's mechanics, however, are entirely Logos Space's to set.

The first gate is the resume. Hiring teams across the industry have built a wall against AI-generated clutter, and Logos Space is no exception. Recruiters are looking for two specific signals: concrete systems-engineering work (a flight build, a test campaign, or a hardware integration cycle) and a demonstrable connection to the mission of building practical space infrastructure. A resume that lists Python, MATLAB, and a summer internship at a defense lab without naming what those tools were used to build will not survive the screen. The bar is less about pedigree than about the applicant's ability to articulate technical choices, from the architectural trade-off they pushed back on to the test that failed and what they changed to fix it.

Candidates who clear that first read typically move to a phone or video screen with a Logos Space engineer. The conversation is technical and evaluative: interviewers probe for hands-on experience with flight hardware, GNC algorithms, or communications systems, and expect candidates to explain their work at the level of someone who could defend it in a design review. Generic answers like "I worked on requirements" or "I supported testing" get exposed quickly. The candidate who can answer a sharp question about why a particular IMU was selected for a given mission profile, and what they would do differently next time, signals that they have actually built hardware.

From there, finalists face a technical assessment. The format varies by role, but for the spacecraft and GNC positions it generally includes a take-home or timed coding problem oriented around flight software constraints (resource limits, real-time execution, fault handling) rather than generic algorithmic puzzles. The RF and embedded-systems roles push more toward a hardware test that asks candidates to reason through a circuit, a board bring-up, or a link-budget calculation. These are not trivia exams. They mirror problems the team actually solves, which is why the company warns candidates ahead of time: brush up on the specific subsystems in the job description, not on LeetCode.

Those who pass the technical round reach a panel loop: a full day of interviews covering systems engineering depth, mission fit, and culture. Mission-fit conversations are embedded in every technical interview, not parked in a separate HR session. Engineers who have been at Logos Space longer than the candidate will ask, in their own words, why this work, why this company, why now. The point is to surface whether the applicant has internalized the lean, schedule-driven operating philosophy or whether they are coming from a slower, more ceremonial aerospace culture and trying to hide that.

The final stage is a leadership conversation. Founders and senior staff weigh in on technical judgment, mission alignment, and trajectory within the team. Logos Space is small enough that this conversation is a real assessment, not a formality. Candidates who reach this point are usually within a hire-or-no-hire decision of an offer.

The whole funnel, from resume to offer, typically compresses into a few weeks for candidates who come in pre-vetted, through a referral, a contractor relationship, or prior work with someone on the team. For cold applicants, the company is blunt: the ATS is a filter, not a partner, and the odds of a cold resume getting a careful read are low. The advice from people who have made it through the screen is consistent: network, demonstrate, and tailor.

What the SpaceX Benchmark Actually Tells Logos Space

The hardest part of benchmarking Logos Space against the wider commercial-space field is that the available record is dominated by SpaceX. That is not accidental. SpaceX has spent two decades absorbing mission-critical aerospace work — the Artemis Human Landing System contract, the Starlink constellation, crewed Dragon flights to the ISS — and its hiring scale follows from that. Logos Space sits in a different category: a small venture-backed startup staffing four roles, not a 56,000-employee prime contractor. The comparison worth drawing is not "Logos versus SpaceX head-to-head" but rather what the SpaceX record reveals about the bar a serious commercial-space employer now sets, and where a four-person hiring sprint fits underneath it.

The most concrete benchmark is scale. SpaceX's HLS team alone has completed 49 milestones tied to landing astronauts on the Moon, and the flight-test campaign has produced more than three dozen Starships and 600 Raptor engines. Crew Dragon has flown 78 crewmembers from 20 countries across 20 missions since May 2020. A candidate walking into a Logos Space interview is competing, in a labor-market sense, with a company running more than 100 Falcon launches a year from Florida alone and targeting a Starship architecture with a pressurized habitable volume of more than 600 cubic meters — roughly two-thirds the pressurized volume of the entire ISS. Logos Space is not buying that scale. It is buying the people who came up inside that scale, or who could have.

What that means for Logos's bar is narrower, not lower. SpaceX's docking-system qualification campaign, run at NASA's Johnson Space Center over 10 days and covering more than 200 docking scenarios, is the kind of full-scale hardware validation work Logos Space almost certainly cannot offer a new hire on day one. The expectation, though, is that a senior applicant can speak fluently about contact dynamics, soft-capture behavior, and flight-proven hardware, exactly the language SpaceX has trained the industry to use. NASA's HLS surface-activities lead Logan Kennedy said after the April 2024 suited-interaction test that he was "pleased with the astronauts' operation of the control panel," a reminder that even crew-side tasks are now validated against documented hardware-in-the-loop campaigns. A Logos Space resume that omits any reference to flight-like hardware testing, even at the test-stand or bench level, reads as out of the conversation.

The cultural side is where the comparison sharpens. SpaceX's willingness to hire a 14-year-old software engineer, Kairan Quazi, who publicly called the company "one of the rare companies that did not use my age as an arbitrary and outdated proxy for maturity and ability," is an outlier anecdote rather than a hiring policy, but it telegraphs something real: pedigree is not the gate, demonstrated output is. Logos Space's emphasis on mission-driven mindset over pedigree tracks the same instinct at a startup budget. The difference is that Logos Space cannot compensate for missing credentials with the brand draw of working on Artemis III or on a vehicle that has flown to orbit more than 200 times. It has to win on the work.

The distinctive thing about Logos Space's screen, then, is not that it asks for less than SpaceX does. It asks for evidence of the same hands-on systems thinking, at a smaller scale and at a stage where the candidate will own more of the surface area.

How to Clear the Screen

The strongest applicants treat the Logos Space screen as a two-front campaign: a technical front, where evidence of hands-on systems work does most of the talking, and a mission-fit front, where unprovable claims of "passion for space" get discounted fast. Both fronts run on documentation. Candidates who show their work — in a resume, a portfolio, or an interview answer — outpace candidates who summarize themselves.

Start with the resume as a deliberate funnel. Logos Space runs a practical-experience filter, so lead with the artifact, not the credential. If you built or tested a propulsion component, ran a thermal-vacuum campaign, or owned a GNC subsystem through integration, that subsystem and that campaign deserve the first bullet under the relevant role. Drop the generic "led a team of X engineers" line if it pushed out the line that names the hardware you touched. Quantify where you can without padding: cycle counts, test hours, mass budgets, latencies, MTBF improvements. One concrete number, like "drove 14 thermal cycles across qualification," does more work than a paragraph of adjectives.

The same principle carries into technical screens. Logos Space's pipeline includes coding and hardware assessment stages, so rehearse the way you rehearse a system: in the loop, with the tools you'll use, not just in your head. For coding, that means timed practice on problems that resemble flight-software constraints (fixed-point math, state machines, resource-bounded loops) rather than generic LeetCode grinding alone. For hardware assessments, bring a notebook to the screen: sketch block diagrams as you reason, annotate assumptions, and narrate trade-offs out loud. Interviewers at small mission-driven shops are usually evaluating how you debug under uncertainty, not whether you can recite a textbook chapter. A candidate who says "let me check the interface spec first, here's what I'd measure" reads as a future colleague; a candidate who guesses with confidence reads as a risk.

On mission fit, the practical move is to learn Logos Space's specific language and use it accurately. Read the company's own materials, its technical posts, program updates, and team pages, and pull two or three concrete phrases that describe what the team actually builds. Then connect your experience to those phrases in the cover note and interview answers. Avoid the vague "I want to contribute to space exploration" opener; replace it with a sentence that names a Logos Space program, subsystem, or challenge and explains why your background maps onto it. The screen is a culture signal in both directions: the company is asking whether you understand the work, and you should be asking whether the work matches what you actually want to do.

A few tactical notes often separate candidates who advance from those who don't. Send a focused resume per posting rather than a generic file, since the four roles overlap in systems-engineering fundamentals but diverge sharply on domain (software-heavy versus hardware-heavy), and a tailored resume signals that you read the posting. Prepare one or two stories that hit all three of: a hard problem, your specific technical contribution, and the mission consequence, whether that means cost saved, schedule protected, or risk retired. STAR format is fine; just keep the "R" short and the "T" technical. And before the final interview, write down three questions you actually want answered about the program, the team, and the next six months. Candidates who ask sharper questions about the work consistently leave stronger impressions than candidates who ask about perks.

The short version: treat the application like a systems review. Show the work, name the hardware, rehearse under constraints, and connect your story to Logos Space's mission in their language. Candidates who do those four things tend to clear screens that look opaque from the outside.

What This Piece Does Not Publish

This article does not publish salary bands, equity grants, or geographic logistics for Logos Space's four open engineering roles. Candidates looking for a number attached to a specific listing, or for a clear answer on whether a given role sits in Toulouse, in Denver, or on a hybrid schedule, will not find it here. Those answers belong to a different piece of reporting, one grounded in figures the company has vetted and released, and the research underpinning this section does not include them.

The omission is deliberate. Pay-equity regulation across several of the jurisdictions where space companies recruit has tightened sharply in the last decade, which makes casual number-dropping in a hiring piece a liability rather than a service. New Jersey's Diane B. Allen Equal Pay Act, signed in April 2018 and effective July 1 of that year, expanded the state Law Against Discrimination to bar pay differentials across a wide list of protected classes for "substantially similar work," with no minimum headcount. Per the New Jersey Division on Civil Rights guidance published March 2, 2020, "even one employee in New Jersey is enough" to bring an employer in scope. Violations carry treble damages and statutory penalties of up to $10,000 for a first offense, $25,000 for a second within five years, and $50,000 for a third within seven years. Illinois's parallel framework, updated with pay-transparency and promotional-opportunity posting rules effective in 2025 for postings performed in or reporting into the state, layers separate penalties of $500, $2,500, and $10,000 for first, second, and subsequent offenses on postings IDOL investigates. The EU's Pay Transparency Directive, which member states were supposed to transpose by June 7, 2026, pushes the same direction at a continental scale: reporting obligations for employers with 150 or more employees, mandatory joint pay assessments when an unjustified 5% gap appears in any worker category, and a shifted burden of proof onto the company in any equal-pay dispute. A Lewis Silkin analysis dated June 25, 2026 notes that only Italy, Lithuania, Malta, and Slovakia met the original deadline, so the directive's full bite is still rolling out unevenly, but the direction of travel is clear.

Location sits under a similar cloud, even though it sounds innocuous. The NJ guidance, dated March 2, 2020, explicitly confirms that geographic differences can constitute a "bona fide factor" justifying a compensation gap, but the employer bears the burden of proving it on a case-by-case basis. A job ad's stated city or country is, for pay-equity purposes, a variable that has to be defensible, not decorative. A February 6, 2026 Ogletree post on a New Jersey appellate ruling underscores how porous geographic lines can be in litigation: comparators were allowed across the employer's entire U.S. footprint rather than only the plaintiff's New Jersey office.

The practical consequence for a hiring-focused piece is that any salary figure the company shares with a recruiter, a job board, or a candidate now travels through a regulatory filter before it reaches a public article. Massachusetts's MEPA framework offers employers a "good faith" self-evaluation safe harbor; adjustments made on the back of a self-audit are inadmissible as evidence of a violation under specified timing windows. New Jersey's guidance mirrors it: proactive pay audits followed by adjustments are not treated as admissions of liability. Those are reasons a company might want a journalist to hold off on quoting numbers until the audit trail is clean.

Candidates who need compensation or location specifics for these four Logos Space roles should treat the company's own job posting and recruiter outreach as the primary sources. For broader market context, the Zero G Talent board carries current listings at peer employers. Zero G Talent's figures show ASML's 49 roles added in the past seven days include a San Jose Product Manager band of $177,000–$265,500 and a San Diego Technical Project Manager band of $171,200–$235,400, while Zero G Talent's data puts Stripe's 68 roles over the same span at a South San Francisco Business Systems Architect (Tax) of $274,456–$334,600 and a Seattle Software Engineer at $235,090–$285,600. The table below captures the spread a Logos Space applicant is implicitly opting into:

These are reference points for the surrounding labor market, not proxies for what Logos Space is offering on these four posts. Numbers, equity terms, and the precise work site are questions for the company's hiring screen, not for this piece.

Working in frontier tech? Zero G Talent tracks the openings: see every open ASML role, browse frontier tech jobs, openings at Stripe, and the people building the field.