Ir al contenidoIr al pie de página
  • Empleos
  • Empresas
  • Sueldos
  • Para empresas

      Impulsa tu carrera profesional

      Averigua cuánto podrías ganar, encuentra el empleo perfecto y comparte información sobre tu vida laboral y personal de forma anónima.

      employer cover photo
      employer logo
      employer logo

      Upgrade

      ¿Esta es tu empresa?

      Información
      Opiniones
      Sueldos y beneficios
      Empleos
      Entrevistas
      Entrevistas
      Búsquedas relacionadas: Opiniones sobre Upgrade | Ofertas de empleos en Upgrade | Sueldos en Upgrade | Beneficios en Upgrade
      Entrevistas de UpgradeEntrevistas para el puesto de Senior Software Engineer en UpgradeEntrevista de Upgrade


      Glassdoor

      • Acerca de
      • Premios
      • Blog
      • Contacto

      Empresas

      • Cuenta gratuita de empresa
      • Centro de empresas

      Información

      • Ayuda
      • Normas
      • Condiciones de uso
      • Privacidad y opciones de anuncios
      • No vender ni compartir mi información
      • Herramienta de consentimiento de cookies

      Trabaja con nosotros

      • Anunciantes
      • Empleo
      Descargar aplicación

      • Buscar por:
      • Empresas
      • Empleos
      • Ubicaciones

      Copyright © 2008-2026. Glassdoor LLC. «Glassdoor», «Worklife Pro», «Bowls» y sus logotipos son marcas comerciales registradas de Glassdoor LLC.

      Empresas seguidas

      Sigue a tus empresas favoritas para estar al tanto de las últimas oportunidades y disponer de información de primera mano.

      Búsquedas de empleo

      Recibe recomendaciones y actualizaciones personalizadas al iniciar tu búsqueda.

      Entrevista de Senior Software Engineer

      9 jun 2026
      Candidato de entrevista anónimo
      San Francisco, CA
      Oferta rechazada
      Experiencia negativa
      Entrevista fácil

      Solicitud

      Acudí a una entrevista en Upgrade (San Francisco, CA)

      Entrevista

      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.

      Preguntas de entrevista [1]

      Pregunta 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?
      Responder pregunta

      Otras opiniones sobre las entrevistas para el puesto de Senior Software Engineer en Upgrade

      Entrevista de Senior Software Engineer

      19 oct 2024
      Candidato de entrevista anónimo
      Toronto, ON
      Sin oferta
      Experiencia negativa
      Entrevista normal

      Solicitud

      El proceso duró 3 semanas. Acudí a una entrevista en Upgrade (Toronto, ON)

      Entrevista

      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.

      Preguntas de entrevista [1]

      Pregunta 1

      Design something involved with transactions and prevent double booking.
      Responder pregunta

      Entrevista de Senior Software Engineer

      16 sept 2022
      Candidato de entrevista anónimo
      Sin oferta
      Experiencia positiva
      Entrevista normal

      Solicitud

      Acudí a una entrevista en Upgrade

      Entrevista

      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.

      Preguntas de entrevista [1]

      Pregunta 1

      only 1st round of code challenge.
      1 respuesta

      Las mejores empresas en cuanto a «Remuneración y beneficios» cerca de ti

      avatar
      HSBC
      3.7★Remuneración y beneficios
      avatar
      Bank of America
      3.8★Remuneración y beneficios
      avatar
      Barclays
      3.8★Remuneración y beneficios
      avatar
      Capital One
      3.9★Remuneración y beneficios