Test Engineer applicants have rated the interview process at Indium Software with 3 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 100% positive. This is according to Glassdoor user ratings.
Candidates applying for Test Engineer roles take an average of 2 days to get hired, when considering 1 user submitted interviews for this role. To compare, the hiring process at Indium Software overall takes an average of 10 days.
Common stages of the interview process at Indium Software as a Test Engineer according to 1 Glassdoor interviews include:
Personality test: 33%
One on one interview: 33%
Skills test: 33%
Here are the most commonly searched roles for interview reports -
I applied through other source. The process took 1 day. I interviewed at Indium Software (Chennai) in Feb 2018
Interview
I've attended Testing interview at Indium software, Chennai o 3rd Feb 2018. They conducted 4 rounds. 1st round is technical aptitude. Its difficulty level is moderate. 2nd round is technical HR. 3rd round is also Technical Hr with Manager. 4th round will be with Companies most senior person. After attending all rounds they told me that I will get call if I am selected. Even after 3 days they didn't call me. So I called and inquired. They told that they will inform after getting result from technical team. Even after 1 week I didn't receive any call from them. While attending interview they were speaking about referrals. They ill give importance to reference only.
Interview questions [1]
Question 1
Explain final, finally, finalize
static and non static
oops concepts
I applied through a staffing agency. I interviewed at Indium Software
Interview
L1 was good basic questions like sdlc stlc verification validation smoke sanity production bug RCA integration testing bug life cycle bug report self intro scenarios bug leakage good test case coverage sdlc modules
2 rounds of interview What is Risk-Based Testing?
Risk-based testing is a software testing technique that is based on the probability of the risks and involves assessing the risk based on factors like:
Software complexity.
Criticality of the businesses.
Frequency of use.
Possible areas of defects.
It uses risks to prioritize the appropriate tests during test execution. It starts early in the software project, identifying the risks to system quality and using the knowledge of risks identified to guide testing planning, specification, preparation, and execution.
18. What is Fuzz Testing?
Fuzz testing or fuzzing is a software testing approach that injects invalid or malformed inputs into the system to reveal software vulnerabilities in an attempt to make it crash.
It is carried out using automated software that generates new test cases and feeds the program inputs.
It is used to detect if the program crashes or reveals other vulnerabilities.
19. What is Test Harness?
It was easy to crack it if you have a thorough understanding of testing concepts. Joining the interview on time gives good impression always. By life cycle, alpha testing, game testing
Interview questions [1]
Question 1
How do you handle bugs when it leaked to end users