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

Who Gets Hired

Latitude has 33 salaried roles open across six technical teams, with posted compensation ranging from $55,000 to $327,000 — a band that reveals a company building flight-critical autonomy stacks in three U.S. engineering hubs. The job board tells a clearer story than any recruiting deck: every role sits where hardware that flies meets software that decides. Pittsburgh, Palo Alto, and Detroit share every posting. That's not a remote-friendly gesture; it's a footprint. Pittsburgh brings the robotics heritage and Carnegie Mellon pipeline. Palo Alto sits on the autonomy talent density. Detroit delivers the automotive-grade hardware validation infrastructure. The company recruits for six core teams (Multi-Object Tracking & State Estimation, RTOS, Advanced Autonomy Systems, Security & Lifecycle, Radar Sensors, Lidar Hardware), and the median posted compensation across all 33 roles stands at $269,000.

These aren't functional silos. They're the subsystems of a vehicle that must sense, decide, and act where GPS denies and comms drop. The Senior Staff Software Systems Engineer role explicitly asks for "Advanced Autonomy Systems Engineering Lead" experience — the title signals they want someone who has owned the architecture, not just contributed modules. Manager roles reveal the team topology: two Software Engineering Manager positions (Multi-Object Tracking & State Estimation, RTOS) suggest those teams run deep enough to need dedicated leadership. The Security & Lifecycle manager (Manager II) indicates a separate org for supply-chain integrity and firmware lifecycle, distinct from the autonomy stack. On the individual-contributor side, Staff Software Engineer for Radar Sensors and Senior Hardware Engineer for Lidar show the sensor layer gets peer-level engineering investment, not afterthought integration.

What's missing is telling. No pure DevOps, no frontend, no data science titles. No "platform" or "infrastructure" roles detached from a sensor or autonomy team. The hiring mix is narrowly flight-critical: if the code doesn't run on the vehicle or the hardware doesn't survive vibration, the role doesn't exist. That filters the candidate pool before a recruiter sees a resume. The $55k floor likely covers roles not currently advertised: test technicians, integration specialists, production ops. The live postings target the senior-and-above slice that can walk into a lab and own a subsystem from day one. Every posted range starts above $190k.

The Pay Picture

Latitude publishes its compensation on the Zero G Talent board, and the numbers map cleanly to the six core teams. The top of the band belongs to engineering managers and senior staff engineers running autonomy, tracking, and real-time operating systems. Three distinct manager-level postings (Senior Software Engineering Manager for Multi-Object Tracking & State Estimation, Senior Software Engineering Manager for RTOS, and Senior Staff Software Systems Engineer (the autonomy lead)) all list identical bands: $253k to $327k across Pittsburgh, Palo Alto, and Detroit. A fourth manager role, Software Engineering Manager II for Security & Lifecycle, ranges $218k to $327k across Pittsburgh and Detroit. Each owns a subsystem that flies.

Individual-contributor staff roles sit one tier down but still clear $200k. The radar sensors engineer posts $218k–$327k across the same three sites. Senior Hardware Engineer for Lidar lists $192k–$288k, also in all three cities. The hardware number confirms that sensor-level ownership (not just software) commands staff-equivalent pay at Latitude. The three-site pattern repeats across every senior posting. Pittsburgh appears in all six; Palo Alto in five; Detroit in five. That consistency suggests the bands are location-adjusted but not location-dependent — a candidate in Detroit sees the same top number as one in Palo Alto. Median compensation of $269k across 33 roles indicates a top-heavy distribution: the company hires a lot of senior talent and pays for it. Candidates negotiating should anchor to the posted band for their exact title and site; Latitude publishes those numbers upfront.

Inside the Process

No public source documents Latitude's interview stages, screening criteria, or evaluation methods. The board data (the strongest available signal) shows only that roles exist and have compensation bands; it does not reveal how candidates move from application to offer. For applicants, this gap means the only reliable signals are the roles themselves. The postings imply a technical bar ("Senior Staff," "Manager II," "Staff"), but the specific screens (coding assessments, system design reviews, hardware bring-up exercises, behavioral panels) are undocumented.

What can be inferred comes from the role taxonomy itself. A Senior Staff Systems Engineer (the autonomy lead) doesn't screen for algorithmic cleverness in isolation; the title demands someone who has integrated perception, planning, and control on metal that flies. An RTOS manager at $327k ceiling isn't managing Jira boards — they're owning the timing guarantees that keep a vehicle stable when sensors disagree. The Security & Lifecycle manager role, separate from the autonomy stack, signals that supply-chain integrity and firmware sustainment are treated as first-class engineering concerns, not compliance afterthoughts. Until Latitude publishes its process or employees share verified accounts, applicants should treat the hiring workflow as opaque. The practical move: apply to a specific posted role that matches your hardware-software systems experience, prepare for engineering-fundamentals evaluation typical of flight-critical development (real-time systems, sensor fusion, safety-critical code), and expect location-specific on-site components given the integration and test infrastructure at each site.

Three Cities, One Stack

Latitude hires across three U.S. metros (Pittsburgh, Palo Alto, and Detroit), not five. Every open role lists at least two of these cities; several list all three. That pattern suggests a distributed engineering model rather than specialized site functions. The postings themselves don't describe labs, test cells, or integration floors at any location. Pittsburgh appears on every role. Palo Alto appears on every role except the Security & Lifecycle manager position. Detroit appears on every role. The Senior Hardware Engineer, Lidar and the Staff Software Engineer, Radar Sensors roles both span all three cities, implying hardware-software integration work is shared rather than siloed by site. The two Senior Software Engineering Manager roles (Multi-Object Tracking and RTOS) and the autonomy lead role also span all three.

No first-party source describes physical infrastructure: no vibration tables, anechoic chambers, thermal-vacuum cells, or final-integration high bays. Until the company publishes a site-capabilities page or a facility tour surfaces in credible reporting, any description of lab equipment would be speculation. What the data does show: the concentration of autonomy, radar, lidar, and RTOS roles across three major engineering hubs indicates a company building flight-critical perception and control stacks that need both Silicon Valley software depth and Midwestern hardware-test access. Pittsburgh brings Carnegie Mellon robotics talent and proximity to defense primes. Palo Alto brings embedded-systems and autonomy ecosystems. Detroit brings automotive-grade hardware validation infrastructure and supplier networks. The overlap on every role suggests engineers in any of the three sites can touch the full stack. If you're evaluating an offer, ask the hiring manager which site owns which test campaigns (hardware-in-the-loop, on-vehicle, or flight) and whether travel between sites is expected. The board data doesn't answer that.

The Profile That Wins

No company records, employee accounts, internal surveys, or documented cultural artifacts from Latitude describe valued traits, behavioral competencies, or success profiles. The first-party board data shows 33 salaried postings across six role families with a board-wide salary band of $55k–$327k (median $269k) and locations in Pittsburgh, Palo Alto, and Detroit. That is the full evidentiary record.

What can be inferred comes only from the job titles and levels themselves. Senior Software Engineering Managers for the tracking team and for RTOS both sit at the $253k–$327k band, suggesting the company places high value on leaders who can own perception stacks and real-time operating systems — domains where missed deadlines or integration failures propagate directly to flight risk. The Staff Software Systems Engineer role for Advanced Autonomy Systems Engineering Lead sits in the same band, indicating that cross-cutting autonomy architecture, not just component delivery, is a recognized career peak. The Security & Lifecycle manager role at $218k–$327k signals that those concerns are treated as such. The Staff Radar Sensors engineer and Senior Lidar Hardware engineer roles, at $218k–$327k and $192k–$288k respectively, show that deep sensor-domain expertise (RF front ends, waveform design, photon-counting detectors) commands staff-level compensation without requiring people management.

No internal rubric, promotion committee notes, or employee testimonial appears in the research to confirm whether "ownership of complex hardware-software systems under real-world constraints" is an explicit hiring screen or an emergent pattern. The five U.S. sites mentioned in company plans are not enumerated in the board data; only three metros appear in the postings. In the absence of first-party cultural documentation, the only grounded signal is the role taxonomy: Latitude hires for depth in perception, autonomy, real-time systems, sensor hardware, and security lifecycle — and pays staff and principal ICs at parity with engineering managers. That structure rewards technical depth that stays technical. Whether the organization also selects for communication style, decision-making under incomplete data, or cross-team influence is not documented in the sources provided.

The board doesn't lie. It shows six teams, three cities, one stack — and a pay band that starts where most companies' principal bands top out. You don't apply to Latitude to specialize. You apply because you've already built the thing that flies, and you want to own the next one.

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