During one point of the interview they come over and create a "hypothetical" situation in which a client is unhappy about something on their website. You are to look into the issue and report what the issues are. After I was able to find a number of "issues", they provided 0 feedback.
How do you decide what goes into production and what does not with minimal time to test.
On the first in-person interview, I was asked about my past experience. On the second interview, they gave me a test. Full of data structure questions. Big-O notation Memory management Code interpretation Data structure algorithms
They asked about my previous company work experience & Technical questions
About last year bachelor's project?
difference between tcp and udp
Basic wireless questions Protocols worked Deployment based questions Tools used for testing
Find the edge cases of an object around you
me preguntaron los diferentes tipos de testing que hay si sabia mencionar y explicar los diferentes metodos de pruebas, pruebas de humo, pruebas de integracion, pruebas explotarias y pruebas unitarias. posterior a eso si sabia ejecutar querys en PL/SQL me hicieron decir algunas consultas basicas y posterior a eso contara mi exp de trabajos anteriores. con esto ademas me preguntaron por que queria el puesto y cual serian las metas si entraba al mismo
reasoning questions, aptitude questions will be there
Viewing 331 - 340 interview questions