Careers

We build the machine
that builds software.

Meet the humans behind it.

We're not hiring software engineers. We're hiring factory builders. The product is automation itself.

Software development as we know it is becoming obsolete. We're building the infrastructure that will automate the entire development lifecycle — from idea to deployment. If that sounds impossible, you're thinking too small.

What makes this different

01

You work on the machine, not just the product.

Most agencies ship client work. Here, you build the automated system that ships client work. Client deliverables are the output. The real engineering challenge is the engine itself — the system that starts building before the night and delivers by morning.

02

AI-native means AI-native.

Not "we added Copilot." The entire methodology is built around AI agents — from proof of concept in Lovable to automated overnight builds with Claude Code and Cursor. If you're still writing code by hand, you're going to wonder why.

03

You'll build NeoGen.

Our malleable software engine. Software that end users can reshape through conversation. Per-tenant branches. AI-generated modifications validated before they ship. This isn't theoretical — we're building it with pioneering customers right now.

→ Learn more about NeoGen
04

Radical transparency starts with this page.

The first 3 months are in-person. High ambiguity. Fast pace. We're building something new — there is no playbook, and the people who thrive here are the ones who find that exciting, not stressful. We'd rather you know this now than discover it on day 30.

Before you apply

Four questions we ask every candidate

1

Can you build without a playbook?

Tell us about a time you solved something with no existing process or documentation.

A strong answer: A specific story with concrete actions. Created the process, didn't just follow one.

2

How do you actually use AI today?

Not theoretically — what's your daily workflow?

A strong answer: Uses AI to delegate, not just autocomplete. Can describe specific workflows.

3

What have you built outside of work?

Personal projects, open source, communities, businesses.

A strong answer: Has tangible things they created when nobody was watching.

4

Does high intensity excite you or just sound good on paper?

Our first 3 months are in-person, full-time, high ambiguity.

A strong answer: Enthusiasm, not just tolerance. Specific about what excites them.

A weak answer on any of these is a dealbreaker, regardless of technical strength.

Open role. Same mission.

01 Senior Software Engineer "The person who has lived the pain we're automating."

Why this role exists

Neo Carbone automates software development with AI agent loops. To automate the right things, we need someone who has lived the full reality of software engineering at scale — CI/CD pipelines breaking, pull request bottlenecks, flaky test suites, on-call rotations, painful migrations, configuration drift. The kind of experience that teaches you which problems are worth solving and which are symptoms of something deeper.

This person brings the judgment that only comes from years of shipping and maintaining production systems. They shape what we automate — and how.

What we're looking for

  • ✓ Production systems experience: Has shipped AND maintained systems with thousands of real users. Not just built MVPs — has managed migrations, breaking changes, tech debt decisions, and incident response over years.
  • ✓ Team-scale experience: Has worked in engineering teams of 10-30. Can articulate concretely what slows teams down: PR bottlenecks, unclear ownership, onboarding friction, environment inconsistencies. From experience, not theory.
  • ✓ Excited to become obsolete: Most senior engineers have ego tied to their craft. We want someone who sees agentic coding and thinks "finally" — not "it'll never work." Already using Claude Code, Cursor, or Copilot aggressively. Not as autocomplete — as delegation.
  • ✓ Architectural thinking: Can look at a codebase and identify invariant structure vs. accidental complexity vs. configurable surfaces. This maps directly to malleable software: what's the stable core, what's the modification surface, what should never change.
  • ✓ Self-directed: No manager setting priorities at this stage. Sees a gap and fills it.

Experience

~10 years

Salary

$100K-$130K + equity (1-3%)

Location

In-person 3mo (Montreal/Charny, QC), then hybrid

This isn't for you if:

  • ✗ You're comfortable only in large-company environments with defined processes
  • ✗ You talk about processes you followed but never ones you created or challenged
  • ✗ You can't explain WHY your team's practices existed, only WHAT they were
  • ✗ You're skeptical of AI tools without having seriously tried them

How to apply

No CV. Show us what you built.

Confirm you meet all requirements for this role. Review the qualifications, experience expectations, and culture fit criteria above. If any of these feel like a stretch rather than a match, this role isn't right for you — yet.

Send an email to career@neocarbone.ai with:

  1. 1.A link to one project you built — personal projects strongly preferred over assigned work
  2. 2.In 200 words or less: what problem does it solve, and what would you do differently today?
  3. 3.One sentence: what's the last thing you automated for yourself?
  4. 4.Explicitly confirm you meet every requirement listed and why you're a match for this role.

If you're wondering whether you're a fit — you'll know by whether these questions excite you or exhaust you. Applications that don't directly address the requirements will not receive a response.

Think you're a fit?

You'll know by whether these questions excite you or exhaust you. Show us what you built.

Apply → career@neocarbone.ai