Skip to contentSkip to footer
  • Community
  • Jobs
  • Companies
  • Salaries
  • For Employers
      Notifications

      Loading...

      Elevate your career

      Discover your earning potential, land dream jobs, and share work-life insights anonymously.

      employer cover photo
      employer logo
      employer logo

      Intuit

      Engaged Employer

      About
      Reviews
      Pay & benefits
      Jobs
      Interviews
      Interviews
      Related searches: Intuit reviews | Intuit jobs | Intuit salaries | Intuit benefits
      Intuit interviewsIntuit Data Engineer interviewsIntuit interview


      Glassdoor

      • About / Press
      • Awards
      • Blog
      • Research
      • Contact Us
      • Guides

      Employers

      • Free Employer Account
      • Employer Center
      • Employers Blog

      Information

      • Help
      • Guidelines
      • Terms of Use
      • Privacy & Ad Choices
      • Do Not Sell Or Share My Information
      • Cookie Consent Tool
      • Security

      Work With Us

      • Advertisers
      • Careers
      Download the App

      • Browse by:
      • Companies
      • Jobs
      • Locations
      • Communities
      • Recent Posts

      Copyright © 2008-2026. Glassdoor LLC. "Glassdoor," "Worklife Pro," "Bowls," and logo are proprietary trademarks of Glassdoor LLC.

      Company Bowl sample

      Want the inside scoop on your own company?

      Check out your Company Bowl for anonymous work chats.

      Bowls

      Get actionable career advice tailored to you by joining more bowls.

      Followed companies

      Stay ahead in opportunities and insider tips by following your dream companies.

      Job searches

      Get personalized job recommendations and updates by starting your searches.

      Data Engineer Interview

      Feb 25, 2023
      Anonymous Interview Candidate
      Petah Tikva
      No offer
      Negative experience
      Difficult interview

      Application

      I applied through an employee referral. The process took 4 weeks. I interviewed at Intuit (Petah Tikva) in Nov 2021

      Interview

      Hiring process consists of 6 interviews: First round: 1 hour of technical questions about Big Data concepts, different AWS resources that I am familiar with, their main usage proc and cons, SQL queries and Spark infrastructure. Second round - home assignment. 3/4/5/6 4 tech rounds in a single day: Craft Demo Presentation Technical interview about the assignment Cultural-functional interview Hiring Manager interview I had a very bad experience with this company. The requiter called me on my day off (in Israel its Friday). First time was "to help me to prepare" for the round day of the final 4 interviews with the presentation. He provided me some not really useful info and types. Nothing that couldn't wait till the beginning of the next week. Second time is was to let me know that I didn't pass the round day and list me all the reasons why. It was very disrespectful to call me again on my day off and ruin me my whole weekend. Also the reasons that he said sound like they misunderstood and maid their own interpretation to everything that I said. And when I mentioned that he works a lot on our off days he said "not that much, only when I have too". Well, I prefer that my days off will stay that way. For me its disrespectful for others family time. Beside that all the process felt very stressful like I was constantly and heavily gauged, even for being nervous during the interview. Sorry that being interviewed 4 hours in a row by different bunch of people is a stressful situation for me.

      Interview questions [1]

      Question 1

      Home assignment: Quick Books Online (QBO) is Intuit’s offering to run accounting for small businesses. QBO customers are called merchants - typically small businesses or self-employed. These merchants prepare invoices for their customers and we track payments made against these invoices. Your assignment is to build a small data mart to track payments made to QBO merchants by their customers. Description of main business entities: • Every merchant has a number of properties – Merchant Id (unique), Merchant Name, Address, Phone Number, Email • Every payment is made by a customer to a merchant • Every payment has a payment Id (unique), payment amount, a payment method (for example Visa, Mastercard, Check – there may be many more), and a status – for the sake of this assignment we only support 3 statuses: Pending, Paid, Rejected • Every payment has a payment date – a timestamp that the payment occurred • We have simplified the scope of this assignment: o Every customer has a unique customer Id and no additional properties. No need to track customers o Similarly for this exercise we don’t reference invoices at all Description of Database source objects: We have created two tables in Redshift Operational Data Store (ODS) schema: • Merchants • Payments Both payments and merchants are updated in the data warehouse once per day. Both tables contain the field ingestion_date, referring to the day that the table was ingested into the ODS. For Merchants table all rows are processed every day. For Payments table only new or changed rows are processed. Assignment 1 - DB 1. Create tables as they will appear in the data mart – You can optionally create additional schemas for these tables. 2. Create SQL scripts to load the data mart tables – one script for each target table. 3. Be prepared to explain your design decisions Assignment 2 - Application Purpose: An internal team needs access to the data you created in the Data Mart section. In their use-case, they are trying to assess if a merchant receiving a payment now has a history of an abundance of rejected payments. This information is important for fraud assessments, as it may indicate that the merchant is defrauding QBO. Requirements: For this use case, we are asked to provide the following: Data Engineering Craft Demonstration Exercise Page 2 of 2 1. The total number of payments for a given merchant with status “Rejected” over the past 7 days 2. The total number of payments for a given merchant over the past 7 days 3. The total payment amounts of rejected payments for a given merchant over the past 7 days 4. The total payment amounts for a given merchant over the past 7 days Implementation: Create a Python application, which provides an api to fulfill the requirements above. The application should: 1. Leverage the data mart you used in the previous section 2. Leverage REST API Be prepared to explain your design decisions.
      Answer question
      9

      Other Data Engineer Interview Reviews for Intuit

      Data Engineer Interview

      Jul 29, 2025
      Anonymous Interview Candidate
      No offer
      Neutral experience
      Easy interview

      Application

      I applied through a recruiter. The process took 3 months. I interviewed at Intuit

      Interview

      The interviewer was okay but the recruitment process was extremely slow. It took many months for them to even review my resume. The actual interview was fairly easy. The first question is just basic binary search.

      Interview questions [1]

      Question 1

      They asked me binary search
      Answer question

      Data Engineer Interview

      Mar 18, 2025
      Anonymous employee
      Mountain View, CA
      Accepted offer
      Positive experience
      Average interview

      Application

      I applied through a recruiter. The process took 1 week. I interviewed at Intuit (Mountain View, CA)

      Interview

      First round with manager or a senior person from the team, secodn with the whole team. Contractor, 2 rounds, conversation and coding, Both were moderate difficulty. Both video calls via zoom

      Interview questions [1]

      Question 1

      coding skills and engineering design
      Answer question

      Data Engineer Interview

      Mar 16, 2026
      Anonymous Interview Candidate
      Atlanta, GA
      No offer
      Positive experience
      Difficult interview

      Application

      I interviewed at Intuit (Atlanta, GA) in Oct 2023

      Interview

      I enjoyed the interview experience thoroughly because I felt that they actually evaluated skills that were relevant to the role. I made it to the final interview (2nd or 3rd interview was the final as of Oct 2023). The first - or the first and second interview - were both behavioral and I believe they gave me a quick coding interview question in which they went over some of the easier coding interview questions you'll often come across in SQL. It felt like they administered that test just to confirm that I knew how to code sufficiently, not that they were relying on it to determine if I was competent for the job. For the real technical evaluation, I was given 3 weeks and a zip file of sample data along with some guided questions to answer when exploring the data. They did have specific questions that the wanted me to answer and demonstrate about the data, but they were relatively open-ended. Through this test they not only evaluated my technical skill, but my ability to communicate important info about the data. I was not accepted for the position, I wasn't a very good communicator a t this point in my career. That interview was about 2.5 years ago now, but it has always left an impression on me because I hate when interviews essentially only evaluate whether you have memorized all of the common coding interview questions - many of which are algorithms that took people time and research to develop. I feel like the plot is often lost during technical interviews and felt that Intuit does not fit that description. They have full handle of the plot, lol. The interview team was very kind as well.

      Interview questions [1]

      Question 1

      They asked me a SQL coding question and asked me to analyze some data that I had 3 weeks to review.
      Answer question