8 Applicants in 72 Hours, Then 250: The Race for Nextera's Six Robotics Jobs

Six Roles, One Architecture

Nextera Robotics has six open roles in Boston, a full-stack build list for autonomous machines that must survive construction sites, not lab benches. The positions span $60,000 to $220,000 and one to three-plus years of experience, mapping the technical architecture Nextera is betting on: a tether between high-level AI perception and hardware that climbs stairs, dodges rebar, and charges itself. Nextera Robotics, founded in 2015 by Lana Graf and Alex Rand (also listed as Alex S. Rand), graduated Y Combinator's S20 batch and runs a 20-person team deploying the Didge platform — treaded robots that autonomously document job sites and feed imagery into an AI layer for progress tracking, safety compliance, and BIM verification. The hiring plan reflects a company scaling AI-native robotics solutions and intensifying competition for specialized talent.

At the software apex sits the Robotics and AI Software Engineer - Autonomous Navigation for AMRs and Drones ($160K–$220K, 3+ years). The title signals the navigation stack is a first-class product concern, not an afterthought. These robots don't follow magnetic tape; they localize across multi-floor concrete structures, climb stairs, and return to chargers without human intervention. That demands SLAM, motion planning, and sim-to-real transfer tuned for dust, vibration, and changing lighting — problems that look more like field robotics than warehouse AMRs.

Directly adjacent, the AI / ML Engineer ($150K–$210K, 3+ years) owns the perception and analytics layer. Skanska and Gilbane deployments show Didge bots capturing thousands of 360° images per run, then running inference for PPE compliance, hole detection, water pooling, and install verification against BIM models. The role requires turning noisy site imagery into structured alerts: "five minutes after the robot captures something, you can get an alert," said Nextera's director of operations Jacob Ryals. This means the ML pipeline must be low-latency, continuously retrained, and robust to domain shift across projects.

Hardware gets two dedicated owners. The Mechanical Engineer - Robotics ($110K–$140K, 3+ years) owns the platform that survives abuse: stair-climbing treads, IP-rated enclosures, thermal management for onboard compute, and a charging dock reliable enough for months of unattended cycles. The Systems Integration Engineer - Autonomous Mobile Robots - Mechatronics ($120K–$145K, 1+ years) bridges that hardware to software: sensor bring-up, driver development, ROS 2 integration, and calibration routines that keep perception aligned after a robot tumbles off a curb.

Two roles reveal constraints most robotics startups underestimate. The Wireless Network Engineer ($110K–$200K, 3+ years) exists because construction sites are RF nightmares: steel, concrete, moving cranes, no IT infrastructure. The robots must maintain telemetry, offload imagery, and receive OTA updates over whatever spectrum is available: Wi-Fi, private LTE, or mesh. That's a distinct discipline from cloud DevOps, and Nextera treats it as such. Finally, the Robot Assembly Technician - MA local only ($60K–$75K, 1+ years) signals the company is past the prototype phase. You don't hire a dedicated assembler for onesies; you hire one when the build rate demands repeatable, documented work instructions and a quality gate before robots ship to Seattle or the next Gilbane site.

The spread tells a coherent story: Nextera is scaling a vertically integrated autonomy product for an industry that punishes fragility.

The Funnel: Four to Six Rounds in Three to Five Weeks

Nextera runs a 4–6 round funnel that typically resolves in 3–5 weeks from application to offer, per Interview Query data current as of March 2026. The acceptance rate sits in the low single digits, a function of rapid growth and a filter designed to surface engineers who can ship robotics software in production, not just recite textbook algorithms. The process starts with a technical hiring team review, not a generic ATS keyword scan. That team looks for autonomous mobile robot experience, SLAM fluency, and advanced programming chops in C++ or Python. If your resume clears that bar, a recruiter schedules a 20–30 minute phone screen covering motivation, mission alignment, and a high-level technical walkthrough.

The technical rounds (usually two to three) test problem-solving, robotics algorithm depth (path planning, sensor fusion, state estimation), and system design for fleet autonomy. Interview Query notes these sessions often include whiteboarding and live coding against simulation scenarios. Candidates without direct robotics backgrounds should expect a take-home challenge to prove hands-on capability. The behavioral round evaluates autonomous execution in agile teams, communication of complex trade-offs, and conflict resolution — standard STAR territory but weighted toward deployment realities. The final onsite (or virtual equivalent) spans a half or full day with multiple team members. Expect technical deep-dives, a practical coding or simulation task, and a system-design discussion centered on real-world deployment constraints: network reliability, hardware variance, safety certification. Offer negotiation follows, managed by the recruiter. Ghost periods after strong rounds usually signal internal scheduling, not rejection, though candidates report occasional disorganization and communication gaps. The funnel rewards candidates who treat it as a project: track stages, rehearse deployment stories, and clarify remote expectations early, since many roles require Boston presence for hardware integration.

The Profile: Deployment Over Theory

Nextera's open roles cluster around three technical pillars: advanced AI and computer vision for multimodal reasoning, full-stack robotics software for autonomous navigation, and the hardware–software integration layer that binds sensors, actuators, and networks into reliable machines. Candidates who advance share a profile shaped by those pillars.

The AI / ML Engineer and the navigation role roles demand three-plus years building AI systems, with explicit emphasis on vision-language models, large language models, and multimodal architectures. The AI/ML posting lists "advanced 'manual' coding and debugging skills (acquired during the 'pre-agentic' era)" alongside proficiency with modern AI-assisted development tools, a signal that Nextera wants engineers who understand model internals, not just API consumers. Both roles require strong mathematics, statistics, or physics backgrounds, familiarity with MLOps pipelines, and the ability to move models from experiment to production on cloud infrastructure. The navigation-focused role adds autonomous stack experience: SLAM, path planning, and real-time control loops that run on resource-constrained onboard compute.

the integration role and Mechanical Engineer - Robotics sit at the hardware–software boundary. The systems integration role asks for one-plus years tying together sensors, actuators, and compute platforms, work that demands fluency in ROS 2, real-time Linux, and the deterministic C++ control loops that Edstellar identifies as indispensable for millisecond-level response. The mechanical role requires three-plus years designing robotic mechanisms, with the implicit expectation that CAD models survive vibration, thermal cycling, and repeated contact forces from mobile manipulation. Both roles call for the "jack-of-all-trades" competence practicing roboticists describe: enough electronics to debug a custom PCB, enough firmware to trace a driver issue, enough software to instrument a test rig.

Wireless Network Engineer reflects a constraint pure software shops often overlook: fleets of autonomous robots need reliable, low-latency connectivity in warehouses, construction sites, and outdoor yards where Wi-Fi, 5G, and mesh networks contend with metal structures and interference. The wide salary band ($110K to $200K) suggests Nextera is hunting for someone who can architect the network layer as a first-class robotics subsystem, not an afterthought.

the assembly technician role anchors the pipeline in Boston. At $60K–$75K with one-plus years, it targets hands-on builders who can turn a bill of materials into a calibrated, tested unit, the "detailed and accurate" mindset GeeksforGeeks flags as foundational. The locality requirement signals Nextera's hardware iteration cycle is tight enough to demand daily physical presence.

Across every role, two soft-skill clusters appear repeatedly. First, communication across technical and non-technical teams: the AI/ML posting names it explicitly, and the cross-disciplinary nature of robotics projects makes it non-negotiable. Edstellar notes that robotics projects inherently require collaboration across mechanical, electrical, software, data science, manufacturing, quality, and domain experts. Second, ownership and adaptability: "strong ownership" in the AI/ML role, "continuous learning" in the Coursera and GeeksforGeeks analyses, and the reality that simulation-to-reality gaps, sensor noise, and fleet-edge cases force engineers to debug problems no textbook covers.

Pay: A $155,000 Spread

Nextera's six open roles span a $155,000 spread from lowest to highest posted base salary, reflecting a team that blends hands-on assembly with senior AI and systems engineering. The salary band spans $85,000–$215,000 with a median of $173,000 across six salaried positions, above the $99,067 average Salary.com estimates for the company. Salary.com notes the manufacturing durable industry range is $87,000–$112,000 and estimates Nextera's level as slightly below that industry average.

The two most senior software roles, both titled "Sr", command the top of the band. The the navigation engineer role focused on autonomous navigation posts $160,000–$220,000; the AI / ML Engineer sits at $150,000–$210,000. These figures align with Indeed's September 2026 data showing an average Robotics Engineer salary at Nextera of approximately $136,892 (18 percent above the national average), though Indeed's sample draws from just one posting. The Systems Integration Engineer and Mechanical Engineer - Robotics cluster in the $110,000–$145,000 corridor. The Wireless Network Engineer carries an unusually wide $110,000–$200,000 band, suggesting the role may span mid-level to principal scope. The Robot Assembly Technician is the sole hourly-scaled position at $60,000–$75,000, consistent with the technician tier.

Equity detail is absent from public postings. The August 2026 strategic equity investment from Oshkosh Corporation (NYSE: OSK), parent of JLG Industries, signals equity exists and has attracted a strategic buyer, but the board data does not disclose grant sizes, vesting schedules, or strike prices. Levels.fyi maintains a structured compensation page for Nextera that collects anonymous, verified employee submissions, though the research does not surface specific equity figures. Candidates should ask directly about the equity pool's size, refresh policies, and whether the Oshkosh investment introduced a new valuation or liquidity event.

Benefits information does not appear in job postings or third-party salary aggregators. Glassdoor lists two anonymous salary reports for two roles but no benefits breakdown. Given the company's sub-$5 million revenue and early-stage profile, benefits likely follow a lean startup model (health insurance, basic 401(k), and equity) rather than richer packages at later-stage robotics firms. The Boston location adds state-mandated paid family and medical leave; applicants should confirm the full package in screening calls.

Culture: Night-Shift Reliability

Public employee-sentiment data for Nextera is limited. SimplyHired shows one review reporting pay satisfaction at 0 percent based on a single response, with work-life balance rated 3.0 out of 5. Indeed lists two reviews for Nextera Robotics (one 5.0, one 1.0), and Glassdoor hosts four reviews. The Indeed reviews attached to "Nextera" without "Robotics" belong to NextEra Energy, the Florida-based utility — a different entity entirely. Conflating the two would mislead.

What external signal exists comes from a customer site. Gilbane Building Company has deployed Nextera's site-documentation robots on construction projects, using them to capture 360-degree imagery for AI analysis. An ENR report on that deployment reveals operational habits that indirectly shape engineering culture at Nextera. The robots typically run on second shift, meaning relatively few site workers interact with them directly. That scheduling choice, night-time autonomy, implies a development rhythm that prioritizes unattended reliability over daytime demo-ability. Engineers building for second-shift operation must design for edge cases that appear when no one is watching: lighting shifts, dust, network dropouts, unexpected obstacles.

The same ENR piece quotes Gilbane personnel describing the robot as "not an audit tool used against them" but "a proactive tool showing what has been installed." That framing — collaborative, not punitive — matters. It suggests Nextera's product philosophy centers on augmenting tradespeople rather than policing them, and that philosophy likely bleeds into internal team dynamics. When your core value proposition is "trust the data, not the surveillance," you tend to hire engineers who default to transparency. The report notes subcontractors have not pushed back because issues caught on one job are resolved on another before they repeat, a closed-loop problem-solving loop that requires high trust and low ego across the team.

First-party board data confirms Nextera is a Boston-based startup with six open roles spanning AI/ML, systems integration, navigation software, wireless networking, mechanical engineering, and assembly. The founding team (the founders) is small enough that early hires operate in direct view of leadership. In a company this size, culture isn't a policy document; it's the daily habits of the founders. Candidates should ask how decisions get made when the three founders disagree, how technical debt is prioritized against new feature work, and whether the second-shift reliability mandate creates on-call expectations for software and hardware engineers alike.

The ENR article also highlights a practical workflow: "People spend time on value-added problem solving, not data gathering," a line that reads as much like an internal aspiration as a customer benefit.

The absence of a deeper review trail means applicants must do their own due diligence: reach out to recent hires on LinkedIn, ask interviewers about on-call expectations for second-shift failures, and press on how the team handles the tension between rapid iteration and the reliability a construction site demands at 2 a.m.

The SimplyHired review, the customer-side operational details, and the founding-team structure together sketch a workplace that is small, technically demanding, and oriented around a hard reliability constraint most robotics startups can defer. That constraint — nightly, unattended, safety-adjacent operation on active job sites — is the cultural anchor. Everything else flows from it.

Strategy: Move Fast, Signal Relevance

The median application at a sub-50-person industrials robotics company gets no response. At Nextera, data shows a 72-hour window after a role posts where you face roughly eight competitors; by day seven the pool balloons past 250. The company has no dedicated recruiters; the founders review applications between running the business. That structure creates a specific playbook: move fast, signal relevance immediately, and follow up.

Apply within the first 72 hours

Theantijobboard's tracking shows roles are spotted and verified within two hours, alerts go out at four hours, and by day three only about eight people have applied. A role stays "uncontested" for roughly four days. Submitting a tailored application on day one or two puts you in front of the founders before the noise arrives. If you see a role on the board (the assembly technician role, AI / ML Engineer, the integration role, the navigation role, Wireless Network Engineer, or Mechanical Engineer - Robotics), apply that day.

Tailor the CV to the exact role; kill the generic resume

Theantijobboard is blunt: "A recycled CV gets rejected fast at Nextera Robotics (<50 people). They notice." Applications that mirror the job description's language clear automated filters at a materially higher rate. For the navigation engineer role, lead with ROS, SLAM, path planning, and sensor fusion, not a laundry list of frameworks. For the Systems Integration Engineer, foreground mechatronics integration, hardware-software interfaces, and fleet deployment experience. The AI / ML Engineer description weights object detection, segmentation, and neural-network training on real-world sensor streams. Match the vocabulary; the founders are scanning for the exact problems they need solved.

Lead with their problem, not your ambition

Nextera's mission is scaling AI-native autonomous robots across warehouses, production floors, and construction sites — deployed at Skanska's Seattle high-rise, integrated with BIM models, running 360-degree capture that replaces 40 human-hours per week. Research the Didge platform, the Boston-headquartered deployment model, and the MIT/Y-Combinator lineage. In the initial phone screen (20–30 minutes per Interview Query), you'll be asked about motivation and mission alignment. Answer with concrete understanding: "Your Didge robots on the Kaye project replace manual photo walks and feed safety compliance into an AI pipeline — I've built similar perception stacks for construction-site autonomy" beats "I'm passionate about robotics."

Prepare for a three-stage, seven-day sprint

Theantijobboard maps the funnel: Intro Call → Technical Deep Dive → Final Round, typically seven days from first contact to offer. Interview Query describes a longer 3–5 week arc with 4–6 rounds for software engineers, including recruiter screen, multiple technical interviews, behavioral, and a half- or full-day onsite with whiteboarding and simulation challenges. The discrepancy likely reflects role seniority and the company's evolving process. Plan for both: be ready to move at the seven-day clip, but budget mental bandwidth for a deeper technical gauntlet if you're targeting the navigation role or AI / ML Engineer roles.

Technical deep dive: show production-grade robotics judgment

The hardest stage is the Final Round. For software and autonomy roles, expect live coding in Python or C++ on graph traversal, dynamic programming, and real-time decision-making, framed as robotics problems (shortest path in a maze, cycle detection for planning). You'll discuss SLAM trade-offs: EKF vs. graph-based, loop closure in dynamic environments, sensor fusion across lidar, IMU, and wheel odometry. System design prompts will ask how you'd architect a fleet manager handling data synchronization, fault tolerance, and sensor calibration across dozens of AMRs. Bring concrete examples: "I reduced localization drift 40% by switching to a factor-graph backend and adding wheel-odometry constraints" carries more weight than textbook definitions.

For the Wireless Network Engineer, prepare to discuss reliable low-latency comms for mobile robots in concrete-and-steel environments. For the Mechanical Engineer - Robotics and Robot Assembly Technician, expect hands-on scrutiny of design-for-manufacturability, tolerance stacks, and fixture design for rapid assembly.

Behavioral: autonomy and self-sufficiency over textbook answers

At <50 people, Theantijobboard notes they "care about self-sufficiency over textbook knowledge." The behavioral round (often with engineering managers or cross-functional peers) probes how you operate in ambiguity: a project where requirements shifted mid-sprint, a hardware-software integration failure you debugged across teams, a time you shipped a perception module without a spec. Prepare STAR stories that end with "deployed to X robots in Y environment." Communication clarity matters — you'll whiteboard architecture decisions in front of the team.

Follow up at day five; don't ghost the process

The median application gets zero reply. One follow-up at day five roughly doubles response rates. Email the founder who replied (or the generic hiring alias) with a one-paragraph value add referencing their public deployments or technical challenges. That signals you've done the homework and can contribute immediately.

Clarify location expectations early

Interview Query notes remote flexibility exists for experienced engineers, but roles involving hardware integration or on-site robot testing require Boston presence. All six current openings list Boston, MA. If you're not local, address relocation timeline in the first screen; don't waste a Final Round onsite only to discover a mismatch.

The acceptance rate is low single digits; differentiate on deployment reality

Interview Query estimates the software engineer acceptance rate in the low single digits. Candidates with direct robotics/SLAM experience move faster. If your background is adjacent (computer vision, controls, embedded systems), bridge the gap explicitly: "I haven't run SLAM on a fleet, but I've shipped real-time perception on edge GPUs under 30W — here's how I'd validate the navigation stack in simulation before hardware bring-up." That translation layer is what a sub-50 team needs.

Scope and Kicker

This article examines the six open roles at Nextera Robotics and the hiring process candidates face. It does not cover the product roadmap, the company's financials, or the broader construction robotics market. The Didge platform — autonomous robots that capture site data daily, AI that processes it into progress, safety, and quality insights, integrations with Procore, Autodesk, and Oracle tools — is the context for these roles. But this article does not analyze Didge's architecture, its computer-vision pipeline, its Bluetooth mesh networking, or its roadmap toward "infinitely scalable Construction Intelligence." Those details appear in Oshkosh Corporation's August 2026 announcement of its strategic equity investment, in JLG's field-validation statements, and on the Didge.ai site. They inform why the six roles exist. They are not the subject here.

Financials are similarly outside the boundary. The Oshkosh investment amount, the terms of the JLG commercialization support, Nextera's $5M ARR figure from getlatka.com (dated August 2026), the $9.5M Series A reported by fundup.ai for 2026, the bootstrapped history prior to that round: none are analyzed. The article does not assess runway, valuation, or capital structure.

Broader market trends are excluded. The construction robotics landscape (Haulotte's work with Builder Assist, JLG's boom-lift concept with a robotic end effector, the industry shift toward connected job sites Jay Iyengar described at Oshkosh) provides background. So does the iRobot Chapter 11 filing in February 2026, tariff pressures on Vietnamese manufacturing, the collapsed Amazon acquisition. These signals matter for the sector. They do not change what a candidate must demonstrate to pass Nextera's screening.

The founders (Lana Graf, Alex Rand, Alex S. Rand) and the MIT origin story appear in the research. Their backgrounds, the Y-Combinator connection, the 2020 founding date: not covered. The article does not profile leadership or trace company history.

Culture and work-life balance are addressed in Section 5 through employee insights. Application strategy belongs to Section 6. The screening funnel stages belong to Section 2. The candidate profile belongs to Section 3. The six roles themselves (what they are and what they signal about technical priorities) belong to Section 1.

If a reader wants to know whether Didge's autonomous navigation stack uses visual-inertial odometry or lidar SLAM, whether the Oshkosh investment includes a board seat, whether the $5M ARR reflects recurring SaaS or hardware-plus-software contracts, how Nextera's salary bands compare to Boston Dynamics or Amazon Robotics, this article will not answer. It answers a narrower question: what does it take to land one of these six roles?

The robots are already running second shift on the Kaye project in Seattle, capturing 360-degree frames while the site sleeps. Five minutes later, a safety alert lands on a superintendent's phone. The six open roles in Boston are the team that keeps that loop closed — night after night, site after site. The talent war isn't coming. It's the night shift.

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