Careers at JPL: Teams, Pay and How to Get Hired

The Hiring Filter

Candidate reports across 320 interviews show a 0.0 percent offer rate at JPL — a filter that has staffed every NASA Mars rover since Sojourner. The clean room doesn't care about your resume. It cares whether the thing you designed survives launch, cruise, and a seven-minute descent to the surface of Mars.

That reality shapes every hiring decision at the Jet Propulsion Laboratory. As a federally funded research and development center managed by Caltech for NASA, JPL sits outside the standard civil-service pipeline. Its roughly 5,500 regular employees are Caltech staff working on NASA contracts, not federal civil servants. The distinction matters: hiring follows Caltech policies, security clearances run through NASA, and the work spans robotic exploration, Earth science, astrophysics, and the Deep Space Network that keeps it all talking to Earth. JPL selects candidates based on proven technical capability and alignment with mission-critical work, offering competitive compensation within a defined band and a rigorous, multi-stage hiring process that prioritizes problem-solving under constraints. Employees thrive in an environment defined by technical excellence, cross-team collaboration, and long-term commitment to exploratory science and engineering.

Open requisitions cluster in Engineering, Financial and Business Operations, Software and Computing Systems, and Research, with smaller but steady demand in Facilities, Human Resources, Institutional Administrative Operations, Logistics, Communications, Educational, and Health and Safety. A recent board snapshot showed 65 listed positions, all in Pasadena; 59 were regular full-time roles and six were postdoctoral appointments. The board doesn't capture every hire (many roles are filled through internal conversion or the Pathways internship pipeline), but the distribution maps to the mission architecture: flight projects need systems, mechanical, electrical, and software engineers; mission operations need navigators, sequence engineers, and DSN analysts; science divisions need planetary scientists, instrument specialists, and data scientists; and the business side needs subcontract managers, resource analysts, and HR partners who understand cost-plus contracting and ITAR constraints.

The title ladder matters. JPL uses a graded engineering and science track (Engineer I through IV, then Principal Engineer and Technical Fellow) parallel to a Technologist track for R&D roles, plus a management track. A Data Scientist II posting explicitly calls for "cutting-edge AI and machine learning to automate planning, scheduling, and resource allocation for real-time missions"; a Technologist III in Frequency and Timing Systems asks for "atomic clock and satellite navigation systems" expertise. These aren't generic reqs. They map to flight projects in formulation or development (Europa Clipper, Mars Sample Return, SPHEREx, NISAR) and to the Deep Space Network upgrade program.

Internships feed the pipeline. JPL's site says "internships and research programs provide a strong pathway to a career with JPL and NASA," and the Pathways Internship Program offers direct conversion to full-time employment upon graduation. The laboratory also runs Project Discovery, a returnship partnership with the Society of Women Engineers and iRelaunch for professionals re-entering after extended absence. Veterans, military spouses, Peace Corps alumni, and Schedule A candidates access special hiring authorities through NASA's broader framework. But the core signal is consistent: JPL hires for technical depth first, mission alignment second, and everything else follows from there.

The people who stay describe the same filter. Bobak Ferdowsi, a systems engineer known for the Curiosity landing, said on the JPL careers page that the workforce shares "a common goal" and "not only great minds, but also really great personalities and characters." An Indeed reviewer with thirty-three years at the Lab called it "a blessing, honor, and privilege" and noted the location and that "people are easy to work with." The pattern holds across disciplines: proven capability on constrained, high-stakes problems — whether that's a Mars rover thermal design, a DSN scheduler, or a subcontract negotiation for a flight instrument — opens the door. The rest is learning the culture that keeps it open.

Pay Bands

As of June 2026, Salary.com reports base salaries at JPL typically range from $60,888 to $78,901 annually, averaging $69,308 (roughly $33 an hour). That band is narrow for a laboratory employing PhD planetary scientists, senior flight software engineers, and mission-critical systems architects alongside early-career technicians. The figures appear to reflect base pay only and may not capture the full picture for experienced staff, particularly given that JPL operates as a Caltech-administered FFRDC with structured grade levels tied to federal salary scales.

Third-party data from Levels.fyi surfaces two outliers. One entry lists a Software Engineering Manager at "NASA JPL" with a Common Range Average total compensation of $221,100, inclusive of base, bonuses, and any stock-equivalent components. Another lists a Product Designer at "JPL" at $51,973, below the Salary.com average and well below the reported floor. The discrepancy between the two "highest paying role" claims, and the fact that the Product Designer number falls under the stated minimum, suggests either data labeling issues (contractor vs. regular employee, different grading systems) or sparse sampling. Levels.fyi does not publish its sample sizes or collection dates; treat these as directional.

Zero G Talent's board currently carries no live JPL postings with disclosed salary bands, so we cannot cross-reference these figures against active requisitions on our platform. The ASML and Stripe bands on our board ($42,000–$266,000 (median $177,000) and $52,000–$286,000 (median $235,000)) illustrate how wide ranges can run at private-sector peers, but they are not proxies for JPL's civil-service-adjacent structure.

What the available data confirms: JPL compensation sits inside a defined band, consistent with a Caltech-managed, NASA-sponsored FFRDC where grades map to experience, education, and role classification rather than market bidding. Candidates should expect base offers to land within or near the $61,000–$79,000 window for individual-contributor technical roles, with total compensation for management and principal-level positions potentially reaching the low-$200,000 range when bonuses and deferred compensation are included. The laboratory's 2024–2025 workforce reductions (roughly 1,000 employees and contractors laid off amid Mars Sample Return budget shifts) may also affect negotiating leverage and grade availability in the near term.

Inside the Interview Loop

JPL's interview loop does not resemble the standard tech gauntlet. Candidate reports collected across 320 interviews rate the difficulty at 4.3 out of 10, with 53 percent calling it medium, 37 percent easy, and just under 10 percent hard or very hard. Sentiment sits at 76 percent positive. Yet the aggregated offer rate in those same reports is 0.0 percent. That gap — approachable process, vanishingly few offers — defines the challenge.

The loop typically opens with a recruiter screen, then moves into a series of panel conversations. Live coding rarely anchors the technical evaluation. Instead, hiring managers ask candidates to present their own work: a prepared technical talk followed by sustained questioning about decisions, trade-offs, and how they handled uncertainty. One reported pattern repeats across roles (software, systems, data, finance): the presentation ends, then the panel drills into depth and fit. "Communication Skills" and "Research communication" appear at the top of extracted topic lists, not as soft-skills checkboxes but as the lens through which technical competence is judged.

A second non-obvious element: spreadsheet walkthroughs. Multiple reports describe a practical case exercise where the candidate works through a problem in a spreadsheet, explaining assumptions and logic in real time. There is no compiler, no IDE. The interviewer watches how the candidate structures the problem, handles missing data, and revises when the numbers shift. For roles touching integration and testing, budgeting, or cost accounting, this replaces the whiteboard algorithm.

The process varies by group. A Reddit thread noted "it all depends on the group and position you'd be going in to," and flagged HR speed as a recurring problem: "abysmally slow and it ends up costing us talent." That delay creates a strategic opening: candidates who secure competing offers during the wait can use them as bargaining chips for a higher starting salary within JPL's defined bands.

Preparation that maps to the loop's actual demands outperforms generic LeetCode grinding. Build a tight presentation centered on what you personally did, the results, and the reasoning behind key decisions. Practice walking through a messy, open-ended problem on paper or in a spreadsheet, narrating each step. Align your examples to the domain themes that appear in the role's topic cluster: system integration and testing, scientific problem-solving, data engineering fundamentals, or cost accounting. Be ready to explain a project from requirements through failure modes, not just the happy path.

JPL recruiters and technical staff also run interviews at career fairs and conferences throughout the year, occasionally extending on-the-spot offers. For candidates near those events, that path can compress a months-long timeline into a single conversation. The data does not specify re-application policies or cooling-off periods; treat each loop as the one that counts.

Campus as Factory

JPL sits at the base of the San Gabriel Mountains in La Cañada Flintridge, near Los Angeles. The campus spans roughly 168 acres and hosts more than 4,500 employees, a population that swells when you count the rotating cast of university researchers, contractors, and the 30,000-plus visitors who pass through in a typical year. The site is a NASA field center operated by Caltech, a governance model that means the physical plant serves both a federal mission and a university research culture.

The most visible facility is the Space Flight Operations Facility, known universally as Mission Control. Designated a National Historic Landmark, it has monitored every NASA deep-space mission since 1964. Adjacent to it, the Spacecraft Assembly Facility houses high-bay cleanrooms where the Curiosity and Perseverance rovers were assembled, where the Ingenuity helicopter was integrated, and where the Europa Clipper spacecraft underwent final stacking before shipment to Florida.

Propulsion testing lives in the Electric Propulsion Laboratory, which maintains a fleet of vacuum chambers ranging from bench-top bell jars to the Owens Test Facility, a 3-meter-diameter, 10-meter-long cryopumped chamber built for high-power electric thruster qualification. Most chambers operate at cryogenic temperatures to replicate the space environment.

Additive manufacturing moved from experiment to production in the Additive Manufacturing Center (AMC). The center runs metal and polymer printers qualified for flight hardware.

The newest major building is the Flight Projects Center, a six-story, 195,000-square-foot facility completed as NASA's first LEED Gold-certified project and only the agency's second LEED building overall. It consolidates project offices, conference rooms, and collaborative workspaces that were previously scattered across older structures.

Caltech's main campus sits about six miles south in Pasadena. The proximity is deliberate: JPL began as a Caltech rocket project in 1936, and the relationship remains operational. Faculty hold joint appointments, graduate students cycle through JPL labs, and the Keck Institute for Space Studies (housed on the Caltech campus) runs study programs that feed directly into JPL mission concepts.

Cleanrooms abut vibration tables; vacuum chambers share walls with optics labs; the machine shop feeds flight hardware to the high bay next door. That density is intentional. The physical layout compresses the iteration loop — and at JPL, the iteration loop is where missions are won or lost.

Who Stays

The people who stay at JPL (some for three decades or more) share a recognizable profile. JPL's own culture documentation ties its identity to its history as an FFRDC operated by Caltech for NASA, a dual affiliation that creates a specific professional environment: academic rigor paired with mission-driven engineering, where publication-quality work must also survive launch vibration, deep-space thermal cycles, and a one-shot landing sequence.

The Lab's 2025 culture statement describes values and character "generated in part by the Lab's history and its unique status as part of the NASA and Caltech families." In practice, that means employees who thrive tend to operate comfortably in both worlds. They can write a conference paper for a peer-reviewed journal and also produce a flight-software requirements document that a downstream integration team can verify against a hardware-in-the-loop testbed. The Benefits & Perks page frames this explicitly: "funded by the space agency to serve the space program and national interests, while staffed and managed by one of the world's premier academic institutions." People who treat that tension as a feature — not a friction — last.

Glassdoor's aggregate rating of 3.9 out of 5 across 38 reviews places JPL in line with the manufacturing-industry average, but the qualitative signals point to a different driver of retention. Reviews consistently highlight work-life balance and collegiality. That observation maps directly to the cross-disciplinary reality of robotic missions: a propulsion engineer cannot succeed without negotiating thermal margins with the thermal team, power budgets with the electrical team, and mass allocations with the systems engineers. The Lab's primary product (robotic spacecraft that explore the solar system) is inherently a system-of-systems endeavor. Candidates who arrive with deep single-discipline expertise but no appetite for the negotiation, documentation, and compromise that integration demands tend to leave. Those who treat cross-team interfaces as the core engineering problem stay.

The "Who We Are" page on JPL's careers site frames the work as "change the course of human history, and etch a legacy in the stars." That language attracts a specific motivation: mission over product cycle. Employees who measure success by whether a rover survives its first Martian winter, not by quarterly feature velocity, align with the Lab's cadence. Missions span years to decades; the Mars Sample Return campaign, for instance, stretches across multiple launch windows and international partnerships. Thriving here requires comfort with long horizons, shifting requirements driven by science discoveries, and the political and budgetary forces that shape NASA's portfolio.

Technical depth remains the baseline. The hiring process screens for proven capability under constraints: panel interviews and assessments that probe how candidates have handled failure modes, schedule pressure, and ambiguous requirements. But the differentiator for longevity is systems thinking: the ability to trace a requirement from a science objective through a subsystem interface to a test procedure, and to communicate that traceability to a reviewer who may sit in a different directorate. JPL's own records and employee accounts converge on a portrait: technically excellent, collaboration-fluent, mission-aligned, and willing to stay long enough to see a spacecraft they touched reach its destination. That filter still applies: it only cares that the hardware works — and the people who stay are the ones who've watched their work ride a rocket into the dark, then turned around to design the next one.

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.