Senior Software Engineer - Marketing Experience

The Team 

We build and run the software behind CMG's marketing platform: consumer websites, loan-officer microsites, rate-lock marketing products, lead intake and routing, review and testimonial syndication, email signatures, and the background services that move loan data between our loan origination system, Salesforce, and roughly fifteen marketing SaaS vendors. The estate is seven .NET monorepos that span generations: the newest platforms are .NET 9 APIs with React frontends and containerized deploys, the oldest are .NET Framework apps we are actively consolidating and retiring, and there's a lot of SQL Server underneath all of it. 

The modernization is in motion, not aspirational. In the past year we consolidated everything into GitHub monorepos with GitHub Actions CI/CD, stood up a modern .NET 9 background-job platform that legacy services are migrating onto, shipped the first phases of a program that moves applications off a shared database and onto internal APIs, and rebuilt our largest legacy product on a current stack. This role exists to keep that moving. 

The Job 

This is a hands-on senior role with three centers of gravity. 

Ship fast against structured requirements. Product hands us typed GitHub issues with testable acceptance criteria. The main number we watch is how quickly an accepted requirement becomes a production deployment. On this team most PRs merge the same day they open, and a bug fix routinely ships with its tests, evidence, and release notes in one pass. We are hiring for that pace, sustained, without skipping the quality gates that make it safe. 

Own your systems end to end. The things you build are yours from requirements review through production. Most of the work is delivery: new capabilities on the loan-officer platforms, vendor API integrations, internal APIs that replace legacy coupling, hardening background jobs that move real loan data. And when something you own misbehaves in production, you're the one who can trace it across application code, SQL Server, vendor APIs, and Azure infrastructure and fix it at the right layer, because you understand the whole path. There's no separate ops team to hand off to; that's why our deploys are gated, evidence-backed, and reversible, and it's also why engineers here get to make real architectural decisions about the systems they run. 

Modernize as you go. This is not a cleanup job, and it's not a greenfield job either; the two run side by side. The target architecture already exists in our newest platforms, the remaining tech debt has been audited and ranked into concrete backlogs (you will never be guessing where to dig), and modernization work is first-class roadmap work here, not something you sneak in between features. You'll pull the older half of the portfolio toward the standard the newer half already meets: extract services out of oversized controllers, bring schema under source control, replace shared-database coupling with internal APIs, retire end-of-life frameworks, and add test suites where they're missing. Every one of those changes makes the codebase faster and safer for both people and coding agents to work in, which feeds directly back into the delivery speed we care about. 

How we work 

We recently moved development onto Claude Code and an in-house SDLC built on GitHub issues. Our EVP of Technology, Kitt Holland, published the full system at tech.cmgfi.com/agentic-sdlc. 

Every change ties to an accepted, typed issue with testable acceptance criteria, and engineers send vague tickets back to product before writing code. Completion runs a validation gate, and the PR carries the evidence. Agents write a large share of the code, so your value is judgment at the gates: is the plan right, is the generated test real or tautological, does the evidence actually prove the acceptance criterion, is this safe to ship. 

We expect fluency with agentic development on day one. You don't need to have used our specific tooling. Yo