Company
PlayMaker
Annual salary
$180k – $220k/yr
Location
New York, NY
Listed
25d ago
- Experience:
- 2 to 6 years
- Workplace:
- In office 3 days per week, little to no travel unless interested.
- Equity:
- Up to 1%
Open to people who live in the US, Canada or the UK
We can only put candidates forward for this role from those three countries for now. See the contract AI training jobs open in more countries.
Hybrid in New York, NY.
Send us your LinkedIn and CV. If your experience fits, we'll introduce you to the recruiter filling this role.
Apply for a referral →The recruiter emails you before anything happens and may suggest other jobs that suit you better.
About this role
PlayMaker is the operating system for sports sponsorship, and this role will lead the effort to transform customer onboarding from a manual project into a scalable, automated product.
This is a founding level hire, where you will have strong influence on the trajectory of the product. You will own the ingestion, contract-to-inventory matching, and data warehouse architecture, ensuring customer data is flexible, trustworthy, and reportable.
You will partner with the CTO to evolve the system of record while building tools that allow for data reconciliation and integration.
Common questions
How do I apply for the Founding Data Engineer, Data Platform (US) role at PlayMaker? +
Use the Apply for a referral button on this page to send us your LinkedIn and CV. If your experience fits, we'll introduce you to the recruiter filling this role. They'll email you to check you're interested, then put you forward for this job or others that suit you better. It's free.
What does this PlayMaker role pay? +
The listing gives $180k – $220k/yr.
Is this role remote? +
The listing gives the location as New York, NY. In office 3 days per week, little to no travel unless interested.
Data Engineer interview prep
Questions Data Engineer interviewers often ask. They aren't taken from this listing.
How do you design an ETL pipeline to be idempotent so reruns don't duplicate data?
I design loads around upserts keyed on a natural or surrogate key rather than plain inserts, and I make each pipeline stage stateless with respect to its inputs so rerunning it with the same input produces the same output. Partitioning by a processing date and overwriting the whole partition on rerun is another reliable pattern, especially for batch pipelines.
When would you choose a star schema over a snowflake schema for a data warehouse?
A star schema keeps dimension tables denormalized, which trades storage and some data redundancy for simpler, faster queries. That's the right call when query performance and ease of use for analysts matter more than storage efficiency. A snowflake schema is worth the extra join complexity when dimension tables are large, change frequently, and normalization meaningfully reduces storage and update anomalies.
How do you handle schema evolution in a pipeline that ingests data from a source you don't control?
I treat the ingestion layer as schema-tolerant by landing raw data first, before any strict schema is enforced, and applying schema validation at a later transformation stage. This way a new or renamed field upstream doesn't break ingestion outright. I also version the schema explicitly so downstream consumers can detect and handle changes rather than silently breaking.
What's your approach to choosing between a batch and a streaming architecture for a new data pipeline?
The deciding factor is how fresh the data needs to be for the downstream use case, not how technically interesting streaming is. If consumers only need daily or hourly updates, batch is simpler to build, debug, and operate. Streaming is worth the added complexity only when there's a real requirement for near-real-time data, like fraud detection or live dashboards.
Related roles
Browse all referral roles
Salaried roles at startups, AI companies and established businesses, all filled by referral. One application covers every role.
See all referral roles →