Platform Architect / Principal Platform Engineer

About the RoleQrvey is an enterprise embedded analytics and AI platform that is deployed into our customers' own cloud environments—not hosted by Qrvey.

Our customers install and operate Qrvey within their AWS or Azure accounts using Kubernetes, Terraform, Helm, and ArgoCD. As a result, deployment architecture is a core part of our product.

We are looking for an experienced Platform Architect / Principal Platform Engineer to own the architecture, design, and evolution of Qrvey's deployment platform.

This role is not responsible for operating customer environments. Instead, you will design the infrastructure platform that enables customers to deploy, upgrade, scale, monitor, and troubleshoot Qrvey independently and confidently.

You will work closely with Product Engineering, Release Engineering, Customer Enablement, and Customer Reliability Engineering to ensure every new product capability is deployable, upgradeable, observable, secure, and operationally scalable.

This role owns the "deployability" of the product.

Just as the Backend Architect owns application architecture, the Platform Architect owns deployment architecture. Every significant backend feature that changes services, dependencies, networking, IAM, storage, or operational characteristics would require review and approval from the Platform Architect before implementation begins.

That elevates deployment from an implementation detail to a first-class architectural discipline. For a customer-deployed enterprise platform. This is because Qrvey offers a deployed product, and the deployment experience is as important as the product experience for customers.

Position Summary

Own the deployment architecture of the Qrvey platform across AWS and Azure.

Design and evolve the infrastructure platform that packages Qrvey into a repeatable, secure, cloud-native product that customers can operate with minimal assistance from Qrvey.

Primary Responsibilities

1. Platform Architecture

Own the overall deployment architecture for Qrvey.

Responsibilities include:

Define deployment architecture standardsDesign runtime architectureDefine Kubernetes architectureDefine service topologyDesign high-availability architectureDefine disaster recovery architectureMaintain AWS and Azure deployment parityEstablish platform engineering standardsReview infrastructure implications of new product features

2. Infrastructure as Code

Own the infrastructure that ships with every Qrvey release.

Responsibilities include:

Terraform modulesHelm chartsArgoCD applicationsKubernetes manifestsInstallation packagesUpgrade packagesSecrets management frameworkInfrastructure automation

3. Deployment Experience

Continuously improve the customer deployment experience.

Responsibilities include:

Reduce deployment complexitySimplify installation workflowsImprove upgrade automationEliminate manual deployment stepsImprove rollback capabilitiesImprove deployment validationImprove deployment diagnostics

4. Platform Services

Own the shared platform capabilities used across all deployments.

Responsibilities include:

Logging interfacesMetrics interfacesTracing interfacesHealth APIsReadiness/Liveness standardsSecrets interfacesConfiguration frameworkInfrastructure APIs

5. Performance & Scalability

Design infrastructure that scales efficiently.

Responsibilities include:

Kubernetes resource optimizationHorizontal scalingInfrastructure sizingPerformance baselinesCapacity planningInfrastructure footprint optimizationCloud cost optimization

6. Security Architecture

Ensure secure-by-default deployments.

Responsibilities include:

IAM architectureLeast-privilege accessSecure defaultsSecret managementPolicy-as-codeInfrastructure hardeningSecurity architecture reviews

7. Product Collaboration

Partner closely with Product Engineering.

Participate in:

Product RFC reviewsArchitecture reviewsSprint planningTechnical design sessionsFeature planning

Ensure every new feature includes:

deployment impactupgrade strategyrollback strategyobservability requirementsinfrastructure implications

8. Engineering Governance

Establish engineering standards for the deployment platform.

Own:

Platform engineering standardsInfrastructure coding standardsModule design guidelinesInfrastructure documentation standardsPlatform design reviewsReference architectures

Success Metrics

Success will be measured by improvements in the following areas:

DeploymentTime required for a new customer deploymentPercentage of fully automated deploymentsInstallation success rateReduction in manual deployment stepsUpgradesUpgrade success rateUpgrade durationRollback success rateZero-downtime upgrade coveragePlatform QualityDeployment reliabilityPlatform scalabilityAWS/Azure feature parityInfrastructure consistencyCustomer ExperienceReduction in deployment-related support ticketsReduction in onboarding effortCustomer operational maturityCustomer self-service adoptionEngineering ProductivityReduction in deployment complexityReusable infrastructure modulesInfrastructure code qualityAutomation coverage

Required Technical Skills

KubernetesHelmTerraformArgoCD / GitOpsAWSAzureInfrastructure as CodeLinuxNetworkingIAMContainersCI/CDObservabilityCloud-native architecture
Preferred Experience

Designing enterprise software deployment platformsMulti-tenant or customer-managed enterprise softwareSaaS infrastructure architectureKubernetes operatorsPlatform EngineeringEnterprise security architectureInfrastructure automation at scaleLeadership Expectations

The Platform Architect is expected to:

Think in terms of platform evolution rather than individual deployments.Balance engineering simplicity with enterprise flexibility.Drive cross-functional technical decisions that affect deployment, upgrades, and customer operability.Influence architecture across Product Engineering, Release Engineering, Customer Enablement, and Customer Reliability Engineering.Continuously reduce the operational burden on customers by making the platform more self-installing, self-upgrading, self-monitoring, and self-diagnosing.

Mission Statement

Build the deployment platform that enables every Qrvey customer to install, upgrade, operate, monitor, and troubleshoot Qrvey in their own cloud with enterprise-grade reliability, security, and minimal dependency on Qrvey.