I would say my interview process started off even weird with the fact I got a rejection letter than a week later a email to schedule an interview. However, I schedule the interview and it starts off as the typical get to know first line behavioral then the person began to ask technical questions. Although, caught off guard, I answer them example he asked me what was an ETL, and I told him it was a traditional data pipeline process, meaning extract, transform, and load. A simple example being when you extract a file, or data from a database, transform (ex. cleanse it, and align it to your data structure/needs), and load it to what ever storage you now want to place this data, i.e. a table in your database. He then aske me what is the largest table I work with at my current job, I told him given my CURRENT INDUSTRY, that the largest table with approx. be in the billions, or at a billion for number of records really.(Side note I didnt want to speak in gigabytes, petabytes, etc. because assuming that I am trying to give technical answers to a non technical person). I finish the interview, and about 3 days later I get a rather rude rejection letter that said I did not receive the role because I was lacking in data engineering experience. In regards to the questions I answered, I do not know how it was determined I was lacking in anything as I gave the answers any ACTUAL data practitioner would give. Honestly, I am writing this in hopes someone in HR leadership or tech leadership at this company will see this, and coach hiring managers and first line recruiters about how inappropriate it is to have first line recruiters ask technical questions, due to a. not having the knowledge to determine if a question was answered appropriately (not to a script, but what makes sense) , and b. its rude to quiz someone shortly after hello.