ITWorx Software Engineer Interview Questions
& Process
Real candidates share what happened, how many rounds they had,
and how the experience turned out.
Based on 38 interview experiences · FREE TO READ
Candidate interview experiences
First-hand accounts from people who interviewed at ITWorx.
ITWorx
Software Engineer
Mid Average Positive experience Accept offer 4 rounds
Interview process
Recruiter call Technical screen Technical screen Onsite Background check Offer
Interview formats
Behavioral Technical Coding System Design
The ItWorks interview process was pretty buttoned-up and took around 2-3 weeks from when I applied to getting the offer. It kicked off with a 30-minute chat with a recruiter about my background, if I knew certain tech like JavaScript, React, and Node.js, and why I wanted to join ItWorks. After that, I had to do an online coding test with 2-3 problems that were kinda medium difficulty, like messing with arrays or how an API would work. Then, I hopped on a virtual call with a senior engineer for a technical interview. This was a mix of system design stuff, some coding, and tricky questions, like building a REST API that could scale or fixing some code on the spot. The last part was more about fitting in with the team and behavioral stuff — how I work with others, deal with deadlines, and pick up new tech. The engineering manager also gave me the lowdown on current projects and their tech. I heard back with feedback about a week later. Overall, it was a good experience; the people were nice, and they kept me in the loop.
Confirmed questions1 question
- Tell me about your experience with specific technologies, mainly JavaScript, React, and Node.js.
ITWorx
Software Developer
Entry Average Neutral experience No offer 3 rounds
Interview process
Recruiter call Technical screen Onsite
Interview formats
Behavioral Technical Other
The process was smooth and well-organized, starting with an HR interview, followed by a technical interview (both conducted online). The final interview was onsite, lasted about 20 minutes, and focused on general questions. The interviewers were cheerful, but unfortunately, I received a rejection email about a month later, without any feedback.
Confirmed questions1 question
- Tell me about yourself.
ITWorx
Software Engineer
Lead Average Positive experience Accept offer 3 rounds
Interview process
Recruiter call Technical screen Onsite
Interview formats
Behavioral Technical System Design
The entire process lasted about a month. It began with an HR interview, followed by a technical interview, and concluded with an interview with the Program Manager. The HR interview covered typical HR topics, such as your career journey and reasons for leaving your previous job. The technical interview focused on design patterns, system design, and some OOB concepts. The final interview was more of a casual conversation about past experiences and how things operate within ITWorx.
Confirmed questions2 questions
- Can you explain the SOLID principles?
- What distinguishes an Interface from an abstract class?
ITWorx Software Engineer Interview Questions
Quoted word for word from ITWorx interview reports.
“What is the difference between web services and REST APIs?”
Read reports →“What is the difference between MVC and 3 tier architecture?”
Read reports →“Could you explain the difference between UNION and UNION ALL?”
Read reports →“What are the new features of swift 4 language?”
Read reports →“Could you explain the difference between JRE and JDK?”
Read report →“What is the difference between an abstract class and an interface, and when would you use each?”
Read report →“State the differences between Types of JOINS in SQL-Server?”
Read report →“Can you explain the difference between an abstract class and an interface?”
Read report →“What is the lifecycle of an MVC application?”
Read report →Formats, difficulty and experience
Across all 38 ITWorx interview reports.