
Itential Interview Questions
& Process
Real candidates share what happened, how many rounds they had,
and how the experience turned out.
Based on 44 interview experiences · FREE TO READ
Which role are you interviewing for?
8 roles · 44 reportsCandidate interview experiences
First-hand accounts from people who interviewed at Itential.
Automation Engineer
The first interview was about 30 minutes, covering personality and networking, and giving me details about the role. The second interview focused on their specific automation tool, requiring prior knowledge. It involved demonstrating how to use the tool and manipulate JSON for automation. Although the interviewer seemed impressed with my use of their platform and expressed interest in hiring me, I was ultimately not selected, receiving a vague email about them moving forward with another candidate.
- Can you use the provided JSON Tool to retrieve the email addresses of all company employees?
Delivery Engineer
The whole thing took like 2 months to wrap up, which felt pretty long. It kicked off in August with a phone chat where they hit me with OOP and data structure stuff, plus some questions about my past work. Round two was a video call where we talked about my resume history and then I had to do a JavaScript coding test. After that, it went straight into three 45-minute interviews back-to-back, so 135 minutes of interviews with no breaks at all. The first part had more technical questions about my background and then a tougher JavaScript coding challenge than the last one. I totally tanked that one because I couldn't finish on time, and I'm pretty sure that's why I didn't get the offer. The second part was a system design question, and the interviewer was cool and actually helpful. The final part was a barrage of behavioral questions, and they also threw in async vs sync execution, which I'd never even heard of in college or my last internship. My mouth was SO dry from all the talking and I wish they'd been a bit more considerate with a small break between those long interview blocks. It really sucks to get rejected after investing so much time and effort into such a drawn-out process.
- What are your thoughts on OOP, Data Structures, and JavaScript?
- Can you tell me about your background?
- What about your past experience mentioned on your resume?
Software Engineer
Applied for a university grad position and the whole process lasted about a month. It was a really positive experience! The entire process took about a month. There were 3 rounds. First, an initial phone screen with the Director of Operations where I was asked to talk about my resume, basic OOPs concepts, and SQL vs NoSQL. Second, a virtual technical round where my screen was shared. I was asked a coding question and to code on an online compiler. What really stood out was that the interviewer allowed me to use google (the test was "open book") and was noting down what I googled. The interviewer was really helpful as well while solving the problem. Third, 3 sets of On-Site Interviews with a panel of 2 developers in each. They asked questions from my resume, one data structure question in each, and one system design question each in all rounds. The questions made sense and were not generic. All the design questions were based on real-life problems encountered by the company. Overall, really great experience. The interviewers were really helpful and great to talk to, relevant questions and a generally positive vibe about the whole process. Accepted offer without any second thoughts.
- Tell me about why you're interested in Itential?
Applications Engineer
I had a phone screen with the Product Manager and it went well. Then I was invited for 3 more rounds of interviews, with 2 interviewers each. The first two rounds were with people from the Product team, and the last round was with the Product Manager and another manager. I felt like the questions were more for experienced people rather than entry-level, which was a bit of a bummer since they said it was entry-level in the first call. After all that, they ghosted me even though I followed up a few times.
- What steps do you take to guarantee cross-browser compatibility for your applications?
Itential Interview Questions
Quoted word for word from Itential interview reports.
“What is the difference between HTTP and HTTPS?”
Read reports →“What distinguishes a binary search tree from a binary tree?”
Read reports →“What is the difference between a linked list and a Binary Search Tree (BST)?”
Read reports →“Can you explain what a broadcast domain is?”
Read reports →“What is the difference between synchronous and asynchronous operations?”
Read report →“Could you explain how to find the middle element of a linked list?”
Read report →“How would you evaluate the postfix notation of an expression?”
Read report →“What's the difference between Async and Sync Execution?”
Read report →“Can you explain what a linked list is in simple terms?”
Read report →Formats, difficulty and experience
Across all 44 Itential interview reports.