Senior Systems Solution Architect Neumo builds the software state and local governments use to collect taxes, license businesses and serve the public. Our Tax & Licensing portfolio - Neumo Tax, FileLocal, short-term rental compliance and several acquired tax products - grew up on separate platforms with separate data models. We are now building the platform those products will consolidate onto: a Tax Transaction Engine and a Tax Capability Rules Engine, designed multi-tenant from day one. We are hiring a Principal Solution Architect to own the target-state architecture for that platform. You will define what we build, how the pieces fit, and how existing products and agencies get from where they are today to where we are going. This is a hands-on architecture role with broad influence: you will set the technical and implementation direction that several engineering teams build against, and you will be accountable for that direction holding up in production. Why This Role Exists Now Each product in the portfolio defines taxpayers, jurisdictions, obligations, filings and payments in its own way. That raises maintenance cost, slows agency onboarding and limits how quickly we can support new tax types. The new engines solve this only if the architecture is right before the build scales - and only if there is a credible path for live agencies, with years of filing history, to move onto them. There is no solution architecture function in the organization today. Decisions are being made team by team. This role brings them into one coherent design, records them, and governs them. What You Will Do Define the target state
- Own the end-to-end target architecture for the Tax & Licensing platform: transaction processing, ledger, rules, tax calculation, forms, agency administration and filer-facing experiences.
- Design for multi-tenancy as the central constraint: tenant isolation, per-jurisdiction configurability, rates and rules as configuration rather than code, and schema-driven forms.
- Establish reference architectures and integration patterns (API-first, event-driven) that product teams adopt rather than reinvent.
Chart the path from current to future state
- Assess the existing products and platforms and produce a realistic, sequenced convergence plan - what moves, in what order, and what has to be true first.
- Partner with the Principal Data Architect on canonical data models, data conversion and the bridge between legacy platforms and the new engines, so that migrated agencies can be proven complete.
- Identify architectural risks early - capacity, cost-to-serve, security, regulatory and timeline - and put options and trade-offs in front of leadership in plain language.
Govern and enable
- Introduce and run architecture decision records (ADRs) and a lightweight architecture review practice.
- Work directly with engineering managers, tech leads, product, QA and SRE to turn architecture into buildable designs, and review designs as they are built.
- Contribute hands-on during build phases: proofs of concept, spikes, reference implementations and critical-path design work.
- Coach senior engineers and raise architectural capability across the teams.
Look ahead
- Design the platform so it can support AI-assisted capabilities - rules authoring, filer guidance, anomaly detection - without re-architecture later.
- Evaluate build, buy and partner options for platform components with a clear view of total cost.
What You Bring Required
- 10+ years in software engineering, with 5+ years in an architect role (solution, platform or enterprise).
- Architecture ownership of a multi-tenant SaaS or large Enterprise grade product, including tenant isolation, configurability and the operational economics of serving many customers on one platform.
- Led the design of a platform consolidation or product convergence, and stayed with it through delivery - including moving live customers and their data onto the new platform.
- Strong domain modeling (DDD or equivalent) and experience with transactional, financial or ledger-style systems where correctness and auditability matter.
- Deep experience on public cloud (AWS or Azure), including designing for security, resilience and cost at scale.
- Experience with rules engines, configuration-driven design or other approaches that let non-engineers change system behavior safely.
- Clear written and verbal communication - able to make a trade-off understandable to an executive and precise to an engineer.
- Track record of influencing engineering teams you do not manage.
Preferred
- Tax, revenue, payments, government technology or another regulated domain.
- Experience modernizing long-lived systems incrementally while they continue to carry production load.
- Familiarity with MySQL/Aurora at scale with both legacy platforms and green field tech stacks.
- AWS or Azure Cloud Professional-level certification (Solutions Architect Professional or equivalent).
How We Will Measure Success First 90 days
- Current-state assessment of the Tax & Licensing platforms, written and reviewed with engineering leadership.
- Target architecture v1 for the Tax Transaction Engine and Tax Capability Rules Engine.
- A written view on the convergence plan and timeline: what is achievable, what is at risk, and what it would take.
- ADR practice in place, with the foundational decisions recorded.
First year
- Teams building the new engines against an agreed, documented architecture.
- First products or agencies migrating along the planned path, with data conversion verified.
- Measurable reduction in one-off, team-by-team design decisions on the platform.
Who You Will Work With Sr. Director of Software Engineering - Tax; the Principal Data Architect; engineering managers for Core Tax, Foundation Engineering, BLT and Short-Term Rental; Application Delivery and QaOps; Product Management; and leaders across the wider engineering organization, including Records.