Staff Software Engineer (Remote)

Neumo Holdings LLC• VA, US, VA

7d•Remote

About The Position

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. We're hiring a Staff Engineer to serve as the senior-most technical individual contributor across our Records and Tax platforms. You'll own the technical direction of two platform families that share deep infrastructure but serve distinct agency workflows, and you'll be accountable for how well they're engineered. This includes architecture, standards, resiliency, and performance. This is a pure IC role at director level, reporting to the VP of Engineering. Your influence comes from technical judgment, written clarity, and the trust of the engineers and leaders you work with. You'll partner closely with engineering managers, product, and security, but you will not carry direct reports. This role is fully remote. Because much of your impact will come through written architecture work and asynchronous influence across distributed teams, we're looking for someone who communicates exceptionally well in writing and builds trust without relying on hallway time. We're looking for someone who is energized rather than deterred by legacy. Much of what we're modernizing has been running in production for years and cannot be broken. The interesting problem here is raising the bar on live, high-consequence systems, not designing on a blank page.

Requirements

12+ years building and operating production software, including significant time at staff/principal level or equivalent scope.
Demonstrated ownership of architecture for large, multi-team, multi-service systems and evidence those systems held up over time.
Deep experience with distributed systems, data modeling, and relational databases at scale, including migrations of live data with no tolerance for loss.
A track record of establishing engineering standards that teams actually adopted, and the judgment to know which standards are worth the friction.
Hands-on depth in resiliency and performance: SLOs, capacity planning, failure-mode analysis, observability, and incident command.
Strong experience with cloud infrastructure and modern delivery practice (IaC, CI/CD, progressive rollout).
Exceptional written communication. Much of your impact will arrive as design documents, RFCs, and architectural decision records.
The ability to lead through influence in an organization where you have no formal authority over the teams doing the work.
Proven effectiveness in a remote, distributed engineering organization.

Nice To Haves

Experience in government technology, regtech, fintech, payments, or another regulated domain with strong audit and compliance requirements.
Experience with tax calculation, billing, or financial reconciliation systems.
Experience with document management, content-heavy systems, or search at scale.
History of modernizing legacy platforms incrementally while keeping them running.
Familiarity with public-sector security frameworks (StateRAMP, FedRAMP, SOC 2, CJIS, PCI DSS).

Responsibilities

Own the target architecture for the Records and Tax platforms, including how they share services, data models, and infrastructure with the broader Neumo platform.
Lead design reviews for significant changes, and set the bar for what a good design document looks like here.
Drive multi-quarter modernization work, decomposing legacy components, defining service boundaries, and sequencing migrations so agencies experience no disruption.
Make and document consequential build/buy/refactor decisions, including the trade-offs you rejected.
Define and evolve engineering standards across both platforms: code quality, testing strategy, API design, data modeling, observability, deployment, and technical documentation.
Make standards real rather than aspirational through tooling, automated checks, templates, and paved paths that make the right approach the easy one.
Raise the quality of code review and technical decision-making across teams by participating directly and by coaching senior engineers.
Set availability, latency, and durability targets appropriate to each workload, and define the SLOs and error budgets that hold us to them.
Lead architecture for fault tolerance, graceful degradation, disaster recovery, and data integrity, including recovery objectives for systems of record that must survive far longer than any single application.
Plan capacity for the seasonal load our platforms face: tax filing deadlines, recording volume spikes, and end-of-period reconciliation.
Own performance engineering practice including load testing, profiling, query optimization, and the instrumentation needed to diagnose issues in production.
Lead or advise on major incident response and post-incident review, and make sure findings turn into durable fixes.
Partner with Security and Compliance to embed requirements into architecture rather than bolting them on. This includes access control, auditability, data retention, redaction of sensitive record data, and payment-adjacent controls.
Design for the regulatory reality of public-sector software, where audit trails and defensible data handling are product requirements.
Act as a force multiplier: mentor senior and staff-track engineers, and grow the depth of the bench across both platforms.
Translate between engineering and executive audiences to make technical risk legible to people making investment decisions.
Represent engineering in conversations with agency customers when technical credibility is what's needed.