About Neumo Neumo builds the cloud software that powers government. More than 4,500 state, local and federal agencies across North America run on our platforms, processing over 900 million transactions and collecting $44 billion in revenue for the communities they serve. When a county records a deed, a family orders a birth certificate, or a business files a local tax return, that transaction often runs through our systems. That comes with a particular kind of engineering responsibility. Our platforms are systems of record for legally binding documents and public funds. Correctness is not negotiable, downtime has civic consequences, and the data we hold is expected to remain accurate and retrievable for decades. The Role Records is where that responsibility is most literal. Neumo’s Records platform (Land Records, Vital Records and Search) is how county recorders and clerks record deeds, index documents, issue certified birth, death and marriage certificates, and give the public secure access to records that go back generations. Every document we record has legal weight, and every index entry has to be right. Records is also a targeted investment and a key revenue generator for Neumo over the next several years. We are evolving it from a tightly coupled, manually configured platform that depends on specific peripherals into a best-in-class product that meets customers where they are. Some of those customers still work mostly on paper. Others are fully digital and want more self-service, automation and fraud protection. We are hiring the engineering manager who leads a core part of that work. You will lead a team of 6-10 engineers on the Records platform. You will own how your part of the platform is architected, built, released and operated, and you will be accountable for predictable delivery to the customers and partners who depend on it. This is a people-leadership role with a high technical bar. You will carry direct reports, run delivery and grow engineers. You will also review designs, write architecture decision records, and be able to explain why a component is coupled the way it is and how it should be pulled apart. We are not looking for a manager who has moved away from the technology. We are looking for someone who has led product engineering teams through modernization and still thinks like an engineer. You will report to the Vice President of Software Engineering and work closely with the Records engineering leadership team and Records product management. Product owns what we build and why. You own how: architecture, delivery, quality and operational health. We are also changing how software gets built. Neumo is moving to an agentic delivery model: small pods working from approved specifications, with AI agents drafting specs, stories and code, and engineers directing, reviewing and owning what ships. You will lead your team through that shift. Many of your engineers are new to Neumo, and some are early in their careers. Helping them build real judgment in this new model, not just speed, is part of the job. What You’ll Do Platform modernization and architecture
- Own the technical architecture and engineering roadmap for your area of the Records platform.
- Lead the work to decouple tightly coupled components, replace manual configuration with configurable, self-service setup, and remove dependencies on specific peripherals.
- Drive the .NET upgrade and related modernization to completion, with a clear plan, owners and dates.
- Design for configurability across jurisdictions, so the platform fits each county’s statutes, workflows and level of digital maturity without custom builds.
- Build on Neumo’s shared enterprise services (identity and access, payments, notifications, reporting and search) rather than re-solving them inside Records. Partner with Platform Engineering where Records needs something those services don’t yet provide.
- Write and maintain architecture decision records so the reasons behind key choices outlast any one person.
Records product delivery
- Deliver and improve core Records capabilities, such as eRecording and eSubmission, automated indexing, full-text and OCR search, certified copy requests, property fraud alerts, and ID verification and payment integrations.
- Partner with implementation teams to migrate customers and their historical records onto the modern platform, with a focus on data accuracy, record integrity and minimal disruption to office operations.
- Make sure recorded documents become publicly available quickly and reliably, and that records stay accurate, secure and tamper-resistant.
Team leadership and delivery
- Lead, hire and develop your engineering team. Hold regular 1:1s, give clear feedback and build growth plans that help new engineers ramp up quickly and stay.
- Own sprint planning, backlog refinement, delivery cadence and release management. Start refinement early enough that commitments are realistic, and flag risk as soon as it appears.
- Run a capacity model that protects planned roadmap work while absorbing production support, defects and customer escalations.
- Close the gap between “dev-complete” and “in production.” Keep QA involved from planning through release, and hold a Definition of Done that includes integration, deployment and operational readiness.
- Reduce key-person risk through knowledge sharing, documentation, pairing and cross-training, so critical platform knowledge doesn’t live with one person.
- Build a culture of ownership, delivery discipline and candor. The team should be the first to say when something is at risk.
Agentic delivery and AI-native engineering
- Lead the team’s move to agentic delivery. In this model, an approved specification is the contract, agents draft specs, stories and code against it, and engineers own design decisions, review and acceptance.
- Adapt how the team works around that model, including roles, ceremonies, estimation and Definition of Done.
- Set the quality bar for AI-generated work. Code that passes its tests can still be wrong or unmaintainable, so establish review standards, test strategies that prove correctness, and merge gates that actually block bad changes.
- Use agentic tools to speed up modernization work, such as understanding legacy code, documenting tribal knowledge and supporting the .NET upgrade, while keeping engineers accountable for what ships.
- Measure what agentic delivery is doing to throughput, quality and rework, report it honestly, and adjust when the data says something isn’t working.
- Grow engineers into this way of working. Help them learn to write precise specifications, direct agents and review generated output critically, while keeping the deep fundamentals that judgment depends on.
Operational excellence
- Own the operational health of your services: monitoring, alerting, on-call, incident response and post-incident follow-through.
- Define and report engineering metrics, including DORA measures, delivery predictability, defect rates and customer-impacting incidents.
- Drive CI/CD, infrastructure-as-code and cloud operational excellence, including disaster recovery readiness and cloud cost efficiency.
Security, compliance and stakeholder partnership
- Embed security in the development workflow, including vulnerability scanning, SBOMs, secrets management and access control. Partner with security leadership on the frameworks our government customers require.
- Translate customer and business urgency into engineering sequencing, and explain constraints and trade-offs plainly to non-technical leaders.
- Work with product management to turn the Records strategy into a sequenced, realistic delivery plan, and be the honest voice on scope, cost and risk.
What We’re Looking For
- Bachelor’s degree in Computer Science, Engineering or a related field, or equivalent experience.
- 8+ years in software engineering, with significant time in full-stack development and cloud software for customer-facing products.
- 4+ years leading engineering teams, including hiring, performance management and growing engineers, ideally with distributed or nearshore teams.
- Hands-on technical depth. You can review a design or a pull request critically, lead an architecture discussion, and write the decision record that comes out of it.
- Broad technical background across languages and frameworks, such as .NET (Framework and modern .NET), Node.js/TypeScript, Java, Python or React, with strong .NET experience.
- A track record of modernizing tightly coupled or legacy systems, including framework upgrades, while continuing to ship customer-facing features.
- Proficiency in cloud-native design patterns on AWS, Azure or both, such as microservices, serverless and event-driven architecture, distributed caching and containerization.
- Experience with search platforms such as Elasticsearch, Solr or Lucene, and with high-volume data processing, SQL and NoSQL databases, and cloud storage.
- Experience leading Agile teams, including backlog refinement, sprint planning and release management.
- Experience coaching and developing early-career and newly hired engineers.
- Hands-on experience leading a team using AI-assisted or agentic delivery in production, not just piloting tools. You can describe what changed in how your team planned, built and reviewed work, and where the approach broke down.
- Experience operating production systems in regulated environments, such as government, finance or healthcare, where data accuracy and auditability matter.
- Clear, direct communication with engineers, product partners and executives, in writing and in the room.
Nice to Have
- Experience with land records, vital records, recording or county clerk systems.
- Experience with document management, OCR, imaging or scanning technologies.
- Experience integrating with hardware peripherals or moving away from hardware-dependent designs.
- Experience with eRecording standards or submitter integrations.
- Experience with multi-tenant SaaS and onboarding customers at scale.
- Experience with large-scale data migrations of historical records.
- Experience with spec-driven development, context engineering, or reusable agent skills and workflows (for example, Claude Code, Cursor or GitHub Copilot agents).
- Experience with public-sector security frameworks such as StateRAMP/GovRAMP, FedRAMP, SOC 2 or PCI DSS.
What Success Looks Like First 30 days. You know your part of the Records platform, where it is tightly coupled or fragile, and which customers and workflows depend on it. You have a working partnership with Records engineering leadership and product management, a clear picture of your team’s strengths and gaps. You have mapped where critical knowledge lives with one person. By 60 days. Delivery is predictable and visible. Refinement runs ahead of the sprint, risks are raised early, and every engineer has regular 1:1s and a growth plan. The .NET upgrade has a realistic plan with owners and dates, and knowledge transfer is underway for the highest-risk areas. By 90 days. Your team is hitting its commitments. At least one meaningful modernization step has shipped to production, such as decoupling a component, removing a manual configuration step or reducing a peripheral dependency. Agentic delivery has a measured baseline for throughput, quality and rework. By the end of year one. Your area of the platform is easier to configure, deploy and support, and customers are migrating onto it with fewer surprises. Engineers are visibly more senior than when you arrived, attrition is down, and no critical area depends on a single person. Agentic delivery is how the team works by default, with a quality bar others look to. Neumo Summary With the backing of four decades of public sector expertise and corporate capability, Neumo has successfully supported government services. Neumo was honored and recognized for four (4) consecutive years as a GovTech 100 Company representing the top 100 companies focused on making a difference in and selling to state and local government agencies across the United States. Neumo is committed to helping communities thrive and brings a wealth of experience combined with innovation. Today, Neumo offers more administrative and financial support to government officials than any other organization. And with a responsive, client-focused approach, we foster partnerships that give our customers the certainty they need to accomplish more. Neumo offers a competitive benefits and compensation package and are looking for team members who will thrive in our dynamic environment. Neumo is an Equal Opportunity Employer. Selection for a position will be made without regard to race, religion, national origin, sex, political affiliation, marital status, non-disqualifying physical handicap, and age.
