Senior Integration Architect

Integration Strategy and Roadmap

Define and own the integrations product vision and roadmap aligned with company and customer goals.
Identify and prioritize new integration opportunities based on customer needs, partner strategy, and business impact.
Evaluate third-party platforms, APIs, and technologies to expand ecosystem capabilities.

Technical Discovery & Solution Design

Lead technical discovery and solution design sessions with developers, architects, and QA to ensure feasibility, scalability, security, and performance.
Partner with stakeholders to understand end-to-end integration requirements (source/target systems, data mapping, error handling, monitoring, authentication, and operational support model), and own architectural decisions for the platform, including cloud-native design, containerization, and API standards.

Leadership

Contribute to and enable a high-performing engineering team supporting frequent, reliable production deployments.
Drive modernization of platform delivery through CI/CD automation (e.g., GitHub Actions, Azure DevOps, or similar tools)
Establish observability and monitoring practices (e.g., Dynatrace or similar) to drive high uptime across mission-critical integrations
Introduce and champion engineering best practices, including test-driven development, domain-driven design, and cloud-native/containerized architectures

Cross-Functional & Partner Collaboration

Work closely with engineering, QA, support, professional services, sales, and customer success teams.
Serve as the primary product contact for integration partners and technical stakeholders.
Support pre-sales and implementation efforts by providing integration guidance and product expertise.

Quality, Reliability & Lifecycle Management

Define and drive integration quality standards: reliability, performance, security, compatibility, and versioning.
Manage the full integration lifecycle, including enhancements, deprecations, and documentation.
Partner with engineering to ensure integrations are observable (logging/metrics), supportable (clear runbooks), and resilient (retries, idempotency, failure modes).