4 rounds Coding+framework round Tech1 Tech2 Leadership and HR discussion Tips for Code(Date) problem ========================= You need to write the Manual Scenarios first all +ve, -ve and boundary cases, Special conditions write as many scenarios as possible. Come up with the Psuedo code(written algorithm kind of) first then convert it to actual program You can write program in the language of your choice. Follow proper coding practice when you do the coding, variable names, modularize the code, name the file properly. Add comments necessarily Test your code for all the different inputs(refer to the manual scenarios) Framework Round Tips ======================= You can consider any basic website like flipkart/amazon for this scenario No need to write the code for Payment section(as it involves OTP and all stuff just add some comment in that block saying //code for payment) Take a basic scenario for automation. 1. open flipkart/amazon(website of your choice) 2. search some product 3. add the product to cart 4. click on the payment(Dont write any code for this because u would need card details and stuff to test this) 5. Then do the log out action Follow OOP's concepts, especially inheritance create a Base class(which will have driver and other stuff) extend Testclasses with that BaseClass. Create different packages and name them accordingly like Utils, PageObjects,TestClasses While writing tests use logging/reporting(optional if you have time left with) Try to run the script locally(If they ask you during the evaluation to execute the test it should run) Write Login and Logout in util methods and use that in testclass Interview - Tech round ================== ==================== Prepare all Basic Manual Testing conccepts like Boundary value analysis, Equivalance partitioning, Decision Table etc Prepare about test plan and test strategy Prepare about cross browser testing, Exploratory testing(its concepts), Cross device testing, Accessibility testing(if you have worked on) Prepare HTTP status codes(5x,4x,2x) How does client server architecture work(when we hit a URL example google.com what happens in the background) How long your automation test suite takes to run(ex:2 hrs) they might ask you i need the time to be reduced to 10 min, how can you do it ? Clues: Make tests parallel, if all your tests are on UI then reduce UI tests(have basic smoke) and make all your tests at API level and have good amount of Unit tests. Prepare about Mock API testing(what is Mock API why do we need that how it is useful?) prepare about Test Pyramid(Martin flowers) In interview they might ask. It says "More Tests should be on Unit level, Moderate Tests on API level, very Less and minimal tests should be on UI" For Senior people more than 4 yrs exp They would give some realtime scneario and you have to come up with approaches on how to test, sprint wise API Testing might play key role. and use all your concepts of testing in this. Consider all the positive cases, negative cases and edge cases. Suggest improvements, Take inputs wherever you are not clear. More than the answers it is your approach to the problem which will be noticed by the interviewers. Additional/Bonus Points for these ============================= Read about ThoughtWorks Read about THoughtWorks University,Step, Vapasi programs Read about ThoughtWorks 3 pillars Read about ThoughtWorks open source contributions(Most famous Selenium) If you had done any open source sharing like blogging and other stuff you can mention during interviews. Express your interest to be part of ThoughtWorks(what made you feel to apply here)

Muito burocratica, muitas entrevistas e um pouco cansativo. Alem de requerer muito aprendizado para um cargo junior para um salario que nao era condizente com o que era requerido na entrevista. Tambem acredito que houve uma ma explicacao das fases da entrevista, o que o entrevistado deveria esperar de cada etapa