Senior Data Engineer
SpyCloud · Austin, TX
$144,000–$187,000from the description
Jul 19, 2026
Austin, TX
Jul 21, 2026
What this job asks for AI summary
A senior individual contributor and technical leader responsible for modernizing a data platform built on Databricks and AWS, designing and maintaining batch and real-time pipelines, and preparing data for machine learning and large language model applications. The role involves mentoring other data engineers and collaborating with product and engineering teams. It suits an experienced data engineer with a background in large-scale distributed architectures and hands-on pipeline development.
Senior level · 8+ years · Remote · Full-time
“or” means any one of them counts — you don't need all of them.
Posted 2 times — it's one opening, so apply once.
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 410 people nationally plausibly meet what this posting asks for (database architects). range 250–740
Applicant volume Moderate — A normal amount of company. The rare requirements below are what will separate a shortlisted application from the rest.
Most people in this occupation already list these. Still required — just not what gets you shortlisted.
What the occupation pays Median $142,568 (middle half $111,775–$173,013). This posting is about at that midpoint.
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)
The role is genuinely ambiguous between data/lakehouse architecture (15-1243) and general software engineering (15-1252). The primary framing is data platform modernization, Lakehouse/Databricks architecture, and pipeline design, which tips toward 15-1243, but the hands-on pipeline coding, ETL scripting, and ML workflow work are also consistent with 15-1252.
The JD lists AWS tools (Lambda, S3, DynamoDB, ECS, EKS, Terraform) together in a single bullet under 'What You'll Do' rather than under a dedicated requirements heading. However, the Requirements section explicitly calls out DynamoDB and AWS-native data services, Elasticsearch/OpenSearch, Databricks/Lakehouse, and Python as hard gates; the AWS tool list is treated as required context for the role's day-to-day work.
RDS and Elasticsearch appear in the intro framing ('purpose-built data stores') and are reinforced in the Requirements section; both are marked required.
LLMs are mentioned as a workflow context ('ML models and LLM applications') rather than a named tool, so no standalone LLM skill is emitted; SageMaker, LangChain, and vector databases are explicitly listed under 'Nice to Have'.
Bachelor's or Master's degree is listed under 'Nice to Have', so the degree requirement is set to None — equivalent experience is implicitly accepted.
C and Go programming experience appear under 'Nice to Have', as does experience with password cracking tools (too vague/non-standard to emit as a named technology skill).
The posting mentions both Austin office and 'flexible and remote-friendly work options', supporting remote=true. The metro is set to Austin-Round Rock-Georgetown, TX as the company's headquarters location.
The 2+ years in a technical leadership or senior engineering role requirement is a role-level gate captured in the overall years minimum (8+ years overall); the leadership tenure is a qualifier on the type of experience, not a separate named-technology demand.
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.