Passa al contenutoPassa al piè di pagina
  • Lavori
  • Aziende
  • Stipendi
  • Per le aziende

      Migliora la tua carriera

      Scopri le tue potenzialità di guadagno, trova lavori da sogno e condividi approfondimenti su lavoro e vita privata in forma anonima.

      employer cover photo
      employer logo
      employer logo

      PlayStation

      Parte di Sony

      Azienda coinvolta

      Chi siamo
      Recensioni
      Stipendi e benefit
      Lavori
      Colloqui
      Colloqui
      Ricerche correlate: Recensioni su PlayStation | Offerte di lavoro di PlayStation | Stipendi di PlayStation | Benefit di PlayStation
      Colloqui di PlayStationColloqui per Senior SDET presso PlayStationColloquio di PlayStation


      Glassdoor

      • Chi siamo
      • Contattaci

      Aziende

      • Account Business gratuito
      • Spazio per le aziende
      • Blog per le aziende

      Informazioni

      • Aiuto
      • Linee guida
      • Condizioni d'uso
      • Privacy e scelte pubblicitarie
      • Non vendere né condividere le mie informazioni
      • Strumento per l'accettazione dei cookie

      Lavora con noi

      • Inserzionisti
      • Carriere
      Scarica l'app

      • Cerca:
      • Aziende
      • Lavori
      • Località

      Copyright © 2008-2026. Glassdoor LLC. "Glassdoor," "Worklife Pro," "Bowls" e il relativo logo sono marchi registrati di Glassdoor LLC.

      Aziende seguite

      Non lasciarti sfuggire opportunità e informazioni privilegiate seguendo le aziende dove vorresti lavorare.

      Ricerche di lavoro

      Ricevi suggerimenti e aggiornamenti personalizzati avviando le tue ricerche.

      Colloquio per Senior SDET

      19 ott 2023
      Candidato anonimo a colloquio
      Nessuna offerta
      Esperienza negativa
      Colloquio facile

      Candidatura

      Ho sostenuto un colloquio presso PlayStation

      Colloquio

      Phone screen then technical interview. Interview was over codepen or similar code sharing site. Intro > challenge > more info and chatting. Overall was pleasant process but I've interviewed many people too and I design a more real world interview that let's the candidate show their ability to test the code they write.

      Domande di colloquio [1]

      Domanda 1

      My problem was, the question was just a coding challenge. If you happened to practice that one, what would that have shown about your ability as an engineer? The second question was based on the first one. I've worked as a senior sdet for almost 10 years and do some pretty technical day-to-day work including fixing bugs in production etc I am no junior, but because I was tripped up by a tricky coding problem I got no offer.
      1 risposta
      1

      Altre recensioni di colloqui per Senior SDET presso PlayStation

      Colloquio per Senior SDET

      20 nov 2025
      Candidato anonimo a colloquio
      Los Angeles, CA
      Nessuna offerta
      Esperienza neutra
      Colloquio nella media

      Candidatura

      Ho presentato la mia candidatura online. Ho sostenuto un colloquio presso PlayStation (Los Angeles, CA) nel mese di nov 2025

      Colloquio

      Applied in their website, got an email and call from recruiter. First round technical interview was scheduled. The interview was good. But I was not moved to next round. Probably they wanted local candidate. I am in NJ but the role was in Los Angeles, CA.

      Domande di colloquio [1]

      Domanda 1

      1. Tell me about your day to day activities. 2. Write code to calculate the factorial of any input number E.g n!=n x (n-1) x (n-2) x.... x 1 5!=5x4x3x2x1 = 120 Solved it using integer. Then asked me do the factorial of 100. The result was 0. Ques: Do you know why it is 0? Ans: I solved it using int. Factorial of 100 is more than max value of int. Need to use different data type like float, double. 3. /* You are given two integer lists nums1 and nums2. Merge nums1 and nums2 into a single list sorted in descending order. list1=[3,9,5] list2 = [6,1,4] expected o/p = [9,6,5,4,3,1] Solved it using list.addAll() and then Collections.reverseOrder(). Follow up: Is there a better way to add the values in a list? Yes, taking an array and then put everything from array to the list. Follow up: If you have duplicates and I want to remove the duplicates, and then sort in descending order, how can I do that? Ans: I will use a TreeSet. Add all elements of the lists to set. And then reverse it using Collections.reverse() method. 4. Write a SQL query for a report that provides the following information for each person in the Person table, regardless if there is an address for each of those people: FirstName, LastName, City, State Person Table: +-------------+----------------+ | Column Name | Type | +-------------+----------------+ | PersonId | int | | FirstName | varchar | | LastName | varchar | +-------------+-----------------+ PersonId is the primary key column for this table. Address Table: +-------------+----------------+ | Column Name | Type | +-------------+----------------+ | AddressId | int | | PersonId | int | | City | varchar | | State | varchar | +-------------+---------+ AddressId is the primary key column for this table. 5. What types of frameworks did you use for UI? Explain the design you followed. Explained framework using POM. 6. Explain your design pattern of API framework. 7. What’s the difference between POST and PUT? 8. What types of authentications have you used? 9. What’s the difference between 401 and 403? 10. When you get a 400 in a POST call, what do you check first? 11. What are the different types of exceptions you handled in selenium? Explained noSuchElementFound exception and different types of waits including Thread.sleep(), implicitWait, WebDriverWait() with expected condition. 12. How do you handle state element exception? I know we are already running over time, but I have a few questions if you have some time. 1. What are the challenges you face day to day in this job? Interviewer: we have a lot of test cases. We are using Java, Selenium for automation. I won’t say it is a challenge. But now we want to do a lot of API testing and unit testing i.e. shift left in addition to UI tests. Me: That’s really a great approach. This is the testing strategy I follow. I use the strategic test pyramid approach. About 60-70% tests should be covered in unit testing. Then 20-25% in API testing as it is really fast to run. Core business logics should be tested via API. I have 1400+ test cases which take just 6min to run in pipeline. Only about 5% test cases should be automated in UI specially which are not testable via API, and end-to-end test cases. Cause a sing UI test case can take as much as 10min to run which is very costly to maintain. 2. What are the next steps in the hiring process?
      Rispondi alla domanda
      2