Technical Lead / Architect
This is the employer's own posting, not a copy on a job board.
What we know
Is it still open?
Confirmed still open
Last checked 17h ago — checked against the employer's own applicant tracking system, which is the company answering directly.
We re-read the employer's own applicant tracking system and the posting was still there. That is the company answering directly.
How old is it?
Posted 1d ago
The date the source published, not the day we noticed it (2026-11-20). Last seen at its source 1h ago.
Is it remote?
Marked remote on the employer's board
Their board carries a remote setting on this posting — a field they filled in, not wording we read. The location field names somewhere specific, which is usually where the team or the entity sits.
Who may apply?
United States
The description states no restriction of its own. This is the source's own tag.
Pay not stated
Similar roles pay $170k–256.6k/yr
Middle 50% of 145 listings that do state pay — Engineering · Lead · United States · USD/year. This employer has published no salary; this is what comparable listings we hold disclose, never converted between currencies or periods. How this is calculated.
Skills named in the ad
Recognised terms only, from a fixed vocabulary — this is what CV matching compares against.
Carried by 1 source
-
Workable employer's own board first seen 17h ago · last seen 1h ago
The listing
You own the architecture, the coding standards and the code-review standard across roughly thirty .NET services on AKS and a large React front end. About half your time is hands-on back-end work; the other half is the standard: what a reviewer looks for, how big a change may be, which areas need a second reviewer, and how generated code is reviewed, tested and merged. You are the person who decides what is recorded, from decision records to runbooks to the repository agent guides, and you run the technical half of hiring.
You inherit a working platform with a list of deferred technical decisions that are yours to make in the first year: merge strategy and branch policy, reviewer assignment, the guarded-area list, environment consolidation, moving provisioning from laptops into pipelines, secrets out of the pipeline library and into the vault, just-in-time privileged access, the regression-suite build order with the QA lead, and the alert and runbook inventory with the DevOps engineer.
What you will do
- Own the review standard and sample merged changes against it; be the required second reviewer on guarded areas (billing, authentication, tenancy, migrations, cross-service contracts) until service owner pairs exist.
- Set the standard for AI-assisted development: how generated code is reviewed, tested and merged; what the pre-review agent checks; what every repository's agent guide must contain and how it stays current.
- Lead the technical side of the transition from the outsourced provider with the DevOps engineer: pipelines, service connections, Terraform state and secrets re-issued under Christie Lites identities.
- Build, hands on, in the back end about half the time, including the guarded areas and the hardest items.
- Lead major platform work: .NET version upgrades, service consolidation, environment consolidation, expand-and-contract schema changes with a rollback test in CI.
- Be the sizing pair of last resort when the business analyst and the rotating engineer disagree on an estimate; sign Ready with the QA lead.
- Run the technical interviews: the review exercise with planted defects, the paired build, the design conversation.
- Take an equal turn on the on-call rota from your third month.
Requirements
- Eight or more years of .NET / C# with ASP.NET Core Web APIs and EF Core against SQL Server or Azure SQL.
- Distributed systems on Azure in production: Service Bus, Redis, SQL, Kubernetes (AKS), with Terraform and Helm.
- Multi-tenant SaaS: tenancy boundaries, per-tenant data, the failure modes that follow from getting it wrong.
- Has led the technical side of a team through a major platform upgrade or service consolidation and can describe the plan, the rollback and what went wrong.
- Daily, fluent use of an AI coding agent on real production work, and a clear point of view on how generated code should be reviewed and tested.
- Has owned a code-review standard, not just participated in reviews, and can show it.
- Clear written English; writes decision records and runbooks that others follow.
Preferred
- React and TypeScript at a level to review front-end changes.
- Azure DevOps pipelines and branch policy as code.
- Identity and secrets management on Azure (Key Vault, managed identity, workload identity federation, PIM).
- Taking over a platform from an outsourced provider.