Data Engineer applicants have rated the interview process at J.D. Irving with 2 out of 5 (where 5 is the highest level of difficulty) and assessed their interview experience as 100% positive. To compare, the company-average is 73.7% positive. This is according to Glassdoor user ratings.
Candidates applying for Data Engineer roles take an average of 7 days to get hired, when considering 1 user submitted interviews for this role. To compare, the hiring process at J.D. Irving overall takes an average of 34 days.
Common stages of the interview process at J.D. Irving as a Data Engineer according to 1 Glassdoor interviews include:
Group panel interview: 50%
Skills test: 50%
Here are the most commonly searched roles for interview reports -
45 minutes interview with mostly behavioural and situational questions, a few technical questions based on SQL, data warehousing and data modelling. Some basic visualization questions based on Power BI and DAX.
I applied online. The process took 1 week. I interviewed at J.D. Irving (Fort Edward, NY)
Interview
The interview process was straightforward and conversational. I was asked a few basic SQL questions such as different types of joins and the languages in SQL (DDL, DML, DCL, TCL). There were also behavioral questions like how I handle conflict or manage teamwork challenges. One of the senior interviewers focused on whether I’d be comfortable collaborating directly with factory managers and personnel to understand their requirements and then build data visualizations and analytics tailored to their needs.
They also asked about my personal projects and research work, verifying what I had mentioned on my resume, and discussed some of my previous internship experiences to understand my hands-on exposure. Overall, it was a balanced mix of technical fundamentals, project discussion, and situational judgment questions.
Interview questions [1]
Question 1
“Would you be comfortable going to the factory floors, talking to managers and technicians directly, gathering their data requirements, and then building dashboards or reports based on what they actually need?”