Careers

Work on software that decides a weld on a hull that will be at sea for thirty years.

Hullira is pre-launch and building its founding team. The four roles below are the ones we expect to open first, written as honestly as we can about the stage: there is no office to show, no customer list, and the first job is a paid pilot on one process.

4 founding rolesPre-launchEdge, OT, simulation, process

run_4b7e19 · agent graph · block B-214 · scenario 10 nodes · 1 approval gate
01 · orchestrator ingest.package ✓ SUCCEEDED 02 · aligna twin.simulate ✓ SUCCEEDED 03 · cut_profile cut.nest ✓ SUCCEEDED 04 · panel_weld weld.sequence ✓ SUCCEEDED 05 · orchestrator approve.human ◆ APPROVAL 06 · quality_anomaly inspect.fuse ✓ SUCCEEDED 07 · fair_form fair.lineheat ✓ SUCCEEDED 08 · blast_coat coat.window ✓ SUCCEEDED 09 · schedule_yard dock.reoptimise ✓ SUCCEEDED 10 · erect_align erect.align ✓ SUCCEEDED

Illustrative scenario: Block B-214 · double-bottom block · panel line PL-2 · dock D1, one block, one approval gate

Founding roles

Where we need people

Role descriptions, not an openings count. Each is a founding role.

Founding role · 01

Founding edge perception engineer

Jetson Orin, DeepStream, Holoscan, TensorRT. Fuse weld-pool and seam cameras, UT and X-ray, coating cameras and laser scans into one estimate of weld, coating and dimensional quality at the yard edge.

Founding role · 02

Founding controls and OT integration engineer

Welding-robot, CAD/CAM, coating-cell, crane and yard-MES connectors. Guarded writes inside the WPS envelope, interlocks, rollback and the audit log.

Founding role · 03

Founding simulation engineer

Omniverse ship and yard twin, weld-thermal and distortion FEA surrogates with Modulus, point-cloud registration, cuOpt dock and crane sequencing.

Founding role · 04

Founding welding or accuracy-control engineer

Someone who has run a panel line or an accuracy-control team. Translate shipwright and welder craft into WPS envelopes, tolerances, metrics and acceptance tests for design partners.

How we work

Six things about working here

01

The yard is the customer

We measure ourselves on rework, fairing hours, coating non-conformance and dock days, the yard's own numbers.

02

Nothing unlabelled

A design target is called a design target. A scenario is called a scenario. We do not round up.

03

Safety is a feature

The policy engine, approvals, interlocks and the audit log are the product, not overhead.

04

Simulate first

A move is rehearsed on the twin before it is written. So are our own changes.

05

Write it down

Every decision, every run, every correction goes into a record someone else can read, including the surveyor.

06

Go to the yard

The craft we are encoding lives on the panel line and in the dock. We go there.

Run timeline · scenario

What you would be building

Every Hullira run is an ordered, inspectable sequence. This is run_4b7e19 on Block B-214 · double-bottom block · panel line PL-2 · dock D1. Scenario completes in 10 steps with one approval gate. Predicted distortion at the erection joint fell from 4.2 mm to 1.8 mm after a back-step sequence, one porosity precursor on seam S-31 was cleared inside the WPS envelope, the ballast-tank coat ran inside a 3.4 °C dew-point margin, and the block landed at 1.6 mm with its conformance record written.

run_4b7e19 Block B-214 · double-bottom block · panel line PL-2 · dock D1 illustrative scenario SUCCEEDED
  1. 01 ingest.package SUCCEEDED 0.8 s

    Yard Orchestrator · Pulled the work package for B-214 from the yard MES: 46 plates, 212 seams under WPS-117, erection tolerance 2 mm at the D1 joint, PSPC-grade ballast-tank coating, erection slot on D1 in the dock plan. Locked the qualified WPS envelope and the class scope.

  2. 02 twin.simulate SUCCEEDED 1 m 12 s

    Ship Twin · Simulated 18 candidate weld sequences on the as-built twin with the weld-thermal surrogate, ranked on predicted distortion at the erection joint, crane reach on D1 and shift takt. Standing sequence predicts 4.2 mm; candidate #6 predicts 1.8 mm.

  3. 03 cut.nest SUCCEEDED 3 m 40 s

    Cut-and-Profile · Released the nest for 46 plates on CL-1 with the fit-up gaps candidate #6 assumes. As-cut geometry logged per plate and handed to the panel line; material yield 91.4% against the nest plan.

  4. 04 weld.sequence SUCCEEDED 2 m 05 s

    Panel-and-Weld · Loaded the back-step sequence for the non-critical seams on PL-2 and set heat input and travel speed inside WPS-117. Weld-pool and seam cameras streaming on 12 channels.

  5. 05 approve.human APPROVAL 58 s

    Yard Orchestrator · Candidate #6 also re-orders two class-critical butt seams, S-31 and S-32. Sequence changes on class-critical seams stay with a human, so the step was held for the shift welding engineer and approved at 06:12:44.

  6. 06 inspect.fuse SUCCEEDED continuous

    Quality-and-Anomaly · Twelve weld cameras and the UT station fused at the yard edge. One porosity precursor on S-31 at 06:41 flagged and cleared by a 4% wire-feed trim inside the WPS-117 envelope; the joint was routed to UT and passed.

  7. 07 fair.lineheat SUCCEEDED 4 m 30 s

    Fair-and-Form · Post-weld scan registered against the twin: 2.1 mm at the erection joint. Two line-heating passes planned on the inner bottom and executed by the fairing crew; re-scan read 1.8 mm, inside the 2 mm tolerance.

  8. 08 coat.window SUCCEEDED continuous

    Blast-and-Coat · Ballast-tank blast and first coat scheduled to a window with steel temperature 3.4 °C above dew point. Dry-film thickness read 312 µm against a 280 µm minimum on the stripe coats; PSPC evidence assembled per area.

  9. 09 dock.reoptimise SUCCEEDED 41 s

    Schedule-and-Yard · Re-solved the D1 dock and crane plan with B-214 ready 6 hours early and a neighbouring block late: erection slot pulled forward one shift, crane G2 reassigned, no berth conflict. Planner approved the revised plan.

  10. 10 erect.align SUCCEEDED 1 h 48 m

    Erect-and-Align · Both blocks scanned on D1 and registered against the twin; fit predicted at 1.6 mm. Shimming guidance issued to the erection crew, block landed and welded out, final scan 1.6 mm. Conformance record written: welds, scans, coating readings, approvals and class evidence for B-214.

Process

How hiring runs

  1. Write to us. What you would own, what you have built or run, and why the yard.
  2. A conversation. An hour on the problem, not a quiz.
  3. A working session. A real design question from the backlog, worked together.
  4. References and an offer. Founding terms, discussed openly.
Accelerated computing

Physical AI, at the arc

A weld pool is decided in milliseconds and a dock waits by the hour. Perception has to be local, deterministic and fast, so Hullira runs GPU inference at the yard edge and keeps training, simulation and optimisation in the cloud or on-prem.

Jetson Orin · DeepStream · Holoscan · TensorRT

Edge perception

6 to 24 cameras per process area plus UT, X-ray, thermal, laser-scan, photogrammetry, robot and coating-instrument streams fused at the yard edge. Sub-50 ms weld alerts and sub-150 ms coating or scan prompts are the design targets. Jetson Thor is planned for higher camera density.

Triton · NIM

Model serving

Weld-defect, distortion-risk, coating-risk, point-cloud and schedule-risk models behind one orchestrator at the yard edge, versioned with rollback, routed by latency, tenant, sensitivity and cost.

DGX or HGX · NeMo

Training

Weld-defect vision, UT and X-ray classification, NeMo class-rule reasoning and weld-thermal FEA surrogates fine-tuned per tenant: 100 to 500 GPU-hours per yard during onboarding, then monthly retraining from engineer corrections and class outcomes. Dedicated training capacity is planned.

Omniverse · OVX · Modulus

Ship and yard twin

Block erection, weld sequence, robot reach, crane paths and yard layout simulated before the shift, as-built against as-designed. GPU weld-thermal and structural FEA is the workload; physics-informed surrogates rank plans at shift cadence.

Cosmos · Omniverse Replicator

Synthetic data

Rare weld defects, coating failures, distortion modes, occluded seams and erection misalignment cases generated and validated against real NDT and scan distributions before promotion. 50k to 250k variants per vessel class is the target. Planned.

cuOpt

Optimisation

Dock, crane and berth schedules, work-package sequencing, yard logistics and erection order, re-solved as progress changes.

Isaac · Isaac ROS

Robot cells and crawlers

Robotic weld, blast, coat and inspection cells and crawler or drone hull inspection, with paths validated in simulation before they run next to a hull.

RAPIDS

GPU ETL

Telemetry ETL across weld parameters, scans, NDT results, coating readings, non-conformance and schedule history, for retraining, drift detection and rework, dock-time and schedule benchmarks.

NeMo Guardrails · Retriever

Policy and grounding

WPS and PQR, class-rule, PSPC, cyber and human-approval policies enforced before any action writes back to robots, MES, QA or work packages; retrieval with citations and tenant isolation.

Autonomy

Four levels, set per agent and per tag

A yard does not go from paper travelers to unattended welding in one step. Hullira makes the level explicit, auditable and reversible at any time. The first release runs shadow mode, then assist mode, then supervised control on low-risk actions. Class-critical seam changes, lift plans and block release stay with named people.

Autonomy levels and the human role at each
LevelWhat the agent doesWhat the human doesWhere it sits in a pilot
L1 · ShadowReads weld, scan, NDT, coating, robot, crane and MES signals; predicts and recommends; writes nothingRuns the process as today; compares predictions to NDT and surveyor outcomesShadow mode; the baseline is measured from the yard's own records
L2 · AssistProposes weld, fairing, coating, routing and schedule moves with evidence, confidence, envelope and rollback pathApproves each action in the review consoleAssist mode, the remainder of the pilot
L3 · Supervised controlExecutes pre-approved low-risk actions: inspection routing, coating pauses when a window drifts, weld parameters inside the WPS envelope, robot path variants tested in simulationApproves class-critical seam changes, lift plans and block releaseGraduated autonomy, after audited accuracy and ROI
L4 · BoundedSupervised work sequencing and weld adaptation for qualified block types, across processes and yardsSets the envelope; reviews the shift record and the evaluation resultsPlanned; after class, yard and insurer acceptance is earned
Guardrails

An agent that can move a weld parameter needs a leash

Hullira writes to production equipment. Every capability is scoped, every write is policy-checked against the qualified WPS, class and PSPC constraints, and every action is written to an append-only audit log the yard owns.

  • Bounded action space. Each agent writes only to an explicit tag allow-list, inside per-tag rate and magnitude limits and the qualified WPS, coating, dimensional and schedule constraints for the block.
  • Policy engine before every write. WPS and PQR, class rules, PSPC, safety limits, role permissions, autonomy level and human-approval requirements are evaluated before a parameter moves. NeMo Guardrails is the design for this layer.
  • Human-in-the-loop gates. Class-critical seam changes, lift plans, block release and class evidence wait for a named approver. Robots adapt only inside pre-approved WPS envelopes until class, yard and insurer acceptance supports more.
  • Immutable audit log. Append-only, assurance-grade and exportable. Every action records source evidence, the WPS, class or PSPC citation applied, confidence, estimated rework, dock-time and schedule impact, rollback path, approver and block scope.
  • Hard fallback. Loss of the edge node, the network or a model returns control to the robot controller, PLC or planner's last known-good state. Interlocks are never in Hullira's path.
  • Tenant and defense-aware isolation. Drawings, WPS, naval data, models and memory never cross a customer boundary. Security is defense and ITAR-aware, and on-prem or yard-edge deployment is available for naval and regulated yards.

Compliance posture

Compliance and certification status
ItemScopeStatus
SOC 2 Type ICloud control plane QUEUED Planned, first 6 months, with a defense and ITAR-aware review
SOC 2 Type IICloud control plane QUEUED Planned, 6 to 12 months
SSO and RBACConsole and approvals QUEUED Planned, 6 to 12 months
Class-society and defense assurance packagesDisposition and genealogy evidence QUEUED Planned, 6 to 12 months; not a class approval or certification claim
Cited reasoningWPS and PQR, ABS, DNV, LR, ClassNK, IMO PSPC, naval specs RUNNING In the design, every answer cites its source
Per-tenant and IP isolationDrawings, WPS, naval data, models, memory RUNNING In the design from day one
On-prem and yard-edge deploymentNaval and regulated yards RUNNING Design option

Read the security overview

FAQ

Straight answers

The questions production directors, welding engineers and class-compliance leads ask in the first meeting.

Yes, but only within an explicit tag allow-list with per-tag rate and magnitude limits, inside the qualified WPS, coating, dimensional and schedule constraints, and only at the autonomy level your yard has set. Design partners start in shadow mode, where Hullira writes nothing. Class-critical seam changes, lift plans and block release stay with named people.

Get started

Tell us what you want to own

Write to hello@hullira.com with the role and what you have built.