Skip to contentSkip to footer

Software Development Engineer In De Test Interview Questions

Salaries
Interviews

5,159 software development engineer in de test interview questions shared by candidates

1. Write a program where input is - "aabbbccaabbbcc" and output should be "a2b3c2a2b3c2" 2. Selenium version u are using and difference between Selenium 3 and Selenium 4 3. Maven and questions on maven 4. Why do we need different types of 2XX series if the developer can make 200 itself to work for different type. ( he was looking for something other than the standard protocols or conventions used) 5. Git fetch vrs Git pull 6. Bare minimum things to in browser before every release to confirm that the application is free from security vulnerability. 7. in postman, what is the difference between access token and refresh token.
avatar

Software Development Engineer In Test (SDET) II

Interviewed at Apple

4.1★
May 3, 2024

1. Write a program where input is - "aabbbccaabbbcc" and output should be "a2b3c2a2b3c2" 2. Selenium version u are using and difference between Selenium 3 and Selenium 4 3. Maven and questions on maven 4. Why do we need different types of 2XX series if the developer can make 200 itself to work for different type. ( he was looking for something other than the standard protocols or conventions used) 5. Git fetch vrs Git pull 6. Bare minimum things to in browser before every release to confirm that the application is free from security vulnerability. 7. in postman, what is the difference between access token and refresh token.

1st coding interview: Easy leetcode question. Palindrome sort of level 2nd coding interview: Mid leetcode question. Two-pointer sort of thing 3rd coding interview: Hard leetcode question. I am not even sure what the interviewer wanted here because he kept changing requirements to make it harder and harder, and he didn't bother to explain what he wanted me to do even after I asked
avatar

Software Development Engineer In Test (SDET)

Interviewed at Apple

4.1★
Jun 13, 2024

1st coding interview: Easy leetcode question. Palindrome sort of level 2nd coding interview: Mid leetcode question. Two-pointer sort of thing 3rd coding interview: Hard leetcode question. I am not even sure what the interviewer wanted here because he kept changing requirements to make it harder and harder, and he didn't bother to explain what he wanted me to do even after I asked

Classic instance of what opponents of coding interviews (which does not include me) object to. The engineneer was looking for me to spot the recursive trick for a string conversion problem, which was by no means obvious, and was by no means obviously correct even after he gave up on me and pointed it out. He ended the programming session after I raised questions about correctness, even though there was time left, without giving me a chance to implement the algorithm he’d suggested. He said that I had shown that I knew how to code it, but obviously meant the opposite: I got a rejection email soon after the interview. (I don’t disagree with the rejection: Apple seemed to be looking for a CS major to output code quickly; I’m a math major who has only written a test harness from scratch three times in my career.) Most troubling for a testing position, while I was writing doctests† to make sure I had understood his specification, he told me there wasn’t enough time to write tests, or to document my iterative algorithm: I should just start typing code. Somewhat less troublingly (at least for me as an applicant, if not as an Apple customer), the problem would probably have been a test of memory rather than coding ability for a CS major, since it seems to be a topic which would have been covered in class. ___ † doctest is a very cool Python module, which examines the examples you put into a function’s documentation string, and complains if it does not produce the output you specified.
avatar

Software Development Engineer In Test

Interviewed at Apple

4.1★
Apr 11, 2021

Classic instance of what opponents of coding interviews (which does not include me) object to. The engineneer was looking for me to spot the recursive trick for a string conversion problem, which was by no means obvious, and was by no means obviously correct even after he gave up on me and pointed it out. He ended the programming session after I raised questions about correctness, even though there was time left, without giving me a chance to implement the algorithm he’d suggested. He said that I had shown that I knew how to code it, but obviously meant the opposite: I got a rejection email soon after the interview. (I don’t disagree with the rejection: Apple seemed to be looking for a CS major to output code quickly; I’m a math major who has only written a test harness from scratch three times in my career.) Most troubling for a testing position, while I was writing doctests† to make sure I had understood his specification, he told me there wasn’t enough time to write tests, or to document my iterative algorithm: I should just start typing code. Somewhat less troublingly (at least for me as an applicant, if not as an Apple customer), the problem would probably have been a test of memory rather than coding ability for a CS major, since it seems to be a topic which would have been covered in class. ___ † doctest is a very cool Python module, which examines the examples you put into a function’s documentation string, and complains if it does not produce the output you specified.

Viewing 1621 - 1630 interview questions

Glassdoor has 5,159 interview questions and reports from Software development engineer in de test interviews. Prepare for your interview. Get hired. Love your job.