Technical Architect (US Hours)

• Own development quality standards for all PS engineering output — defining what 'good' looks like and enforcing it through review, testing, and sign-off processes 

• Lead or directly conduct meaningful code reviews for significant features, integrations, and custom development — providing substantive architectural feedback 

• Establish and own release governance: production readiness criteria, release sequencing, and the decision to ship 

• Build and maintain authoritative technical knowledge of the SHR CRS codebase — becoming the go-to expert on its architecture, data model, integration points, and risk areas 

• Lead architectural design decisions for new PS development work before development begins 

• Serve as primary technical mentor and coach for PS engineering contributors 

• Partner with the Head of Technical Solutions as the technical counterpart in customer-facing conversations requiring architectural depth 

• Maintain awareness of all active PS engineering workstreams, identifying technical risks early and escalating where commitments are at risk 

Minimum Qualifications / Must Haves: 

• 8+ years of progressive software engineering experience, with at least 3 years in a senior or lead architect capacity 

• Proven hands-on engineering depth — comfortable reading, reviewing, and reasoning about production codebases directly 

• Demonstrated experience establishing or significantly improving development quality standards and release practices 

• Strong architectural reasoning: evaluating design trade-offs, identifying systemic risk, recommending sustainable solutions under real delivery constraints 

• Working knowledge of modern CI/CD principles (pipeline design, environment promotion, automated quality gates, release risk management) 

• Cloud architecture literacy — well-architected reasoning across cost, resilience, and scalability trade-offs 

• Active, hands-on use of AI-assisted development tooling, with a point of view on how it should be governed at team scale 

• Experience with enterprise SaaS or hospitality technology systems with third-party integrations and production risk 

• Ability to cover Pacific Time Zone hours, with minimum availability through 12:00 PM PT Monday–Friday 

• Excellent written and verbal English communication