
Petal Data Engineer Interview Questions
& Process
Real candidates share what happened, how many rounds they had,
and how the experience turned out.
Based on 5 interview experiences · FREE TO READ
Candidate interview experiences
First-hand accounts from people who interviewed at Petal.
Senior Data Engineer
Started with a 30 min phone call with a tech recruiter to discuss my expectations and the role/company. Then, there were tech rounds with two data engineering team members. The first was with a guy from the data eng team who gave me some schemas and sql questions. I felt he wasn't qualified to interview me, as he struggled with basic SQL concepts like case statements. This interview is where I got negative feedback about my SQL skills, which was frustrating because I believe the interviewer lacked knowledge. The second interview was a higher-level design problem with someone who seemed knowledgeable and straightforward. A couple of days later, I was told they weren't moving forward because the first tech round didn't go as they expected. My advice is to ensure interviewers are competent engineers to avoid wasting candidates' time.
- Regarding the schemas provided, how many cards has customer '1544' possessed?
- Identify customers who have not made any transactions using any of their cards.
- Calculate the total transaction value per customer, broken down by month.
Data Engineer
I had an HR chat first, then did a take home coding challenge that took about 30 minutes. After that, we had a technical interview where we talked about the take home assignment. Then, I had a virtual on-site interview that lasted 4 hours and I met with 6 people.
- Can you use SQL window functions to summarize user transactions?
Data Engineer
The interviewer was really nice and understanding. It was detailed, but fairly easy. As long as you do your research on the company and know what you're doing, you are good.
- What is your motivation for wanting to join Petal?
Petal Data Engineer Interview Questions
Quoted word for word from Petal interview reports.
“What is the current card_number for each customer?”
Read reports →“Regarding the schemas provided, how many cards has customer '1544' possessed?”
Read reports →“Using SQL, can you explain how to calculate the moving average of a metric?”
Read reports →“Considering the card table and the rule that a customer can have only one active card at a time, how would you ascertain the close_date for each card?”
Read reports →“Can you implement an LRU cache in Python 3 that runs in constant time, using any available Python data structures, and pass the given unit tests within 15 minutes?”
Read report →“Can you use SQL window functions to summarize user transactions?”
Read report →“How would you go about designing a SQL script and report pipeline, considering these tables?”
Read report →“What are your thoughts on using SQL aggregation and window functions for this specific dataset?”
Read report →“This current model is not very user-friendly for analysts. We want to build an analytical model in Redshift. Here are some of the questions these analysts might want to answer: 1.) How many applications were approved? How many yesterday? 2.) How many of these applications were manually decisioned? 3.) How many potential customers dropped off between Prequalification and Application? 4.) What is our distribution of customers by income?”
Read report →Formats, difficulty and experience
Across all 5 Petal interview reports.