There were 5 technical rounds. 1st round was of 1 hr 30 mins. Another 4 rounds were of 45 mins each. 4 out of 5 rounds has 2-2 questions from coding in C and Python. And remaining were in depth technical questions from C, Embedded systems, Embedded Security, SoCs, Microcontrollers, Interrupts, ISRs, Communication protocols in details and Puzzles
Senior Software Qa Testingenieur Interview Questions
491 senior software qa testingenieur interview questions shared by candidates
Experience in test automation tools, frameworks, and Security Testing. Mainly focus on discussion around assignment and how I went about coming up with test cases.
1. C program to reverse the string. 2. Storage classes and code to explain them. 3. Questions on my previous project. 4. Difference between malloc and alloc. 5. Linux commands. 6. Few puzzles. 7. Features of vCenter, vSphere Client. 8. Hobbies, my work profile, reason to change the company, strength and weakness, how did I overcome the problems faced etc.
file and direcory permissions
What is your salary requirement?
The interviewer asked anything whatever came to his mind. SQL,Selenium,SOAP,REST,Agile,Unix,Linux,windows,manual testing concepts, anything. There were so many things which I never heard of in any interview,or are usually not asked in interview.They were not even related to the opening.
In the first screening call, I was asked what differentiates a good QA engineer from a bad one. The second interview was more technical, focusing on how I approached tasks and challenges in my previous role.
Shuffle the deck of card and return a random array
Assessment Details: Objective: To assess UI automation and coding proficiency Tool & Language: Playwright + JavaScript/TypeScript Task: Choose any website Create at least 10 unique test cases Use a standard test runner (e.g., Jest or Playwright’s built-in) Document how to set up and run the project No use of BDD tools like Cucumber or SpecFlow Evaluation Criteria: Code quality and SOLID principles Test design techniques Adherence to best practices Clarity of setup documentation Submission: GitHub public repo or Google Drive link (no GitLab) Timeline: 4 days I completed the task and submitted it on time, but unfortunately, I was rejected. I wasn’t given specific feedback on what went wrong, so I’m unsure where I fell short.
What are you doing currently in the job and why are you looking for a change
Viewing 121 - 130 interview questions