Senior Data Architect
73 Strings · New York, NY
—
Jun 29, 2026
New York, NY
Jul 20, 2026
What this job asks for AI summary
A senior technical leadership role focused on designing and evolving a cloud-based data platform for a private capital software company. The work spans defining enterprise data architecture strategy, building data warehouse and lakehouse solutions on Snowflake and Databricks, architecting REST and ETL/ELT integrations, and guiding implementation teams during client onboarding. The role suits an experienced data architect comfortable bridging hands-on engineering with cross-functional technical advisory responsibilities.
Senior level · 8+ years · National
“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
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 $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 (7)
No work location or city is specified in the posting; CBSA and state fields are left blank. The company (73 Strings) appears to be a global fintech firm, but the role's primary geography cannot be determined from the JD alone.
Snowflake and Databricks are listed together as a paired requirement ('such as Snowflake, Databricks') under the Requirements section. They are treated as a hard gate on cloud data platform expertise, with each listed as an alternative for the other since either alone would likely satisfy the requirement.
Kafka, Flink, and Spark are listed together as examples of 'real-time and streaming data platforms' in the Requirements section. Each is marked required with the others as alternatives, reflecting that the JD gates on streaming platform expertise broadly.
AWS, Azure, and GCP are listed as alternatives under a single cloud platform requirement ('AWS, Azure, or GCP'); AWS is used as the primary name with the others as alternatives.
GraphQL appears in the 'What You'll Do' responsibilities section (not the Requirements block) and is therefore marked preferred.
Vector database / embedding infrastructure experience and LLM/RAG architecture knowledge are both explicitly listed in the Requirements section and are marked as hard gates, which is somewhat unusual — this reflects the company's AI-powered platform focus.
The role blends data architecture, data engineering, API development, and pre-sales/client-facing advisory work. 15-1243 (Database Architects) is the best fit for the primary day-to-day work, but 15-1252 (Software Developers) is a credible runner-up given the hands-on API and pipeline engineering scope.
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.