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

      Polly

      ¿Esta es tu empresa?

      Información
      Opiniones
      Sueldos y beneficios
      Empleos
      Entrevistas
      Entrevistas
      Búsquedas relacionadas: Opiniones sobre Polly | Ofertas de empleos en Polly | Sueldos en Polly | Beneficios en Polly
      Entrevistas de PollyEntrevistas para el puesto de Software Engineer en PollyEntrevista de Polly


      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.

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

      avatar
      SAP
      3.9★Remuneración y beneficios
      avatar
      Cisco
      4.0★Remuneración y beneficios
      avatar
      ADP
      3.5★Remuneración y beneficios
      avatar
      Autodesk
      4.0★Remuneración y beneficios

      Entrevista de Software Engineer

      6 feb 2020
      Candidato de entrevista anónimo
      San Francisco, CA
      Sin oferta
      Experiencia neutra
      Entrevista normal

      Solicitud

      Solicité el puesto a través de un captador. El proceso duró 3 semanas. Acudí a una entrevista en Polly (San Francisco, CA)

      Entrevista

      Started with a brief phone call from the recruiter, asking basic questions about my qualifications. After that, I was sent a coding challenge via email. I was asked to not disclose what the challenge is, but it's simple and straight forward, and the email will tell you what the expected answer is so you can check your work. Then had a phone interview with two engineers. They asked a series of canned questions about my experience. I had an on-site interview about a week later. In general, it was pretty average, though very light on the technical side of things. One of the engineers kept asking me the most bizarre questions I've ever been asked in an interview like "what is your favorite part of the python programming language?" and when I answered he wasn't satisfied with what I said and was trying to get me to change my answer. It's an opinion based question.... my answer, by definition, cannot be wrong. I think he wanted me to list off notable features of the language as if that was some sort of demonstration of technical ability (list comprehensions, decorators, lambdas, etc.). So weird. The answer I gave was that I appreciate the elegance. The only technical segment was a brief architecture question from the VP of Engineering, which I tripped up on a little bit, but he was super cool about it and helped guide me through to the answer. In general, everyone was incredibly nice and enjoyable to talk to, and I got the impression that I could enjoy being in their presence all day. However, the CEO used some aggressive interview tactics on me, which I did not appreciate, and which left a sour taste in my mouth. I think he was trying to put on a lot of pressure to see if I choked or changed my answers. I got the impression that I would need to forgo having a work/life balance to be successful at PollyEx, and would need to work 50 hour weeks. Maybe that's standard for Bay Area engineering, but it's not quite what I was looking for. I pulled out of the process before they could make a decision as I had a more compelling offer come through.

      Preguntas de entrevista [2]

      Pregunta 1

      What is your favorite feature of Python?
      Responder pregunta

      Pregunta 2

      Why do you want to work here?
      Responder pregunta
      5

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

      Entrevista de Software Engineer

      15 dic 2020
      Candidato de entrevista anónimo
      Sin oferta
      Experiencia negativa
      Entrevista fácil

      Solicitud

      Envié una solicitud electrónica. Acudí a una entrevista en Polly en sept 2020

      Entrevista

      I applied and after few days, I got an email from HR requesting phone screening. I replied the email with available times and there was no reply back. After a week, the HR emails me again to reply with available times for screening. I replied again but no reply. Another week passes and again emails me asking for my available time for phone screen. I replied, once again, and this time the HR person was able to schedule me for a phone screening. It was hard to just get through the initial phone screening. After the phone screen, I was give a take home coding assignment which I promptly sent back. They took another week to review and to schedule a INITIAL interview with the hiring managers. They were very slow in replying back but when they requests for available time, they ask for something within 2 days. The day of the interview, I was joined by 2 people on Google Meet. It was very awkward experience. Both of them turned off their videos, muted and would unmute only to read questions, no introduction other than their names, no background information given and one of them started reading out questions which weren't technical at all. At this point, it didn't feel like interview any more but responding to a void. The amount of take home task they request (yeah, the mortgage calculator, it's not just the programming, it's all the side things they request you to do takes more time than programming a calculator) from the candidates was surprising and when you actually get to speak with an actual people from dev, all they do is read out questions to you. When one person was done, the next person would take over and again read out questions. At this point, I was frustrated in answering their questions. Few days later, I got an email saying that they have decided not to move ahead. This is the quickest reply I got from them in any of the communications.

      Preguntas de entrevista [1]

      Pregunta 1

      What was your worst mistake?
      Responder pregunta
      2

      Entrevista de Software Engineer

      14 may 2020
      Candidato de entrevista anónimo
      San Francisco, CA
      Sin oferta
      Experiencia negativa
      Entrevista normal

      Solicitud

      Solicité el puesto a través de un captador. El proceso duró 3 días. Acudí a una entrevista en Polly (San Francisco, CA) en may 2020

      Entrevista

      The guy on hackerjobs slack channel posted a message on the position. When I tried to get more details he disappeared for a day, then gave some evasive answer, which was a first red flag for me. Anyways, I've applied and got a phone call with recruiter, who sent me a coding challenge, that they wanted to keep private, as if they have no creativity to test tech skills. They asked me to create a mortgage calculator app within two hours including docs, tests, dependencies etc. Seemed as some wet blanket nerd trying to access how you would fit his "standards" to work in a sweat shop environment. Not a big surprise that they are so desperate to search for talent on slack channels :)

      Preguntas de entrevista [1]

      Pregunta 1

      You are in charge of creating a loan payment calculator. A lot of people want to figure out what their payments are going to look like and how much of it is going to go towards principle vs interest. To do that calculation you will need to take in the interest rate, loan amount, downpayment and the term length. Your program is going to get data from standard input in the following format: ``` amount: 100000 interest: 5.5% downpayment: 20000 term: 30 ``` NOTE: a) the last line of input is a blank line. b) The term is given in years. c) The interest can be given a percentage or a digit. Your program needs to process the input including handling some human errors (upper/lower case, spacing etc) and output a JSON of the monthly payment and total interest paid. ``` { "monthly payment": 454.23, "total interest": 83523.23, "total payment": 163523.23 } ``` ## Solution Framework 1. This challenge should take no more than 2-3 hours. If it's taking longer chances are that you are solving something bigger than what we had in mind. 2. Please send us back an archive (zip, tar) via some sharing method (DropBox, Google Drive etc) which contains your solution with instructions of how to get it running on either Mac or Windows. Please do not use any tools that require purchase or subscription (Visual Studio Enterprise, for instance). We will most likely test this on a bare bones Mac, Linux or Windows machine and just execute it on command line. 3. It is preferred that if the dependencies are needed that you include requirements in a file rather than sending us the libraries, so please utilize npm, nuget, pip or whatever is appropriate. 4. While this is a small task we do want to see a glimpse of your production code. This is not a 10 minute white boarding task - it's designed to be a take home test for a reason. Imagine you are delivering a new module into a production system, you'd probably want to include docs, tests, comments etc. 5. As a personal favor we ask you not to post this challenge as a public repository on GitHub or another code sharing site. We don't want to spoil the fun for the next engineering candidate.
      Responder pregunta
      5