Senior Data Engineer
G2i Inc.
—
Jul 22, 2026
—
Jul 23, 2026
What this job asks for AI summary
A greenfield role building the analytical data foundation for a pre-launch fintech startup from scratch — no existing data lake or warehouse. The engineer will design ingestion pipelines from PostgreSQL and Kafka/AWS MSK, establish governance practices (access controls, audit logging, data lineage), and contribute to platform selection across AWS-native tooling, Snowflake, and Databricks. Suits an independent, senior-level builder comfortable making architectural decisions in an early-stage environment.
Senior level · 5+ years · Remote · Full-time
“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 1,600 people nationally plausibly meet what this posting asks for (database architects). range 950–2,850
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).
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 sits at the intersection of data pipeline engineering (15-1252) and data/warehouse architecture (15-1243); it is classified as 15-1243 because the primary mandate is greenfield platform design, governance architecture, and data modeling decisions — not ongoing application software delivery.
Snowflake and Databricks appear in the required 'What They're Looking For' section alongside AWS-native tooling; all three are marked required even though the final platform choice is still being evaluated — the JD explicitly gates on 'working knowledge' of all three.
Kafka and AWS MSK are listed as interchangeable alternatives in the requirements ('Kafka, AWS MSK, or comparable streaming'); AWS MSK is captured as an alternative to Kafka.
Terraform is listed under 'Nice to Have' and is marked preferred accordingly.
SOC 2 is listed under 'Nice to Have' alongside data residency requirements; marked preferred.
No compensation figures are provided — only a description of 'competitive base salary, bonus, and equity'.
The '5–7+ years' range is treated as a 5-year minimum (lower bound of the stated range).
'Data governance' is retained as a named skill because the JD treats it as a concrete, gated practice area (access controls, audit logging, data lineage) rather than a generic concept — it is explicitly required in the qualifications section.
Ignored 1 non-technology phrase(s) as skills (responsibilities/concepts, not named tools): data governance.
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.