Founding edge perception engineer
Jetson Orin, DeepStream, Holoscan, TensorRT. Fuse froth cameras, online analyzers and particle-size sensors into one live read of grade, recovery and froth condition at the bank.
Careers
Work on software that moves a reagent pump and a mill setpoint.
Orebex 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 circuit.
Illustrative scenario: Line 1 · SAG and ball circuit, rougher bank 2 · copper porphyry blend, one shift, one approval gate
Founding roles
Where we need people
Role descriptions, not an openings count. Each is a founding role.
Founding controls and OT integration engineer
Mill, flotation APC, DCS, reagent-dosing, dewatering and robot connectors. Guarded writes, interlocks, rollback and the audit log.
Founding simulation engineer
Omniverse concentrator twin, comminution and DEM, flotation and geometallurgy simulation, physics-informed surrogates with Modulus, cuOpt optimisation.
Founding metallurgist
Someone who has run a flotation or comminution circuit. Translate metallurgist craft into operating envelopes, reagent-scheme policy, metrics and acceptance tests for design partners.
How we work
Six things about working here
The plant is the customer
We measure ourselves on recovery points, kilowatt-hours per tonne, reagent per tonne and water per tonne, the plant's own numbers.
Nothing unlabelled
A design target is called a design target. A scenario is called a scenario. We do not round up.
Safety is a feature
The policy engine, approvals, interlocks and the audit log are the product, not overhead.
Simulate first
A move is rehearsed on the twin before it is written. So are our own changes.
Write it down
Every decision, every run, every correction goes into a record someone else can read.
Go to the plant
The craft we are encoding lives in the control room and on the flotation floor, often a long way from anywhere. We go there.
Run timeline · scenario
What you would be building
Every Orebex run is an ordered, inspectable sequence. This is run_4b9e27 on Line 1 · SAG and ball circuit, rougher bank 2 · copper porphyry blend. Scenario completes in 10 steps with one approval gate. P80 held at 148 µm as the blend hardened, froth stability recovered on rougher bank 2 after an air trim, a collector-dose change was approved by the shift metallurgist, predicted recovery held inside the plan, lot C-20931 released with full genealogy.
run_4b9e27
Line 1 · SAG and ball circuit, rougher bank 2 · copper porphyry blend
illustrative scenario
SUCCEEDED
-
01
ingest.shift
SUCCEEDED
0.7 s
Concentrator Orchestrator · Pulled the shift plan from the concentrator MES: copper porphyry blend B-14, P80 target 150 µm, concentrate grade at or above 25% Cu, recovery target per the geometallurgy model, energy and water budgets. Locked the operating envelope for the blend.
-
02
twin.simulate
SUCCEEDED
58 s
Concentrator Twin · Simulated 32 candidate grind, air and reagent schemes on the as-run twin for the hardening blend, ranked on predicted recovery, concentrate grade, kWh per tonne and water per tonne. Two candidates breached the thickener bed limit and were discarded.
-
03
grind.setpoint
SUCCEEDED
3 m 40 s
Crush-and-Grind · SAG-1 feed trimmed 3% and cyclone water raised as load and power signatures read a harder feed. P80 from the particle-size analyzer held at 148 µm against the 150 µm target; mill power stayed inside the energy budget.
-
04
froth.read
SUCCEEDED
continuous
Grade-and-Froth · Twelve froth cameras and the online XRF on rougher bank 2 fused at the edge. Froth stability on cells 3 and 4 fell as the blend hardened; predicted recovery drifted 0.4 points below plan. Early warning published to the control agents.
-
05
approve.human
APPROVAL
1 m 12 s
Concentrator Orchestrator · Scheme #7 raises collector dose 6% on rougher bank 2, above the standing reagent scheme. Reagent-scheme changes stay supervised on this blend, so the step was held for the shift metallurgist and approved at 07:19:44.
-
06
float.dose
SUCCEEDED
2 m 05 s
Float-and-Reagent · Approved collector dose applied with an air trim of 4% down on cells 3 and 4 inside the envelope. Froth stability recovered within eight minutes; predicted recovery returned to plan with concentrate grade read at 25.6% Cu.
-
07
classify.cyclone
SUCCEEDED
42 s
Separate-and-Classify · One cyclone brought online in cluster 1 as feed density rose with the hardness change, holding overflow size and circulating load inside the plan.
-
08
dewater.thickener
SUCCEEDED
continuous
Thicken-and-Dewater · Tailings thickener TH-2 flocculant dose trimmed as bed pressure rose; underflow density held and overflow clarity stayed inside the water-recovery target.
-
09
optimise.targets
SUCCEEDED
18 s
Throughput-and-Recovery · Whole-plant targets recomputed for the hardened blend: feed rate, P80, air and reagent targets handed to the control agents with recovery, grade, energy and water inside the budget. The losing candidates and their scores are in the run record.
-
10
lot.release
SUCCEEDED
1 m 30 s
Quality-and-Conformance · Concentrate lot C-20931 released: genealogy written (blend, grind record, reagent and air moves, froth and grade reads, approvals, dewatering record, assays as they land) and dispositioned against the concentrate spec with cited evidence for the metallurgist's sign-off.
Process
How hiring runs
- Write to us. What you would own, what you have built or run, and why the concentrator.
- A conversation. An hour on the problem, not a quiz.
- A working session. A real design question from the backlog, worked together.
- References and an offer. Founding terms, discussed openly.
Accelerated computing
Physical AI, at the bank and the mill
Froth changes in seconds and a shift of feed is gone before the assay lands. Perception has to be local, deterministic and fast, so Orebex runs GPU inference at the plant edge and keeps training, simulation and optimisation in the cloud or on-prem.
Edge perception
8 to 24 froth cameras per bank at 15 to 30 FPS plus online XRF, particle-size, pump, level, air, reagent, density and energy streams fused at the plant edge. Sub-250 ms froth inference and local fail-safe through a network outage are the design targets. Jetson Thor is planned.
Model serving
Froth, particle and mineralogy, recovery prediction, time-series anomaly and metallurgy retrieval models behind one orchestrator at the plant edge, 20 to 60 per site as a design target, with versioned canaries and rollback.
Training
Froth segmentation, bubble velocity and stability, grade and recovery prediction, ore hardness, grind-size response, reagent response and metallurgy assistants trained on froth video, analyzer readings, telemetry and metallurgist corrections. 2,000 to 8,000 GPU-hours per commodity model family is the design target once partner data exists.
Concentrator twin
Grinding, flotation, classification and dewatering simulated as-run against as-designed before the shift. GPU comminution and DEM, flotation and geometallurgy simulation is the workload; physics-informed surrogates with Modulus are planned so schemes rank at production cadence.
Synthetic data
Rare froth-collapse, feed-upset, mineralogy-shift, equipment-drift and camera-fouling cases generated and validated against real assay distributions before promotion. 50k to 250k scenarios per commodity and circuit class is the design target.
Optimisation
Throughput, energy, water and reagent allocation and the grade and recovery trade-off solved before the shift and during upset recovery, and handed to the control agents as targets.
Robot sampling and handling
Sampling routes, reagent tote inspection and inspection rovers trained and validated in simulation before they run on site. Assistive until the safety case is proven.
GPU ETL
Daily features from froth, analyzer, mill, flotation, dewatering and genealogy telemetry for retraining, drift detection and recovery, energy, water and reagent benchmarks.
Autonomy
Four levels, set per agent and per tag
A concentrator does not go from manual to unattended in one step. Orebex 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 grinding and flotation loops. Reagent-scheme changes stay supervised until the ore type is characterised.
| Level | What the agent does | What the human does | Where it sits in a pilot |
|---|---|---|---|
| L1 · Shadow | Reads froth, analyzer, particle, mill, flotation, dewatering, robot and MES signals; predicts and recommends; writes nothing | Runs the circuit as today; compares predictions to assays and metallurgist outcomes | Shadow mode, baseline measured first |
| L2 · Assist | Proposes grind, reagent, air, froth and dewatering moves with evidence, confidence, envelope and rollback path | Approves each action in the review console | Assist mode, the remainder of a 90 to 120 day pilot |
| L3 · Bounded | Executes pre-approved low-risk grinding and flotation loop moves: feed, water, air, level, flocculant, cyclones online, inside APC, DCS and envelope limits | Approves reagent-scheme changes and lot release | Graduated autonomy, after audited accuracy and ROI |
| L4 · Constrained auto-control | Supervised reagent-scheme adaptation for characterised ore types, across circuits and sites | Sets the envelope; reviews the shift record and the evaluation results | Planned; after golden-dataset evaluation, twin validation and metallurgist sign-off |
Guardrails
An agent that can move a reagent pump needs a leash
Orebex writes to production equipment. Every capability is scoped, every write is policy-checked against the operating envelope, 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 operating envelope for the blend.
- Policy engine before every write. Autonomy level, shift, ore type, interlock state, water and tailings constraints and metallurgist policy are evaluated before a setpoint moves.
- Human-in-the-loop gates. Reagent-scheme changes and lot release wait for a named approver. Robotics stays assistive until the site safety case is proven.
- Immutable audit log. Append-only and exportable. Every action records source evidence, the envelope applied, confidence, estimated recovery, grade, energy, water and reagent impact, rollback path, approver and lot scope.
- Hard fallback. Loss of the edge node, the network or a model returns control to the APC or DCS last known-good state. Interlocks are never in Orebex's path, and the edge runs fail-safe through a network outage.
- Tenant and ore-body isolation. Ore-body data, geometallurgy models, reagent schemes and recovery records never cross a customer boundary. On-prem and edge deployment is available for remote sites.
Compliance posture
| Item | Scope | Status |
|---|---|---|
| SOC 2 Type I | Cloud control plane | QUEUED Planned, first 6 months |
| SOC 2 Type II | Cloud control plane | QUEUED Planned, 6 to 12 months |
| SSO and RBAC | Console and approvals | QUEUED Planned, 6 to 12 months |
| Environmental and water assurance packages | Recovery, energy, water and tailings evidence | QUEUED Planned, 6 to 12 months; not a certification claim |
| Standards-cited reasoning | ISO, ICMM, tailings and water governance documents | RUNNING In the design, every answer cites its source |
| Per-tenant and ore-body isolation | Ore data, schemes, models, memory | RUNNING In the design from day one |
| On-prem and plant-edge deployment | Remote and IP-sensitive sites | RUNNING Design option |
FAQ
Straight answers
The questions processing managers, metallurgists and sustainability leads ask in the first meeting.
Yes, but only within an explicit tag allow-list with per-tag rate and magnitude limits, inside the operating envelope for the blend, and only at the autonomy level your plant has set. Design partners start in shadow mode, where Orebex writes nothing. Reagent-scheme changes stay supervised by a named metallurgist until the ore type is characterised.
Control returns to the APC or DCS last known-good state. Orebex is a supervisory layer on top of the control systems and interlocks you already run, never a replacement for them, so an outage degrades the circuit to its current way of running, not to a stop. The edge is designed to run fail-safe through a network outage.
Advisory recommendations start from the twin and the shift plan in the first weeks. Froth, grade, recovery and grind-response prediction improve as circuit history and assay-labelled outcomes accumulate per ore type. The compute plan sizes training at 2,000 to 8,000 GPU-hours per commodity model family once partner data exists, a design target.
Only if you choose cloud training. Ore-body data, geometallurgy models, reagent schemes, process models and recovery records are isolated per tenant and never used to train another customer's models. A fully on-prem deployment at the plant edge is available for remote and IP-sensitive sites, and federated learning across sites is planned and waits on data-rights agreements.
You are, the same as with any control strategy, which is why every write is policy-checked, bounded, logged and reversible, and why anything above your risk threshold waits for a named approver. The audit log records the request, the evidence, the envelope applied and the human decision.
A paid pilot of 90 to 120 days on one grinding or flotation circuit, scoped to a single wedge with a success metric written into the order form: recovery gain, energy per tonne saved, water reduction or reagent per tonne. The first weeks baseline recovery, energy and water in shadow mode from your own assays and meters.