Careers

Build the layerbetween softwareand molten metal.

In brief

Weldeon is a small, technical team building autonomy for a process that punishes hand-waving. If you want your work measured in first-pass yield rather than engagement, read on.

The work

Software that has to be right the first time

Most software fails softly. A retry, a rollback, an apology in a status page. Ours writes parameters to a machine depositing molten metal into a joint that will hold a bridge up for fifty years.

That changes how we build. Boundaries are enforced below the intelligence, not above it. Every action is recorded before the next one begins. Confidence is a first-class value, and 'we are not sure' is a supported outcome that stops a cell.

It also changes who enjoys it. People who like constraints, physical reality and being told plainly by a welding foreman that they are wrong tend to thrive here.

Team

How we work

Six practices we actually hold to.

On the floor

We scope, deploy and debug in fab shops. Assumptions die quickly there, which is the point.

Small teams, whole problems

An engineer owns a scope end to end — sensing, model, adapter and the number it moves.

Domain in the room

Welding and quality engineers sit inside product decisions, not downstream of them.

Written arguments

Design decisions are written down and argued in text before they are built.

Honest status

We label what is unknown internally with the same discipline we use externally.

Deep work

Meeting load is deliberately low. Physics does not respond well to context switching.

Roles

Open positions

All roles are hybrid with regular travel to customer fab shops. [PLACEHOLDER] — role detail and locations are confirmed in the first conversation.

  1. 01

    Perception engineer — welding

    Sensor fusion across laser tracking, through-arc sensing, thermal and vision to produce a metric joint estimate with honest uncertainty.

  2. 02

    Controls engineer — robotic welding

    Real-time parameter and motion control on the factory edge, inside a hard qualified envelope, at 20 ms.

  3. 03

    Welding engineer, product

    Own procedures, envelopes and code models. Translate D1.1, BPVC, ISO 3834 and EN 1090 into machine-enforceable constraints.

  4. 04

    Simulation engineer — distortion

    Physics-informed models for weld sequence, distortion and residual stress that run fast enough to plan a shift.

  5. 05

    NDT machine-learning engineer

    Radiographic and ultrasonic interpretation with calibrated confidence and an inspector genuinely in the loop.

  6. 06

    Deployment engineer

    Own integration weeks: controllers, sensors, MES, roles and the baseline that makes a scorecard mean something.

  7. 07

    Founding account executive

    Sell a paid pilot to a fabrication operations director on a scorecard, not a demo.

Hiring

The process, start to finish

Four conversations, about two weeks, no take-home marathon.

Intro
45 minutes on what you have built and what you want to build. Two-way from the start.
Technical depth
A conversation about a real problem in your domain — no algorithm trivia.
Working session
Two hours on an actual Weldeon problem, paid, with the engineer who owns that area.
Floor visit
Where possible, a fab-shop visit together. It is the fastest way for both sides to know.
Offer
Compensation, equity and level explained in full, with the reasoning behind the numbers.
Team

What we optimise for

Depth

few people, whole problems, long attention spans

Floor

regular time in customer fab shops for every engineer

Written

design decisions argued in text before code

Honest

unknowns labelled internally and externally

Team size, funding stage and specific locations are shared in the first conversation rather than published.

“Physics does not care how confident your model sounded.”
WeldeonA phrase used often, usually while reviewing a failed pass
Growth

What a first year looks like

Concrete, because vague career pages help nobody.

  1. 01

    Weeks 1–4

    Ship something small to a real cell, and spend at least one week in a fab shop watching people weld.

  2. 02

    Months 2–4

    Own a scope end to end — the sensing, the model, the adapter and the metric it is judged on.

  3. 03

    Months 5–8

    Lead an integration week at a customer site, including the parts that go wrong at 6am.

  4. 04

    Months 9–12

    Own a scorecard line publicly, in front of a customer, including the weeks it does not move.

Benefits

The practical things

[PLACEHOLDER] — final benefit detail confirmed at offer stage.

Equity for everyone

Meaningful ownership with the calculation explained rather than implied.

Real hardware

Access to cells, sensors and edge appliances. You cannot build this on a laptop alone.

Travel that matters

Fab-shop visits are funded and expected, not rationed.

Learning budget

Including welding certifications for engineers who want to actually understand the process.

Apply

Tell us what you would build

No cover letter. Tell us about a hard technical problem you owned end to end, and which of our roles it points at.

Questions

Career questions

Begin

Bring autonomy to thearc, the fit-up andthe inspection bay.

Book a pilot on one cell or line. We agree the scorecard before we start — first-pass yield, rework hours, defect escapes, takt — and we report against it in the open.