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

      Upgrade

      Questa è la tua azienda?

      Circa
      Recensioni
      Stipendi e benefit
      Lavori
      Colloqui
      Colloqui
      Ricerche correlate: Recensioni su Upgrade | Offerte di lavoro di Upgrade | Stipendi di Upgrade | Benefit di Upgrade
      Colloqui di UpgradeColloqui per Senior Software Engineer presso UpgradeColloquio di Upgrade


      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 Software Engineer

      9 giu 2026
      Candidato anonimo a colloquio
      San Francisco, CA
      Offerta rifiutata
      Esperienza negativa
      Colloquio facile

      Candidatura

      Ho sostenuto un colloquio presso Upgrade (San Francisco, CA)

      Colloquio

      The interview process for the Senior QA Engineer position consisted of 4 rounds and lasted almost 3 weeks.Round 1: Recruiter Screening (30 minutes) The recruiter asked very basic questions about my notice period and current salary. She seemed unprepared and kept mixing up the role with a development position. When I tried to explain my experience in automation, she interrupted me saying “Yeah, yeah, testing stuff” and moved on.Round 2: Technical Screening (45 minutes) The interviewer joined 15 minutes late. He asked me to explain the difference between Smoke and Sanity testing but cut me off after 20 seconds. Most questions were theoretical and outdated (e.g., “Write test cases for a login page” on a shared notepad). When I mentioned API testing with Postman and REST Assured, he asked, “Is that even necessary?” He appeared distracted and was typing on his other laptop throughout the call.Round 3: Automation Round (1 hour) They asked me to write a Selenium script for a dynamic web table live on the shared screen. The interviewer kept arguing that my approach was wrong even though it was correct. He insisted on using Thread.sleep() everywhere and rejected Page Object Model saying “It’s overcomplicating simple things.” When the code had a small syntax error due to nervousness, he made a long face and said, “Even freshers don’t make this mistake.”Round 4: Managerial + HR Round The manager spent most of the time complaining about how the current QA team is “not delivering” and how they expect the new joiner to “fix everything in 2 months.” He showed zero interest in my achievements and only asked about my availability to join early. The HR person asked strange questions like “How do you handle pressure when developers blame QA for their bugs?” and “Will you work on weekends if there is a release?”Overall Experience Multiple rescheduling of interviews with very short notice. Interviewers were rude and dismissive. Questions were not aligned with the job description (JD mentioned Cypress and Playwright, but they only asked about Selenium). No proper feedback was given at the end. The entire process felt chaotic and unprofessional. I felt demotivated after the interviews and decided to reject the offer even though it was selected.

      Domande di colloquio [1]

      Domanda 1

      Round 1: Technical Screening (Basic but Painful)Tell me the difference between Smoke and Sanity testing. What is a Test Case? Write 10 test cases for a Login page right now. What is the difference between QA and QC? Explain the Software Testing Life Cycle (STLC). What is a Bug? What is a Defect? Are they different? How many test cases can you write in a day? Round 2: Automation Round (Most Painful)Write a complete Selenium script to login to Gmail (live on shared screen). What is Thread.sleep()? Why do we use it? Explain Page Object Model (POM). Why is it needed? (Then argue why it’s unnecessary) How do you handle dynamic dropdowns in Selenium? Write an XPath for this element (shows a very complex nested element). What is the difference between findElement and findElements? How do you run the same test on Chrome, Firefox, and Edge? (No mention of Selenium Grid) What is your framework? Explain it in 2 minutes. Why is your automation suite slow? How will you make it faster? Round 3: Manual + Scenario-Based (Tricky & Outdated)Write test cases for a Pen. How will you test a Coffee Machine? What if the Developer says “It works on my machine”? How do you test an application when there are no requirements? Explain Regression Testing vs Retesting with examples. What is Boundary Value Analysis and Equivalence Partitioning? Give examples. How will you test WhatsApp’s “Last Seen” feature? Round 4: Managerial / Behavioral (Negative & Demotivating)Why do you want to join our company? (Even after they know you’re interviewing elsewhere) Tell me about your biggest failure in your previous project. Why are you leaving your current company? How will you manage if the entire team blames QA for production issues? Are you okay working on weekends and late nights during releases? How many years of automation experience do you have in Selenium? (Even if your resume clearly says Cypress/Playwright) What will you do in the first 30 days if you join? Don’t you think QA is less important than Development?
      Rispondi alla domanda

      Altre recensioni di colloqui per Senior Software Engineer presso Upgrade

      Colloquio per Senior Software Engineer

      19 ott 2024
      Candidato anonimo a colloquio
      Toronto, ON
      Nessuna offerta
      Esperienza negativa
      Colloquio nella media

      Candidatura

      La procedura ha richiesto 3 settimane. Ho sostenuto un colloquio presso Upgrade (Toronto, ON)

      Colloquio

      I was reached out by a recruiter and then setup for the interview. The interview consists of 3 rounds, and all of them are a bit casual chat on a system design. I thought I was doing okay, and I provided more than one possible solution to the questions. I don’t think I clearly say I didn’t know something, as I answered most of the asks. But still I got rejected due to 2 reasons per the HR. First off, one of the interviewers is saying, I didn’t demonstrate enough attitude, and lack of desire to join the company, like I should demonstrate them I enjoy their technical challenges or something. This is beyond me. First, I did ask them what they are building and what the challenges are and the discussion lasted 3, 4 minutes. This interviewer straight up lying. Second, I told them the reason why I am switching my job, is due to a very practical reason, and my team are all good people. It’s just the RTO arrangement doesn’t work quite well for me. I also mentioned that I used to work at traditional banks, and the pace is very slow. Newer FinTech companies are fast in adapting changes which is something I do enjoy. If I am not determined to make a change, why do I bother taking a job interview? And again, how can you quantify attitude? I can pretend to be super excited and slacking off right after I am hired. Still, if he intended to misinterpret my willingness to join, sure. This is utterly unprofessional I must say. Second, they mention, I am not demonstrating enough knowledge on transactions. Well, I am not sure how much is enough. I said, code wise, a @Transactional annotation would do. And in a distributed system, you can consider use MQ to ensure message is delivered once, or consider using Redis cache lock to be more performant. I even mentioned that @Transactional would use cglib to regenerate the code, and wrap it with transaction, commit, rollback method. The reason sounds to me like, you said you know Java, but you don’t understand what a Serializable interface does, so you are not great. Not to mention some of the techniques I told them, they don’t seem to know about, or it’s like their first time knowing it. Again, I am deeply disappointed, and yet HR has to call me to tell you are doing great, most of the feedback is positive, but you are not chosen. I have notes on the entire interview process, just to be clear. So, I can back track what people say.

      Domande di colloquio [1]

      Domanda 1

      Design something involved with transactions and prevent double booking.
      Rispondi alla domanda

      Colloquio per Senior Software Engineer

      16 set 2022
      Candidato anonimo a colloquio
      Nessuna offerta
      Esperienza positiva
      Colloquio nella media

      Candidatura

      Ho sostenuto un colloquio presso Upgrade

      Colloquio

      1. 30 mins phone all with recruiter; 2. code challenge as the 1st step ( you can take a few days of it) 3. Internal code review on your project. 4. decision made for next round of interview.

      Domande di colloquio [1]

      Domanda 1

      only 1st round of code challenge.
      1 risposta

      Le migliori aziende per "stipendio e benefit" vicino a te

      avatar
      Standard Chartered Bank
      3.5★Stipendio e benefit
      avatar
      Barclays
      3.8★Stipendio e benefit
      avatar
      Absa
      3.8★Stipendio e benefit
      avatar
      Standard Bank Group
      4.0★Stipendio e benefit