Staff Software Engineer

Staff Software Engineer, Records Platform 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. Summary The Staff Software Engineer is the technical lead for key projects on Neumo’s Records platform (Land Records, Vital Records and Search). County recorders and clerks use Records to record deeds, index documents, issue certified birth, death and marriage certificates, and give the public secure access to records that go back generations. Every recorded document has legal weight, so correctness, security and reliability are essential. Records is a key area of investment for Neumo. 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. The Staff Engineer designs and builds scalable solutions, guides project-level technical decisions, and sets the technical standards the team works to. This role requires deep expertise in cloud-based micro service architecture and technology. It also requires leadership skills: influencing team decisions, championing quality and mentoring Senior Engineers, many of whom work alongside newer team members. The Staff Engineer reports to a Software Engineering Manager on the Records platform. The manager leads people and delivery, and the Staff Engineer leads on technical depth and direction. Duties and Responsibilities

• Serve as technical lead on key Records projects. Work with cross-functional teams to gather requirements, shape solutions and guide implementation from design through production.
• Design, build and maintain advanced features within the Records platform, such as eRecording and eSubmission, automated indexing, search, certified copy requests, property fraud alerts, and ID verification and payment integrations.
• Provide technical direction for the broader modernization. That includes decoupling tightly coupled components, replacing manual configuration with configurable, self-service setup, and removing dependencies on specific peripherals.
• Design for configurability across jurisdictions, so the platform fits each county’s statutes, workflows and level of digital maturity without custom code.
• Own the technical direction for Records search, including indexing strategy, relevance, query performance and scaling for large volumes of recorded documents.
• Design data migration approaches that move customers and their historical records onto the modern platform with full data accuracy and record integrity.
• Partner with Senior Engineers, product, architects and leadership to create, refine and document technical standards, including standards for search and related infrastructure.
• Write and maintain architecture decision records so the reasons behind key choices outlast any one person.
• Set the code review and quality bar for the team, including review standards and test strategies for AI-generated code under Neumo’s agentic delivery model.
• Help the team work well from approved specifications. Write precise specs, show how to direct AI agents effectively, and make sure engineers own what ships.
• Conduct thorough code reviews, troubleshoot complex issues, and resolve hard performance, reliability and data quality problems.
• Lead the technical response to serious production incidents, and make sure post-incident follow-up actually improves the platform.
• Contribute to CI/CD pipelines, infrastructure-as-code, automated testing and observability to support reliable, repeatable releases.
• Mentor Senior Engineers on design, code quality and development standards, and help them grow into technical leaders.
• Reduce key-person risk by documenting platform knowledge and spreading expertise through pairing, design reviews and walkthroughs.
• Build on Neumo’s shared enterprise services, such as identity and access, payments, notifications, reporting and search, instead of rebuilding them within Records. Partner with Platform Engineering where Records needs something new.
• Embed secure development practices, including vulnerability scanning, secrets management and access control, in line with the frameworks our government customers require.
• Stay current with emerging technologies in search, cloud and AI-assisted engineering. Run small, deliberate experiments and bring what works back to the team.

Qualifications

• Bachelor’s degree in Computer Science, Engineering or a related field, or equivalent experience.
• 8+ years of experience in full-stack development and cloud software, across both Microsoft and open-source technology stacks.
• Advanced backend coding skills in Java and .NET, including both .NET Framework and modern .NET. Experience with Python or Node.js/TypeScript is a plus.
• Strong front-end experience with React, including building responsive, accessible user interfaces for both staff and public users.
• Deep experience designing, building and operating microservices, including service boundaries, API design and versioning, inter-service communication, and resilience patterns.
• Proficiency in Azure (preferred) or AWS and cloud-native design patterns, such as serverless and event-driven architecture, distributed caching and containerization. Examples include Azure Functions, Service Bus, Event Grid and AKS, or Lambda, EventBridge, SQS/SNS and ECS/EKS.
• Deep experience with SQL Server and other relational databases, and hands-on experience with document databases, ideally Azure DocumentDB (Azure Cosmos DB for MongoDB). That includes data modeling, indexing and performance tuning, plus strong knowledge of cloud storage and data management best practices.
• Strong expertise in search platforms such as Elasticsearch, Azure AI Search, OpenSearch, Solr or Lucene, and experience optimizing large-scale search architectures.
• A track record of leading the modernization of tightly coupled or legacy systems into microservices, while keeping them stable in production.
• Experience with high-volume data processing and large-scale data migrations.
• Experience serving as a hands-on technical lead on complex projects, including writing design documents or architecture decision records.
• Hands-on experience with AI-assisted or agentic development, and a clear view of where it helps and where it produces work that’s hard to maintain.
• Experience working in Agile environments, with a collaborative approach to problem-solving and technical mentorship.
• Understanding of security and compliance standards, such as SOC 2 and PCI, and how they apply to engineering design.
• Excellent communication skills, with the ability to explain complex technical topics clearly and influence technical decisions.

Nice to Have

• Experience with land records, vital records, recording or county clerk systems.
• Experience with document management, 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 platforms.
• Experience with spec-driven development, context engineering, or building reusable agent skills and workflows (for example, Claude Code, Cursor or GitHub Copilot agents).
• Experience with public-sector security frameworks, such as StateRAMP/GovRAMP or FedRAMP.

What Success Looks Like First 30 days. You understand the Records monolith: its main domains, where they’re tightly coupled, and which customers and workflows depend on each. You’ve mapped how the platform talks to printers, scanners and other peripherals today, and where those dependencies are hard-coded. You’ve walked through the current UI with staff and public users to see where the experience breaks down. You know where manual configuration slows down onboarding and support. You’ve built working relationships with your manager, product, architects and the engineers on the team, and you’ve seen the agentic delivery flow end to end. By 60 days. You’ve proposed a domain-by-domain modernization plan that ranks domains by customer value, risk and coupling, and names the first domain to pull out of the monolith. You’ve written architecture decision records for the key patterns:

• Service boundaries and APIs.
• Data ownership. When to use specific databases.
• A peripheral abstraction layer. This lets the platform work with any standard printer or scanner rather than specific models.
• The modern React UI approach. Including a shared component library and accessibility standards.

You’ve also outlined the design for self-service configuration, so customers and implementation teams can set up workflows, fees and document types without engineering help. Code review and testing standards, including for AI-generated code, are documented and in use. By 90 days. The first domain is being extracted from the monolith and is close to production, with data migration and rollback plans in place. A working proof of concept shows the platform using standard printer and scanner protocols on at least two device types it couldn’t use before. The first modern UI screens are built on the shared component library and validated with real users. Senior Engineers are leading parts of this work with your guidance, and the full modernization has a clear technical path. By the end of year one.

• Domains. Several domains run as independent services, with a published roadmap for the rest of the monolith.
• Peripherals. The platform is peripheral-agnostic in production. New customers can use their existing printers and scanners without custom work, and hardware-related support tickets are going down.
• UI. Key staff and public workflows run on the modern UI, with measurably better usability, accessibility and task completion times.
• Self-service. Customers can configure common settings themselves, which shortens onboarding and reduces requests to engineering.
• Upgrade and search. The .NET upgrade is complete, and search performance and data migration quality have measurably improved.
• Team. Senior Engineers are visibly stronger technical leaders, and modernization standards are being used as the model across Records.

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.