Decisions Interview Questions
& Process
Real candidates share what happened, how many rounds they had,
and how the experience turned out.
Based on 20 interview experiences · FREE TO READ
Which role are you interviewing for?
6 roles · 20 reportsCandidate interview experiences
First-hand accounts from people who interviewed at Decisions.
Decisions
Junior QA Engineer
Entry Easy Negative experience No offer 1 round
Interview process
Recruiter call Technical screen
Interview formats
Technical
The HR team was very professional and timely with communication, which I appreciated. But the actual interview was a letdown. It was supposed to be 30 minutes but only lasted 10. They only asked six questions, and I felt good about four of them. I was ready for coding or deep technical questions, but there were none. It feels unfair to judge someone with 1.8 years of experience in such a short time. A 30-minute interview should have about 20-25 minutes of actual discussion. It felt unprofessional and didn't give me a chance to show what I can do.
Confirmed questions1 question
- Can you explain positive and negative test cases?
Decisions
Junior Software Developer
Entry Easy Negative experience Decline offer 3 rounds
Interview process
Take home Technical screen Recruiter call
Interview formats
Technical Coding Behavioral
applied on LinkedIn for a "Junior Software Developer" role, after two weeks got an email about an online exam which included simple C#, OOPs and SQL questions. Then, after three months, the HR took a telephonic round and offered a salary of 3 LPA, which was quite surprising for a Mumbai location.
Confirmed questions3 questions
- Could you tell me about yourself?
- Can you walk me through your educational background?
- What are your key skills?
Decisions
QA Manual Tester
Mid Easy Negative experience No offer 3 rounds
Interview process
Technical screen Recruiter call Technical screen
Interview formats
Technical Behavioral
The interview process had 3 rounds. First was a technical test with some testing questions. The second round was a normal screening call, asking about my education and other general questions. The third round was a technical interview on Zoom. It had easy questions about manual testing, but the interviewer, who seemed very senior and arrogant, said everything I answered was wrong. When I asked for feedback, he was extremely rude and dismissive. HR was calm and supportive, but I'd advise against interviewing with that specific testing interviewer as he seemed determined to reject and demotivate candidates. The role was for a manual tester, but he kept pushing why I wasn't interviewing for automation.
Confirmed questions6 questions
- Can you explain STLC?
- What is the difference between sanity and smoke testing?
- Describe regression testing and retesting.
Decisions
Sales Engineer
Mid Difficult Positive experience Accept offer 3 rounds
Interview process
Recruiter call Technical screen Onsite Background check Offer
Interview formats
Behavioral Technical
I was initially interviewing for a Solutions Developer position, but it became unavailable after my interview. A couple of weeks later, I got a call asking if I'd be interested in a sales engineer role. I wasn't sure, but I accepted the challenge and agreed to interview. I did my research and came prepared. Everyone I met was really nice and genuine. They mentioned they were interviewing other candidates and I should hear back soon. About a week later, I got invited for more interviews, and finished with a meeting with the VP. This whole process taught me a lot, and I'm thankful for the opportunity.
Confirmed questions2 questions
- Tell us something about yourself.
- What makes you a better candidate than others?
Decisions Interview Questions
Quoted word for word from Decisions interview reports.
“What is the difference between sanity and smoke testing?”
Read reports →“What are negative test cases for pen testing?”
Read reports →“Describe regression testing and retesting.”
Read reports →“Can you explain the distinction between sanity testing and smoke testing?”
Read reports →“What are the basics of .net?”
Read report →“Can you define low severity and low priority?”
Read report →“Could you elaborate on the concept of logical sums?”
Read report →“Could you describe the different types of firewalls?”
Read report →“What's your understanding of low-code platforms?”
Read report →Formats, difficulty and experience
Across all 20 Decisions interview reports.