Seattle, WA

Salary
Posted
Jul 9, 2026
Location
Seattle, WA
Last confirmed open
Jul 21, 2026

What this job asks for AI summary

A senior individual-contributor engineering role focused on the foundational platform layer of an HCM suite spanning HR, recruiting, payroll, and benefits. The work centres on defining technical strategy, designing distributed shared services and APIs, leading modernisation efforts, and contributing hands-on to critical platform code. Suited to a seasoned engineer with a strong background in scalable platform or shared-services development and a track record of setting architectural direction across multiple teams.

Principal level · 8+ years · National

Must have (7)
distributed systemsRESTKafka or RabbitmqDockerKubernetesGitCI/CD
Nice to have (2)
GCP, AWS or AzureAI/ML

“or” means any one of them counts — you don't need all of them.

We read this from the posting text with AI. Skim the description below before ruling yourself out.

How this req sits in the market our data

What gives you an edge
Kafka12%

Rare in this occupation — lead with these, and say what you built with them.

What won't set you apart
Docker53%CI/CD45%

Most people in this occupation already list these. Still required — just not what gets you shortlisted.

What the occupation pays Median $138,970 (middle half $107,524–$175,762).

Estimated from BLS employment for this occupation and area, per-skill prevalence across our listing corpus, and published wage benchmarks — as of Jul 28, 2026. It is a model, not a headcount.

Why we read it this way (5)

Remote eligibility is not stated; remote is set to false by default.

The degree requirement is 'Bachelor's degree in Computer Science or related field, or equivalent experience' — the explicit equivalent-experience escape means no hard degree gate.

GCP is listed as 'preferred' in the requirements section ('GCP experience preferred'), so it is marked as a preferred skill with AWS and Azure as common cloud-platform alternatives.

AI/ML tools in engineering workflows or product capabilities appears only in the trailing 'nice to have' block and is marked preferred.

The role carries no explicit title or level label, but its scope — owning org-wide architecture, setting technical standards across multiple product and platform teams, and driving long-term technical strategy for a foundational HCM platform — is consistent with a Principal-level individual contributor, not merely a Senior engineer. Seniority is assessed as Principal accordingly.

Read the full posting

The employer publishes the full description on their own site — read it there ↗. Or sign in to read it here — it's free, and it also lets you track this application.

Apply

Apply on employer site ↗