This is a .NET engineering role, not a JavaScript/AWS role. Deep C# / .NET is a hard requirement. AI/LLM-assisted development (building with Claude) is a hard requirement. Please read the skills grid before applying.
Why this role exists
nextSource is running Mission: Possible — an enterprise transformation onto a single source of truth, Elipsum Enterprise (a modern MACH architecture). Engineering today bottlenecks on one person. This role is the senior hands-on engineering counterpart to the CTIO — you own the platform, the release pipeline, and security; you lead the migration to .NET 10; and you build modules alongside Claude in an AI-augmented workflow.
What you'll own
- The platform. The Elipsum Enterprise codebase (ASP.NET MVC today → .NET 10), its data model, and its architecture decisions.
- The release pipeline. Build, migrations, staging-gated deploys, and the health checks that keep production safe.
- Security. Multi-tenant isolation, secrets, auth, and the controls that let us bill correctly and never leak one client's data to another.
- The .NET 10 migration. Strangler-fig from the legacy MVC app to a clean, modular .NET 10 architecture — no big-bang rewrite.
- AI-augmented delivery. Ship modules with Claude in the loop: you design the stations, the AI does the repetitive part, you own the gates.
Outcomes — what success looks like
This role is measured by outcomes, not activity.
- First 30 days: own the build + deploy pipeline end to end; one production release shipped by you, health-gated, with a clean rollback path.
- 60 days: the security baseline documented and the top tenant-isolation risks closed; a second engineer (or a Claude workflow) can deploy without you.
- 90 days: the .NET 10 migration plan agreed and the first module cut over behind a feature flag, with no regression to the legacy app.
- Year 1: Elipsum Enterprise runs on a modular .NET 10 core; engineering no longer bottlenecks on one person; release cadence is weekly and boring.
Skills grid — read before applying
Hard requirements (non-negotiable):
- Deep C# / .NET — you've owned non-trivial .NET systems in production (not bootcamp-level).
- AI/LLM-assisted development — you actively build with Claude (or equivalent) and have a point of view on guardrails, verification, and where AI helps vs. hurts.
- SQL Server / EF, ASP.NET (MVC and/or modern .NET), and a real grasp of release engineering + security.
Strongly preferred: .NET 10 / modern minimal-API patterns, multi-tenant SaaS, MACH / clean architecture, Azure App Service + slot deploys, observability.
Not this role: primarily JavaScript/front-end, or primarily AWS/Java/Python — if your depth isn't C#/.NET, this isn't the fit.
How we work
Small written-down rules the AI reads first; one job per station; a human at every gate that costs money. You'll have real ownership and a direct line to the CTIO — this is a build seat, not a ticket queue.
