A business intelligence engineer, or BI engineer for short, will probably receive several questions about their ability to use scripting languages, processors, and programs used by the prospective employer's company. Though some questions about human relations may come up, the BI Engineer interview may be more involved with your experience level in data analysis.
Here are three top BI engineer interview questions and how to answer them:
How to answer: Going into the interview, you'll want to be prepared to talk about a past project you can thoroughly talk about. Whether it's because of the people you worked with or your contribution to making it successful, showing that you have a passion for your work is key. Be sure to highlight the skills you used for the project.
How to answer: BI engineering is all about using tools to analyze data. You may likely get an interview question about the tools you're comfortable using. Be sure that you can confidently speak about the languages, programs, and software you claim proficiency in.
How to answer: It's very likely your interview for a BI engineer position will contain a puzzle or problem that you must solve. Whether it's how to handle a SQL issue or calculating performance in Tableau, you should be ready to answer it. Generally, in-depth knowledge of the tools required by the job posting will help you successfully navigate these questions.
↳
Dod they communicate to yoy about the offer or not then?
↳
No I have followed up many times. They are not answering call... I just asked 5% more than what they were offering... Less
↳
How much increment did they offer?
↳
Solved it! select state from geo group by state where count(*) > 1;
↳
select state from employee group by state having count(cityname)1
↳
select state from employee group by state having count(cityname)1
↳
Cite your CV, and show up SQL statements or procedure for the problem.
↳
Can you please tell me what kind of sql statements were they
↳
I answered second bag. But, he said it was wrong.
↳
coin is in first bag as: put first statement false i.e. coin is not in third in third bag put third statement true i.e. coin is not in third bag so it's concluded by two statements that coin is not in third bag. now put the second statement true which says coin is not here i.e. coin is not in 2 or 3 bag Less
↳
Use CTE.
↳
or to clarify duplicates into a staging table when you are taking a subset of all the fields and you know what specific fields you are after, INSERT INTO > (>) SELECT > FROM (>) GROUP BY > having count(*)>1 and to add only those that are not duplicates INSERT INTO > (>) SELECT > FROM >) T GROUP BY > having count(*)=1 Less