Data Engineer at Nearwater Capital
New York, NY
—
Jul 25, 2026
New York, NY
Jul 26, 2026
What this job asks for AI summary
A greenfield data engineering role at a specialty finance firm, responsible for building and owning the company's data infrastructure from scratch. Day-to-day work covers designing and operating Dagster-based pipelines, ingesting data from sources such as Bloomberg, Kafka, REST APIs, and Enfusion, and maintaining data quality and governance standards including a data dictionary. Suits an independent engineer with a financial services background who is comfortable setting architectural direction with minimal oversight.
Mid level · 3+ years · New York-Newark-Jersey City, NY-NJ-PA · 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 450 people in the New York-Newark-Jersey City, NY-NJ-PA area plausibly meet what this posting asks for (database architects). range 340–580
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 $134,433 (middle half $95,331–$179,625).
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 titled 'Data Engineer' with no level modifier; advertised seniority is Unspecified. The 3+ years requirement and scope (owning pipelines end-to-end at a small firm) support a Mid-level classification.
SOC is a judgment call: the role centers on building and owning data pipelines and defining data architecture (15-1243 Database Architects), but the emphasis on writing production Python code and building integrations also fits 15-1252 Software Developers. 15-1243 was chosen as the primary because pipeline ownership, data governance, and data dictionary stewardship are the core deliverables.
Dagster is explicitly named as the firm's current orchestration tool and is listed as a hard gate ('Exposure to one of the following tools or equivalent is a must: Dagster, Prefect, or Airflow'). Prefect and Airflow are listed as acceptable alternatives.
DuckDB is described as 'our primary analytical data store' but is framed as 'familiarity with or genuine interest in learning it' — treated as preferred rather than a hard gate.
Kafka is explicitly called 'helpful but not a requirement' — marked preferred.
Bloomberg, Enfusion, and REST APIs appear in the responsibilities narrative describing data sources the engineer will work with, not in a formal requirements section — marked preferred.
React / frontend development is explicitly called a 'nice-to-have' — marked preferred.
Claude (the AI assistant) is mentioned as an active tool at the firm, but as a workflow/productivity tool rather than a technical skill gate; omitted from the skills list.
The posting states the firm is '100% work from office' at its New York City headquarters — remote is false.
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.