Platform Engineer
Meibel · Tysons, VA
—
Jul 12, 2026
Tysons, VA
Jul 20, 2026
What this job asks for AI summary
A platform engineering role focused on designing and maintaining the infrastructure underpinning an AI platform across both cloud and on-premises environments. Day-to-day work spans Kubernetes cluster management, infrastructure-as-code with Pulumi, CI/CD pipelines via Argo, workflow orchestration with Temporal, and integration of graph, vector, and relational databases. Best suited to engineers with a strong DevOps or SRE background and hands-on experience with hybrid deployments.
Senior level · 4+ years · Remote
“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
Roughly 2,850 people nationally plausibly meet what this posting asks for (software developers). range 840–4,300
Applicant volume Moderate — A normal amount of company. The rare requirements below are what will separate a shortlisted application from the rest.
Rare in this occupation — lead with these, and say what you built with them.
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 (9)
No location is specified beyond 'remote-friendly'; the role appears fully remote with no stated geographic restriction, so no CBSA could be assigned.
SOC classification is a genuine judgment call: the role is titled 'Platform Engineer' and the JD emphasizes building infrastructure-as-code (Pulumi), CI/CD pipelines (Argo), and internal tooling — work that ships code — which points to 15-1252 Software Developers. However, a meaningful portion of the work (Kubernetes operations, monitoring, hybrid cloud/on-prem management) could support 15-1244. 15-1252 was chosen because the primary deliverables are code-built systems, not operations of existing infrastructure.
Pulumi is listed as the primary requirement with Terraform accepted as a substitute ('or strong experience with Terraform and interest in Pulumi'); Terraform is captured as an alternative.
Temporal is listed as required with 'or similar workflow orchestration engines' — no specific named alternatives are given in the JD; well-known substitutes (e.g. Apache Airflow, Prefect, Dagster) would likely be accepted.
Vector databases (Pinecone/Weaviate/Qdrant) and graph databases (Neo4j/TigerGraph) appear under 'Familiarity with' language in the requirements section, indicating a softer gate; they are marked preferred accordingly.
Relational databases are required ('Familiarity with… Relational databases e.g. PostgreSQL, MySQL'); PostgreSQL is emitted as the primary with MySQL as an alternative.
Bonus Points items (AI/ML pipeline experience, compliance/multi-tenancy, open source contributions, internal developer platforms) are not emitted as skills as they are explicitly framed as optional extras.
No compensation figures were provided in the posting.
This posting reads as a fully-remote role, so it was scored against the national candidate pool rather than a single metro.
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.