Software Architect

Aptive Environmental•Provo, UT

1d•Onsite

About The Position

We are seeking a hard-working, innovative, detail-oriented, and creative team player to join our Aptive team! This is a full-time Software Architect position located in Provo, Utah. The individual we are looking for is someone who enjoys working in a team environment and excels at working at an individual level. We're hiring a Systems Architect to own the technical blueprint that ties Aptive's platforms together. You will define how services, data, and integrations fit into a coherent, scalable whole — setting architectural standards across the Aspyn platform (Customer, Sales, Field Service, and Platform teams) and guiding engineers through the migration from legacy systems (e.g., FieldRoutes/PestRoutes) to modern, well-bounded services. This is a hands-on architecture role: you'll write reference implementations and proofs-of-concept, not just diagrams.

Requirements

8+ years in software/systems engineering, with 3+ years in an architecture or staff-level role
Distributed systems depth: proven design of service-oriented / event-driven architectures at scale, including API and integration design
Cloud-native expertise: hands-on with a major cloud (AWS preferred), containers/orchestration, IaC, and CI/CD
Data fluency: strong SQL and experience designing systems that feed a modern data warehouse (Snowflake, dbt, or equivalent)
Migration experience: led at least one significant legacy-to-modern platform migration in a live, revenue-generating environment
Integration savvy: payments, telephony/CRM, or field-operations integrations in a real business context
Communication: can translate architecture to both engineers and executives; writes crisp ADRs and design docs

Nice To Haves

Field-service, logistics, home-services, or scheduling/routing domain experience
Experience with FieldRoutes / PestRoutes or comparable field-service management platforms
Familiarity with design systems and shared component libraries (e.g., internal platforms like Aspyn's)
Exposure to ML/analytics productization (call classification, routing optimization, collections/AR modeling)

Responsibilities

Own the target architecture: define and evolve the end-to-end system design across customer, sales, field-service, billing, and analytics domains, with clear service boundaries and integration contracts
Lead the legacy migration: architect the phased move off FieldRoutes/PestRoutes and other legacy systems onto first-party Aspyn services without disrupting field operations or billing
Set standards: establish and socialize architectural principles, patterns, and guardrails (APIs, events, data contracts, security, observability) that engineering teams build against
Design the data platform interface: partner with data engineering on how operational systems feed the Snowflake/dbt analytics platform — event schemas, CDC, lineage, and data quality
Integrate the ecosystem: design reliable integrations across payments (Stripe), communications/telephony (Genesys, Twilio), CRM, and third-party field/routing systems
Prototype and prove: build reference implementations, spikes, and PoCs that de-risk major decisions and give teams a concrete pattern to follow
Guide, don't gatekeep: review designs, mentor senior engineers, and drive architecture decision records (ADRs) that keep tradeoffs transparent
Non-functionals: make scalability, reliability, security, and cost first-class concerns — capacity planning, failure modes, and SLOs for systems serving millions of appointments and transactions