Careers

Help us automate
software development

We are hiring engineers to build the AI agent system that develops our clients' software.

What we build

Our engineers build the system that delivers each client product

We are building the infrastructure that automates the software development lifecycle, from the first idea to deployment. We expect it to replace most hand-built development, and the people we hire build and improve that system.

  1. Idea
  2. Specification
  3. Build
  4. Review
  5. Deployment

How the work is organized

You build the system that delivers client work

Most agencies assign engineers to client projects. Here you build the automated system that delivers those projects, so client deliverables are its output and the engineering problem is the system itself, which starts a build overnight and delivers it by morning.

Our method is built around AI agents

Our whole development method runs on AI agents, from the proof of concept in Lovable to automated overnight builds with Claude Code and Cursor. Engineers who join should expect to delegate most code writing to agents, well beyond adding an assistant to a manual process.

You will build NeoGen

NeoGen is our malleable software engine: applications that end users change by describing the change in conversation. Each tenant runs on its own branch, and every AI-generated modification is validated before it ships. We are building it now with our first customers.

→ Learn more about NeoGen

What the first 3 months look like

The first 3 months are in person, at a fast pace and with a high degree of ambiguity. There is no established playbook for what we are building, so the role suits people who find that motivating. We describe it here so you can decide before you apply, not on day 30.

Before you apply

The 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, in which you created the process yourself.

2

How do you use AI in your daily work?

Describe a typical working day and the tools you use in it.

A strong answer: you delegate whole tasks to AI and can describe the specific workflows you use.

3

What have you built outside of work?

Personal projects, open source, communities, businesses.

A strong answer: concrete things you built on your own initiative, without anyone asking for them.

4

How do you work under high intensity?

The first 3 months are in person and full-time, with a high degree of ambiguity.

A strong answer: specific reasons this pace motivates you, beyond a willingness to tolerate it.

A weak answer to any of these questions ends the application, whatever the candidate's technical strength.

The open role

Senior Software Engineer An engineer with first-hand experience of the workflows our software automates.

Why this role exists

Neo Carbone automates software development with AI agent loops. To choose what to automate, we need an engineer who has worked through software engineering at scale: broken CI/CD pipelines, pull request bottlenecks, flaky test suites, on-call rotations, difficult migrations and configuration drift. That experience shows which problems are worth solving and which are symptoms of a deeper cause.

The role calls for judgment built over years of shipping and maintaining production systems, and the person in it will decide what we automate and how.

What we are looking for

  • ✓ Production systems experience: You have shipped and maintained systems with thousands of users, and over several years you have managed migrations, breaking changes, technical debt decisions and incident response, well beyond building MVPs.
  • ✓ Team-scale experience: You have worked in engineering teams of 10 to 30 people and can name, from your own experience, what slows them down: PR bottlenecks, unclear ownership, onboarding friction and inconsistent environments.
  • ✓ Committed to agentic coding: You welcome agents taking over work you used to do by hand, and you already use Claude Code, Cursor or Copilot heavily to delegate whole tasks, beyond autocomplete.
  • ✓ Architectural thinking: You can read a codebase and separate its invariant structure from accidental complexity and from the surfaces that should be configurable. That skill maps directly to malleable software, where we decide what forms the stable core, what users can modify and what must never change.
  • ✓ Self-directed: At this stage no manager sets your priorities, so you identify gaps and close them on your own initiative.

Experience

~10 years

Salary

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

Location

In person for 3 months (Montreal/Charny, QC), then hybrid

This role is not a fit if:

  • ✗ You work well only in large companies with defined processes
  • ✗ You can describe processes you followed, but none you created or challenged
  • ✗ You can describe your team's past practices, but not the reasons behind them
  • ✗ You doubt AI tools without having used them on real work

How to apply

Show us what you built, instead of a CV

Check that you meet every requirement for this role. Review the qualifications, experience expectations and culture fit criteria above. If any of them is a stretch for you, this role is not the right one yet.

Send an email to [email protected] with:

  1. 1.A link to one project you built. We give more weight to personal projects than to 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 on the last thing you automated for yourself.
  4. 4.A confirmation that you meet every listed requirement, with the reasons you are a match for this role.

Applications that do not address each requirement directly will not receive a response.

Send us one project you built

Email us a link to the project, your written answers and a confirmation that you meet each requirement listed above.