Company
Sparrow
Annual salary
$100k – $135k/yr
Location
New York, NY
Listed
29d ago
- Experience:
- 2 to 4 years
- Workplace:
- 5 days in-office in New York, NY
- Equity:
- 0.05-0.15%
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.
On-site 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
We are looking for a Partner Data Analyst with 2-4 years of experience to take full ownership of how our credit union partners' data gets into Sparrow's Crest platform. Partner volume is growing fast, and our Partner Success team is spending its time fixing data problems instead of building relationships. We need a curious, pragmatic owner with an "art of the possible" mindset: someone who enjoys messy relational data, keeps asking questions until they have the answer, and can find workable solutions within the real limits of traditional financial institutions. You'll start as our go-to data troubleshooter and can quickly grow into a data leadership and governance role.
What will you be doing?
- Owning data mapping for every new partner: taking data from each credit union's banking core processor and mapping it into Crest so it can be ingested and used correctly.
- Fixing live data issues fast and pragmatically, such as fields not mapping as expected or campaign logic not being applied correctly. Your time will shift between onboarding and troubleshooting, anywhere from 50/50 to 90/10 in either direction.
- Turning complex technical findings into clear, simple explanations that Partner Success Managers can pass on to partners, with patience for teammates who aren't technical.
- Writing down and structuring a data mapping process that has so far been passed along by word of mouth, working directly with the CPO and CTO.
- Building reusable SQL/Python/JavaScript checks, automation and governance standards that stop the same problems from coming back and reduce reliance on Engineering.
Common questions
How do I apply for the Partner Data Analyst (US) role at Sparrow? +
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 Sparrow role pay? +
The listing gives $100k – $135k/yr.
Is this role remote? +
The listing gives the location as New York, NY. 5 days in-office in New York, NY.
Data Analyst interview prep
Questions Data Analyst interviewers often ask. They aren't taken from this listing.
What's your process for cleaning a dataset before starting analysis?
I start by profiling the data for missing values, duplicates, and outliers, then decide case by case whether to impute, drop, or flag issues based on how they'd affect the specific analysis. I document every transformation so the cleaning process is reproducible and reviewable, not just a black box.
How do you decide which statistical test is appropriate for comparing two groups?
I check the distribution of the data and whether the groups are independent or paired first, since that determines whether a t-test, a non-parametric alternative like the Mann-Whitney U test, or a paired test is appropriate. Choosing a test based on convention rather than the data's actual properties leads to unreliable conclusions.
What makes a data visualization misleading, even if the underlying numbers are correct?
Common issues include truncated axes that exaggerate differences, using pie charts for data with too many categories to compare visually, or choosing a chart type that implies a trend the data doesn't actually support. I try to match the chart type to the specific comparison I want the viewer to make.
How do you handle outliers in a dataset when you're not sure if they represent errors or real extreme values?
I investigate the source of the outlier before deciding how to handle it, since a data entry error should be corrected or removed, while a genuine extreme value, like a real high-value transaction, should usually stay in the dataset. Removing outliers automatically without checking their origin risks losing real signal.
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 →