Any
$2500 per month
40
Jul 23, 2026
Tech Lead — Hospitality Commerce Platform & AI-First Development
**Danner Enterprises / Save on Branson · Branson, MO (hybrid or remote considered) · Full-time**
---
The Short Version
We run a hospitality and vacation portfolio in Branson, Missouri — show tickets, lodging, tours, vacation rentals — with **$20M+/year flowing through a custom platform we call SMASH**: 248 daily users, 978,000 customer records, 371,000 orders, and a decade of real business logic.
The developer who built most of it over the last 4.5 years is transitioning out. We're not replacing her with a bigger team — we're moving to an **AI-first development model**: AI coding agents generate most of the code; one exceptional human tech lead reviews it, deploys it, owns the architecture, and makes the calls.
That human is you.
This is a rare kind of role: total technical ownership of a revenue-critical system, a mandate to modernize it, and a front-row seat (driver's seat, actually) in how AI-assisted development actually works at a real company — not a demo, not a lab.
---
What You'll Own
**A legacy system that pays the bills.** ASP.NET Zero / ABP Framework
**A modern system that's replacing it, piece by piece.** A .NET 10 Clean Architecture build (`SOB.*`): stored-procedure-first data access (Insight.Database), DbUp migrations, a Vite/JavaScript campaign UI, a REST API replacing the legacy RPC surface, and an SMS campaign engine (ClickSend, GoTo Connect, consent/opt-out management, Hangfire send engine). Both systems share one database — schema changes are a coordination discipline, and you'll own it.
**A production MCP server.** `SOB.Mcp` — built on the official C# Model Context Protocol SDK — already gives AI agents structured, auth-forwarded access to platform data. You'll extend it: more tools, more capabilities, more of the business safely exposed to agents.
**The AI development pipeline itself.** AI agents submit PRs against the repo daily. You review them, harden them, merge them, and deploy them. You maintain the CLAUDE.md / AGENTS.md context documentation that keeps agent output quality high. Target state: 80–120 commits/month shipping through your review, with you as the quality gate — not the bottleneck.
**The integration estate.** Stripe, ActiveCampaign, GoTo Connect, Five9, Twilio, RingCentral, ClickSend, Contentful, Zapier, outbound webhooks to automation platforms. Phones and payments are this business — the integrations are not side quests.
---
Your First 90 Days (Real Backlog, Not Boilerplate)
We believe in showing you the actual work. If this list makes you lean in, apply. If it makes you wince, we've saved us both time.
- Fix an ActiveCampaign sync integration that's logging millions of error rows at a 99.9?ilure rate — while the business thinks it's fine
- Triage 215 failed Hangfire jobs and stand up failure alerting
- Stand up CI/CD on Azure DevOps (PR ? build ? staging auto-deploy) to replace manual, single-person deployments
- Design and run a backfill inferring order status for 308,000 orders where it's NULL (83% of all orders)
- Reconcile a six-figure gap between recorded transactions and orders
- Close a 378,000-ticket gap in our voucher/billing pipeline
- Groom a 178-item backlog, kill the zombies, and set priorities with leadership
- Continue porting ~22 legacy API endpoints to the new REST surface
- Absorb a structured knowledge transfer from the outgoing developer (recorded walkthroughs, deployment procedures, the undocumented quirks)
- Make the first calls on two end-of-life fronts: Angular 8 and Xamarin mobile
---
What We Need You To Bring
**The legacy depth (non-negotiable)**
- 7+ years of professional C#/.NET, with current production experience
- Deep experience with a heavily-opinionated enterprise framework — ABP / ASP.NET Zero is the dream; an equivalent conventions-based monolith (with its DI container, module system, and dynamic API layer) is acceptable if you can prove you reverse-engineer framework internals from source
- Expert SQL Server, in multiple paradigms: EF Core migrations at scale, stored-procedure-first access, Dapper, and script-based deployment (DbUp). You've managed schema changes on a database that more than one application depends on.
- Large-scale data-quality engineering: backfills, reconciliations, deduplication — safely, auditable, reversible
- Authentication breadth: JWT bearer internals (if you've debugged
- Production integration engineering: payments, SMS at scale with consent/opt-out compliance, telephony webhooks, marketing automation APIs — with idempotency, retries, and activity logging as instincts, not afterthoughts
- Hangfire, Redis, SignalR; Docker builds; Azure DevOps
- Front-end pragmatism: you can maintain an Angular 8 app and a Vite/vanilla-JS app without needing either to be your favorite
- Testing discipline: xUnit, mocking, and written test plans/verification results as release artifacts
**The AI fluency (equally non-negotiable)**
- You use AI coding agents (Claude Code, Codex, Cursor) daily and seriously — and you know exactly where they hallucinate in legacy codebases (migrations, auth config, framework conventions) and how to gate for it
- You've built or extended an MCP server, or can show us a real tool-calling / structured-output LLM integration you shipped to production
- You can write and maintain repo AI-context documentation as a first-class engineering artifact
- You have opinions about reviewing AI-generated PRs at volume — formed by doing it
**The judgment**
- You've been the person a business depended on before, and it didn't scare you
- You default to guardrails-before-velocity: tests and CI first, then speed
- You'd rather inherit a profitable, imperfect system than build a perfect one nobody uses
---
Nice to Have
- Prior ASP.NET Zero / aspnetboilerplate commercial project (tell us immediately)
- Xamarin ? .NET MAUI migration experience; Angular major-version upgrade or SPA strangler-replacement leadership
-
- E-commerce cart, pricing, voucher, or commission domain experience
- Hospitality, ticketing, or OTA industry background
- You've led a framework migration (.NET 3.1 ? 8 ? 10 or similar) and lived to document it
---
Why This Role Is Different
**Total ownership.** No committee. You are the technical authority, working directly with the owner/architect and leadership. Your decisions ship.
**The AI-first model is real here, not a press release.** AI agents already have commit history in this repo. A production MCP server already runs. Your leverage is the point of the job.
**The system matters.** This isn't an internal tool nobody uses. Two hundred forty-eight people run their workday through it, and $20M+ of real revenue depends on it staying up.
**The problems are honest.** We showed you the backlog above — including the ugly parts — because the right candidate finds a 99.9%-error-rate integration *interesting*.
---
Logistics
- **Location:** Branson, MO preferred (hybrid); remote considered for an exceptional fit (US time zones)
- **Compensation:** Competitive, commensurate with the scope above — we know what total ownership is worth
- **Reports to:** Ownership/leadership, working alongside our AI development agents and a project-based systems architect
---
How to Apply
Skip the cover letter. Send us:
1. **Your resume and why you are the best candidate for the job**
2. **One paragraph on the gnarliest legacy system you've owned** — what it was, what broke, what you did
3. **Proof of AI fluency** — a repo, an MCP server, a PR trail, a writeup, anything that shows you actually work this way
4. **(Bonus)** Your answer to this: *"You inherit a .NET 8 app where JWTs validate successfully but the session user ID comes back null. Where do you look first?"*
If you've read this far and you're already thinking about the NULL-status backfill strategy — we should talk.
Really want to jump to the front of the line? Respond to my test questions. No cheating. Send this with everything else when you apply:
Here it is in plain text, ready to paste straight into an Onlinejobs.ph message or application form. I've reworded them slightly for written async answers and added length guidance so applicants know what "done" looks like:
SCREENING QUESTIONS — Please answer all 7 in your reply.
Short, direct answers are fine (3-6 sentences each). We are
looking for how you think, not essay length. If you don't
know an answer, say so honestly — guessing hurts you more
than a straight "I haven't hit that one yet."
1. We upgraded a .NET app
JWT tokens still validate successfully, but the session
user ID now comes back null. Where do you look first,
and why?
2. You inherit a legacy app where Program.cs still uses
WebHost.CreateDefaultBuilder instead of the modern Generic
Host. An AI coding agent submits a PR "modernizing" it to
Host.CreateDefaultBuilder. What do you do before merging?
3. 83% of our orders (about 308,000 rows) have a NULL
Status column. We can infer the correct status from related
data (cancellations, payment transactions, arrival dates).
Outline your approach to backfilling this safely.
4. An integration sync job has logged 3.9 million error
rows at a 99.9?ilure rate, but the business says the
integration works fine and their data looks correct.
What is your first move, and what would you NOT do yet?
5. You are the only human reviewer in a team where AI
agents (Claude Code / Codex) generate most pull requests.
An agent submits a 15-file PR that touches an EF Core
migration and auth configuration in a codebase you've
owned for only two months. Walk me through your review
process, step by step.
6. Two applications share one SQL Server database. One
uses EF Core with a 900-migration history. The other uses
stored procedures deployed with DbUp SQL scripts. You need
to alter a core table that both depend on. How do you do
it without breaking either app?
7. We have an MCP server that exposes contact search to
AI agents. It is a zero-identity proxy that forwards the
caller's auth to our API. We now want to add a tool that
lets AI agents send SMS campaigns to customers. What
concerns would you raise before building it?
BONUS (optional, strong answers get priority review):
Link us to proof you work with AI coding tools daily —
a repo, an MCP server you built, a PR history, or a
short writeup of your workflow.