Careers

Work on software that decides a weld schedule, then waits for a human.

Chassira 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_41a9c2 · agent graph · plant BIW-2 · scenario 10 nodes · 1 approval gate
01 · orchestrator ingest.shift ✓ SUCCEEDED 02 · vehicle_line twin.simulate ✓ SUCCEEDED 03 · stamp_form stamp.form ✓ SUCCEEDED 04 · orchestrator approve.human ◆ APPROVAL 05 · weld_join weld.join ✓ SUCCEEDED 06 · frame_geometry frame.geometry ✓ SUCCEEDED 07 · paint_finish paint.finish ✓ SUCCEEDED 08 · powertrain_battery marriage.torque ✓ SUCCEEDED 09 · quality_anomaly inspect.fuse ✓ SUCCEEDED 10 · eol_calibrate eol.release ✓ SUCCEEDED

Illustrative scenario: Plant BIW-2 · EV crossover body shop to end of line · shift 1, 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 seam, gap-and-flush and paint-defect cameras, weld and torque traces and metrology into one model of build quality at the cell.

Founding role · 02

Founding controls and OT integration engineer

Robot, press, paint, torque, test-stand and MES connectors. Guarded writes, safety-rated PLC boundaries, interlocks, rollback and the audit log.

Founding role · 03

Founding simulation engineer

Omniverse plant twin, weld-thermal and geometry FEA, stamping and springback, paint-flow and structural surrogates, cuOpt sequencing.

Founding role · 04

Founding body, paint or assembly process engineer

Someone who has launched a body shop, a paint shop or a general-assembly line. Translate launch-engineer craft into process windows, metrics and acceptance tests for design partners.

How we work

Six things about working here

01

The plant is the customer

We measure ourselves on rework per body, repaint rate, downtime minutes and first-time-through, the plant'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, locked parameters, 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.

06

Go to the line

The craft we are encoding lives on the floor, next to the robots. We go there.

Run timeline · scenario

What you would be building

Every Chassira run is an ordered, inspectable sequence. This is run_41a9c2 on Plant BIW-2 · EV crossover body shop to end of line · shift 1. Scenario completes in 10 steps with one approval gate. Weld schedule change on robot W-14 approved by the body-shop launch engineer, framing offset held inside the envelope, booth humidity trimmed before the predicted dirt defects appeared, one pack held at marriage on a torque trace, and the shift released with full as-built records.

run_41a9c2 Plant BIW-2 · EV crossover body shop to end of line · shift 1 illustrative scenario SUCCEEDED
  1. 01 ingest.shift SUCCEEDED 0.8 s

    Plant Orchestrator · Pulled the shift build sequence, program control plan and qualified envelopes from MES: 412 bodies, four trim variants, weld schedule set W-rev 7, framing targets per station, paint colour blocks, torque specifications. Locked every safety-critical parameter as read-only.

  2. 02 twin.simulate SUCCEEDED 1 m 40 s

    Vehicle-and-Line Twin · Simulated 18 candidate weld-sequence, framing-offset and booth-window combinations on the plant twin, ranked on predicted body geometry, expulsion risk at robot W-14, paint defect map and takt against launch cadence.

  3. 03 stamp.form SUCCEEDED continuous

    Stamp-and-Form · Blank feed on press line P-3 adjusted by 0.4 mm and lubricant dose raised 3 percent for the new coil lot as springback risk on the rear door inner climbed. Panel dimension held inside the window; genealogy handed to framing.

  4. 04 approve.human APPROVAL 3 m 12 s

    Plant Orchestrator · Candidate #6 lowers weld current 2 percent and adds 20 ms hold on robot W-14 to cut predicted expulsion. Weld schedules are crash-safety critical and stay with a human, so the change was held for the body-shop launch engineer and approved at 06:14:52.

  5. 05 weld.join SUCCEEDED continuous

    Weld-and-Join · Approved schedule 7b applied on W-14. Current and force traces confirmed inside the window on the first 40 bodies; predicted expulsion risk fell from 0.31 to 0.06 and no geometry debt was introduced at the adjacent seams.

  6. 06 frame.geometry SUCCEEDED continuous

    Frame-and-Geometry · Framing station FS-1 offset corrected by 0.3 mm on the left B-pillar datum inside the qualified envelope as in-line measurement trended toward the tolerance edge. Gap-and-flush vision confirmed the correction on the next 25 bodies.

  7. 07 paint.finish SUCCEEDED continuous

    Paint-and-Finish · Booth B-2 humidity trimmed 2 points and airflow rebalanced for the dark-colour block as the defect model predicted dirt on horizontal panels. Film build held inside the window on the first colour block.

  8. 08 marriage.torque SUCCEEDED continuous

    Powertrain-and-Battery · Pack PK-1182 held at marriage after a torque-to-yield trace on fastener 7 fell outside the specification curve. Routed to rework with the trace attached; torque specification untouched, as always.

  9. 09 inspect.fuse SUCCEEDED continuous

    Quality-and-Anomaly · Gap-and-flush and paint-defect cameras, weld and torque traces and test results fused per body. Two paint dirt defects localised to booth B-2 zone 3 before the humidity trim took effect; both routed to spot repair, none escaped to final.

  10. 10 eol.release SUCCEEDED 2 m 05 s

    EOL-and-Calibrate · End of line proved alignment, ADAS calibration, leak, brake, roll and functional tests on every vehicle; two ADAS retests sequenced inside takt. Shift 1 released with as-built records, approvals and dispositions written for the quality lead.

Process

How hiring runs

  1. Write to us. What you would own, what you have built or launched, and why the car plant.
  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 line

A spot weld lasts a fraction of a second and a body passes a station every minute. Perception has to be local, deterministic and fast, so Chassira runs GPU inference at the plant edge and keeps training, simulation and optimisation in the cloud or on-prem.

Jetson Orin · DeepStream · Holoscan · TensorRT

Edge perception

8 to 32 cameras per process area at 15 to 60 FPS, plus torque, dimensional, thermal, robot and paint-instrument streams fused at the cell. Weld and gap alerts under 50 ms and paint or dimensional prompts under 150 ms are the design targets. Jetson Thor is planned for higher density.

Triton · NIM

Model serving

Weld-defect, geometry-risk, paint-risk, torque and battery, and takt-risk models served at the plant edge with versioned rollback, routed by latency, tenant and cost, with canary rollout by line.

DGX or HGX · NeMo

Training

Weld, paint and gap vision, dimensional models, NeMo IATF and spec reasoning and GPU-accelerated stamping, springback and weld-geometry FEA surrogates. 150 to 600 GPU-hours per plant during onboarding, then monthly retraining from engineer corrections. Dedicated capacity is planned.

Omniverse · OVX

Plant twin

Body framing, weld sequence, robot reach, paint flow and line balance simulated before the shift. The pattern is production proven at BMW and Mercedes-Benz, per the architecture; Chassira's twin and OVX capacity are planned.

Cosmos · Omniverse Replicator

Synthetic data

Rare weld defects, paint failures, geometry-drift modes, occluded joints and misbuild cases generated and validated against real distributions before promotion. 50,000 to 250,000 variants per program is the design target. Planned.

cuOpt

Optimisation

Line sequencing and JIS feeding, AGV routing, takt, line balancing, buffers and retest sequencing.

Isaac · Isaac ROS

Robot cells and AMRs

Robotic weld, paint, assembly and inspection cells and AGV and AMR line-feed autonomy, with skills validated in simulation before a cell runs them.

RAPIDS

GPU ETL

Telemetry ETL across weld and press parameters, measurements, paint readings, torque traces, battery and ADAS results, non-conformance and takt history for retraining and benchmarks.

NeMo Guardrails · NVIDIA AI Enterprise

Policy and deployment

Spec, IATF, functional-safety, cyber and human-approval policy enforced before any write; supportable on-prem or plant-edge deployment for regulated OEM plants.

Autonomy

Four levels, set per agent and per tag

A car plant does not go from manual to unattended in one step. Chassira makes the level explicit, auditable and reversible at any time. The first release runs shadow mode, then assist mode, then bounded autonomy on low-risk loops. Weld schedules stay supervised until the joint family is qualified, and torque specifications and test verdicts are never written by an agent.

Autonomy levels and the human role at each
LevelWhat the agent doesWhat the human doesWhere it sits in a pilot
L1 · ShadowReads weld, metrology, vision, torque, test, robot and MES signals; predicts and recommends; writes nothingRuns the line as today; compares predictions to audit and engineer outcomesDesign partners start here; the baseline is measured from the plant's own records
L2 · AssistProposes weld, framing, paint, routing, holding and sequencing moves with evidence, confidence, envelope and rollback pathApproves each action in the review consoleAssist mode: accuracy and ROI proven against the signed baseline
L3 · BoundedExecutes pre-approved low-risk actions: booth environment, framing offsets, blank feed and lubrication, routing, holds, sequencing, inside PLC and safety limits and the qualified envelopeApproves weld-schedule changes, torque-related decisions and vehicle releaseGraduated autonomy, after audited accuracy and ROI
L4 · ScaledSupervised weld-schedule adaptation for qualified joint families, across lines and plantsSets the envelope; reviews the shift record and evaluation resultsPlanned; after golden-dataset evaluation, twin validation and quality sign-off. Torque specifications and test verdicts never leave human hands
Guardrails

An agent near a crash-safety joint needs a leash

Chassira writes to production equipment. Every capability is scoped, every write is policy-checked against the qualified envelope, safety-critical parameters are locked, and every action is written to an append-only audit log the plant owns.

  • Bounded action space. Each agent writes only to an explicit tag allow-list, inside per-tag rate and magnitude limits and the qualified process envelope for the joint family, colour block or vehicle program.
  • Policy engine before every write. Autonomy level, shift, program, interlock state and operator presence are evaluated before a setpoint moves. NeMo Guardrails enforces spec, IATF, functional-safety, cyber and human-approval policy before any action writes back to robots, MES, QA or work instructions.
  • Safety-critical parameters locked. Weld schedules wait for a named body-shop engineer until the joint family is qualified. Torque specifications, battery-joint parameters and end-of-line test limits and verdicts are read-only to every agent, always.
  • Immutable audit log. Append-only and exportable. Every action records source evidence, the approved envelope, confidence, estimated quality, rework, downtime and warranty impact, rollback path, approver and vehicle scope.
  • Hard fallback. Loss of the edge node, the network or a model returns control to the press, robot, booth or MES controller's last known-good state. Safety-rated PLCs and interlocks are never in Chassira's path.
  • Tenant and program isolation. Vehicle designs, control plans, specs, models and memory never cross an OEM boundary. On-prem and plant-edge deployment are available for regulated plants.

Compliance posture

Compliance and certification status
ItemScopeStatus
SOC 2 Type ICloud control plane QUEUED Planned, first 6 months, with an IATF and functional-safety-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
IATF 16949 and APQP assurance packagesDisposition and traceability evidence QUEUED Planned, 6 to 12 months; not a certification claim
ISO 26262-aware controlFunctional-safety requirements cited in reasoning and gates RUNNING In the design; not a certification claim
Standards-cited reasoningIATF 16949, APQP and PPAP, torque specs, recall procedures RUNNING In the design, every answer cites its source
Per-tenant and program isolationDesigns, control plans, models, memory RUNNING In the design from day one
On-prem and plant-edge deploymentRegulated OEM plants RUNNING Design option

Read the security overview

FAQ

Straight answers

The questions plant managers, launch engineers and quality 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 envelope, and only at the autonomy level your plant has set. Design partners start in shadow mode, where Chassira writes nothing. Weld-schedule changes wait for a named body-shop engineer, and torque specifications, battery-joint parameters and end-of-line test limits and verdicts are read-only to every agent, always.

Get started

Tell us what you want to own

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