
Resultant Interview Questions
& Process
Real candidates share what happened, how many rounds they had,
and how the experience turned out.
Based on 33 interview experiences · FREE TO READ
Which role are you interviewing for?
12 roles · 33 reportsCandidate interview experiences
First-hand accounts from people who interviewed at Resultant.
Technical Support Specialist
It was a 3 part process. First, they checked my basic skills and if I understood the job description. Then, I met the hiring manager and HR. Finally, there was a technical interview with a lead engineer.
- Tell me about your experience with Azure, as mentioned on your resume.
- What do you know about the Azure platform?
Client Service Network Engineer
I had 3 rounds of interviews, it started with a screening and then 2 technical interviews. The second interview, I was interviewed by a systems administrator who stated he was not a network professional. He had a precompiled list of questions related to mostly cisco equipment, even though I had let the interviewer know that I was mostly experienced in Fortinet. 2 days later I had been told I was not moving forward, with no feedback as to why.
- What would be your troubleshooting steps if a vpn tunnel between two devices failed to establish?
Data Engineer
Please don't interview for this company. A lot of reviews have mentioned here that it's a complete waste of time. The HRs think they are above all candidates and do not do basic communication, which even HR's from Fortune 50 companies do. They close out positions after keeping candidates waiting for 3 months without any response during that period. They keep posting newer positions and never fill them, wasting candidate time and effort. I believe they just want to collect applicant data for internal use purpose.
- What are your salary expectations?
- Can you discuss the tools mentioned on your resume?
Azure Databricks Administrator
Recruiter was unclear about the interview schedule and didn't give proper info about the rounds, initially stating there would be 3 rounds, but then changing the process. All 3 rounds were with the same person. The first 2 rounds focused on data engineering concepts, and the 3rd round was more about Databricks admin, but the questions weren't clear and it was hard to tell what answers were expected. The job description was very vague, making it unclear if the role was entry-level or senior. Following up with the recruiter was difficult as responses were not timely or accurate. It felt like a waste of time.
- What are your thoughts on scenario-based questions related to Databricks administration?
Resultant Interview Questions
Quoted word for word from Resultant interview reports.
“What are the three 2.4Ghz channels that can be used?”
Read reports →“What would be your troubleshooting steps if a vpn tunnel between two devices failed to establish?”
Read reports →“Could you define process modeling?”
Read reports →“Given a Python data structure question, can you solve it?”
Read reports →“When collecting information from various sources, how do you determine its relevance?”
Read report →“How would you fix this code?”
Read report →“What's the best number to get in touch with you?”
Read report →“Can you explain the distinction between a Data Engineer and a Project Manager?”
Read report →“What do you know about the Azure platform?”
Read report →Formats, difficulty and experience
Across all 33 Resultant interview reports.