Skip to content

(nai™ — 01)

Build With Nukes

A closer look at how we work, what we value,
and the people building thoughtful automation
here inside Nukes AI.

Join
Our Team (@)

A plumb line hanging true against the work

(nai™ — 02)

Our Culture

What
Drives Us

We build systems that work under real pressure — and we expect the same from the people who build them.

We do not hire for hype or titles. We hire people who think clearly, take responsibility, and care about the outcome.

Working here means building systems that have to function under pressure — inside real teams, real constraints, and real timelines.

(nai™ — 03)

How You Work

Small team, real ownership, and no layers in between

There is no shadowing period and no account
layer. You own a surface from the first week.

Day one

You own a surface

No warm-up period. You take a piece of the build and it is yours.

Every build

You talk to the client

Nobody relays your questions. You ask them and you answer them.

Every week

You ship to real use

Work goes to people who depend on it, not into a demo branch.

Every call

You can say no

Refusing a bad idea early is the job. Nobody here is paid to agree.

(nai™ — 04)

How We Work

                Smart people.
Real problems. Clear execution. You’ll have the space to think and the freedom to build.

We care less about performance theater and more about thoughtful execution. At Nukes AI, people are trusted to solve hard problems, challenge assumptions, and build systems that hold up over time.

Nukes AI
How we staff a build

One ring drawn around every zone — a single team across all of them

WEEKLY / ONE CALL, EVERY TIME ZONE

The only meeting nobody is allowed to skip.

A clear surface handed over for someone to work on

EVERY BUILD / ONE ENGINEER, ONE SURFACE

Nobody shadows. You own a piece from day one.

A part measured before it is opened up

BEFORE ANY CODE / THE AUDIT COMES FIRST

We map how the work runs before agreeing what to build.

Inside Nukes AI

0:40 sec film

Hiring

Applied to decided

From first message

Predictability over heroics.

Systems beat intuition — every time.

  • The AI automation practice mark

    AI

    Automation

  • The custom software practice mark

    Custom

    Software

  • The commerce practice mark

    Shopify

    Hydrogen

4 practices

Pick the one you belong in

Bench

Senior Only

Of the engineers on a build

Build systems that hold up next to people who care

Work with people who value clarity, ownership and execution.

VIEW OPEN ROLES

(nai™ — 05)

Open Roles

Open Roles

We’re looking for people who can think clearly, take ownership, and build systems that hold up in real environments.

We hire people who can say no to a bad idea in week one. That turns out to be much rarer than another framework on a CV.

The commerce practice mark

Nukes AI

What we screen for

© ‒ 001.

AI Automation Engineer

Job Description:

Map how an operation actually runs, then build the agents and pipelines that carry the repetitive half of it, day after day.

Requirements

Trace business processes and find the real bottleneck

Ship with LLM APIs, retrieval and agent orchestration

Design guardrails, escalation and human-in-the-loop

Instrument decisions so accuracy can be checked later

© ‒ 002.

Full-Stack Engineer

Job Description:

Build the internal tools, APIs and platforms a business runs its operations on — typed end to end, tested where it counts.

Requirements

Strong TypeScript, React and Next.js App Router

Design schemas, services and API boundaries

Work confidently with SQL, queues and integrations

Take a surface from scoping through to production

© ‒ 003.

Shopify Hydrogen Engineer

Job Description:

Move stores onto headless Hydrogen and keep them fast — where the speed of the page is the conversion rate.

Requirements

Shipped Shopify Hydrogen or Remix storefronts

Comfortable across Liquid, themes and the Admin API

Hold Core Web Vitals under real sale traffic

Migrate catalogue and checkout without losing data

© ‒ 004.

Mobile Engineer (React Native)

Job Description:

Ship iOS and Android for people working away from a desk, built for the worst signal the job will ever see.

Requirements

Shipped React Native apps to both app stores

Design offline state, conflict handling and resync

Drop into native code when the bridge is not enough

Own release, signing and staged rollout

(nai™ — 06)

Hiring Process

A clear process — no surprises, no guessing.

We keep the hiring process structured and straightforward — focused on real skills, clear thinking, and how you approach problems in practice.

001.

Application Review

We review your background,
experience, and how you approach problem-solving.

Timeframe:

24–48 HOURS

002.

Intro Conversation

A short call to understand
how you work, and whether our ways of working align.

Timeframe:

30–45 MIN

003.

Practical Task

You will work through a
real scenario from the role — clarity and execution.

Timeframe:

2–4 HOURS

004.

Final Interview

A deeper conversation about
decisions, trade-offs, and how you work in practice.

Timeframe:

45–60 MIN