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.
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