Passa al contenutoPassa al piè di pagina
  • Lavori
  • Aziende
  • Stipendi
  • Per le aziende

      Migliora la tua carriera

      Scopri le tue potenzialità di guadagno, trova lavori da sogno e condividi approfondimenti su lavoro e vita privata in forma anonima.

      employer cover photo
      employer logo
      employer logo

      Intuit

      Azienda coinvolta

      Circa
      Recensioni
      Stipendi e benefit
      Lavori
      Colloqui
      Colloqui
      Ricerche correlate: Recensioni su Intuit | Offerte di lavoro di Intuit | Stipendi di Intuit | Benefit di Intuit
      Colloqui di IntuitColloqui per Data Engineer presso IntuitColloquio di Intuit


      Glassdoor

      • Chi siamo
      • Contattaci

      Aziende

      • Account Business gratuito
      • Spazio per le aziende
      • Blog per le aziende

      Informazioni

      • Aiuto
      • Linee guida
      • Condizioni d'uso
      • Privacy e scelte pubblicitarie
      • Non vendere né condividere le mie informazioni
      • Strumento per l'accettazione dei cookie

      Lavora con noi

      • Inserzionisti
      • Carriere
      Scarica l'app

      • Cerca:
      • Aziende
      • Lavori
      • Località

      Copyright © 2008-2026. Glassdoor LLC. "Glassdoor," "Worklife Pro," "Bowls" e il relativo logo sono marchi registrati di Glassdoor LLC.

      Aziende seguite

      Non lasciarti sfuggire opportunità e informazioni privilegiate seguendo le aziende dove vorresti lavorare.

      Ricerche di lavoro

      Ricevi suggerimenti e aggiornamenti personalizzati avviando le tue ricerche.

      Colloquio per Data Engineer

      25 feb 2023
      Candidato anonimo a colloquio
      Petah Tikva
      Nessuna offerta
      Esperienza negativa
      Colloquio difficile

      Candidatura

      Ho presentato la mia candidatura tramite segnalazione di un dipendente. La procedura ha richiesto 4 settimane. Ho sostenuto un colloquio presso Intuit (Petah Tikva) nel mese di nov 2021

      Colloquio

      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.

      Domande di colloquio [1]

      Domanda 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.
      Rispondi alla domanda
      9

      Altre recensioni di colloqui per Data Engineer presso Intuit

      Colloquio per Data Engineer

      29 lug 2025
      Candidato anonimo a colloquio
      Nessuna offerta
      Esperienza neutra
      Colloquio facile

      Candidatura

      Ho presentato la mia candidatura tramite un selezionatore. La procedura ha richiesto 3 mesi. Ho sostenuto un colloquio presso Intuit

      Colloquio

      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.

      Domande di colloquio [1]

      Domanda 1

      They asked me binary search
      Rispondi alla domanda

      Colloquio per Data Engineer

      18 mar 2025
      Dipendente anonimo
      Mountain View, CA
      Offerta accettata
      Esperienza positiva
      Colloquio nella media

      Candidatura

      Ho presentato la mia candidatura tramite un selezionatore. La procedura ha richiesto una settimana. Ho sostenuto un colloquio presso Intuit (Mountain View, CA)

      Colloquio

      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

      Domande di colloquio [1]

      Domanda 1

      coding skills and engineering design
      Rispondi alla domanda

      Colloquio per Data Engineer

      16 mar 2026
      Candidato anonimo a colloquio
      Atlanta, GA
      Nessuna offerta
      Esperienza positiva
      Colloquio difficile

      Candidatura

      Ho sostenuto un colloquio presso Intuit (Atlanta, GA) nel mese di ott 2023

      Colloquio

      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.

      Domande di colloquio [1]

      Domanda 1

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

      Le migliori aziende per "stipendio e benefit" vicino a te

      avatar
      AnyVan
      4.0★Stipendio e benefit