
Quanata Interview Questions
& Process
Real candidates share what happened, how many rounds they had,
and how the experience turned out.
Based on 41 interview experiences · FREE TO READ
Which role are you interviewing for?
21 roles · 41 reportsCandidate interview experiences
First-hand accounts from people who interviewed at Quanata.
Engineering Manager
The entire process from applying to getting the offer took around 5 weeks. It was a really well-thought-out and organized interview process. What stood out was how curious, kind, and welcoming all the interviewers were. The recruiters were also amazing, providing lots of individual support. There were just the right number of check-ins to make me feel confident that my skills and how I work would fit well with BlueOwl.
- Could you describe your experience related to culture and working style?
- Tell me about your past experience.
- Let's do a project retrospective focusing on technical implementation details.
Data Warehouse Engineer
I had a 30 minute phone call with a recruiter, followed by a 45 minute video interview with two employees. During the video interview, the employees discussed a shift in the company's strategic direction, but were vague about specifics, even with an NDA signed. This suggests a lack of clear direction currently within BlueOwl. The interview heavily emphasized specific Python skills, despite my extensive experience in Java and other programming languages. My significant experience with SQL, Snowflake, dbt, data quality, data governance, AWS, CI/CD, and Terraform was largely overlooked. The interviewers seemed unaware of my background in Java rather than Python, which I had disclosed to the recruiter. A large part of the interview focused on Python over other technologies mentioned in the job description. The interviewers didn't seem to assess emotional intelligence (EQ) or a balance of IQ and EQ, focusing instead on specific language skills. I believe EQ is crucial for software engineers, alongside a sufficient IQ, for them to excel and be valuable contributors, especially in asking critical questions and improving processes. The interview lacked discussion of core values, company vision, or mission. When I asked about company culture, the response was that they only have senior-level engineers and operate with minimal supervision, with no mention of diversity. One interviewer came across as arrogant and interruptive, while the other seemed to have a narrow focus on Python expertise.
- Tell me about your experience with Snowflake.
- How proficient are you with dbt?
- What's your background with PostgreSql?
Finance Systems Manager
It was a long and frustrating interview process. We had many remote calls with the team, but the technology made it hard to hear and understand the questions. I eventually gave up and said I couldn't answer. Then some condescending system engineers who didn't grasp that Agile applies to both project management and software engineering told me I hadn't answered their questions. There was also no communication about arrival, parking (which is tricky in Providence), the scent-free policy, or the 'compensated interview' with an NDA that never actually got compensated.
- What steps would you take if the revenue software was inaccurately calculating figures?
- Could you tell me your favorite movie and the reasons why?
- How would you go about managing projects using Agile principles?
Lifecycle Marketing Manager
The recruiter reached out on LinkedIn to set up a time, and we had a phone chat about the company, the role, and what they were looking for. It was a good conversation, but we couldn't lock down the next interview right away. After that, I spoke with the hiring manager, Kayla. She was straightforward, smart, and nice. She dug deep into the company, the role, and expectations. She asked good questions about my lifecycle marketing skills and experience, asking for real-life examples. She also laid out the next steps: a 4-hour video interview with the team, including a 2-hour 'homework simulation.' Scheduling the final round took over two weeks because of busy schedules. On the interview day, as promised, I got the homework simulation two hours before the first interview. It was a pretty standard lifecycle marketing task. I liked that they gave us only 2 hours before the interview and didn't use their actual company in the case study, so I didn't feel pressured to spend hours unpaid building them a marketing plan. They also offered to pay for the 2 hours spent on the exercise. I felt like I was on 'Top Chef,' given a task to cook up a strategy and present my dishes to judges in 2 hours. The interview was broken into 4 segments, about 45 minutes each, with breaks, plus a quick initial call with the hiring manager. Each segment had a specific focus, and 3-4 people were in each video call, so no one repeated questions from other segments. Everyone asked smart, interesting questions and shared helpful info about their jobs. I thought the whole process was really well-planned and detailed, and I genuinely enjoyed talking to everyone. By the end of the nearly 4-hour interview, I was wiped out but also pumped. I was interviewing with others actively. On my interview day, I got an offer from another company. I let the hiring manager know since this company was my top choice. She tried to speed things up internally, but it had only been a day or so since our interview. After a few days, I had to make a tough choice; a bird in hand is worth two in the bush(?) - so I took the offer I had. But I'd totally recommend this company based on how they structured the interview process for the Lifecycle Marketing role. They all seemed like great people to work with.
- Regarding the lifecycle marketing task, can you describe your skills and experience?
- Could you provide specific examples from your background that demonstrate your lifecycle marketing abilities?
- Your assignment is to create a lifecycle program for a hypothetical company, 'x company,' aimed at acquiring new customers and re-engaging inactive ones, with some additional parameters.
Quanata Interview Questions
Quoted word for word from Quanata interview reports.
“What is a generator in Python?”
Read reports →“Write code to scrape text from a URL and create a persistent word cloud.”
Read reports →“Explain the differences between OLAP and OLTP.”
Read reports →“Given some messy code, can you refactor it? Test cases are provided to ensure correctness.”
Read reports →“Can you explain what a context manager is in Python?”
Read report →“What is concurrency?”
Read report →“Could you tell me your favorite movie and the reasons why?”
Read report →“What steps would you take if the revenue software was inaccurately calculating figures?”
Read report →“There were simple coding questions like, "how do you reverse a string?"”
Read report →Formats, difficulty and experience
Across all 41 Quanata interview reports.