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

      Philo

      Azienda coinvolta

      Circa
      Recensioni
      Stipendi e benefit
      Lavori
      Colloqui
      Colloqui
      Ricerche correlate: Recensioni su Philo | Offerte di lavoro di Philo | Stipendi di Philo | Benefit di Philo
      Colloqui di PhiloColloqui per Software Engineer, Backend presso PhiloColloquio di Philo


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

      10 set 2019
      Dipendente anonimo
      San Francisco, CA
      Offerta accettata
      Esperienza positiva
      Colloquio nella media

      Candidatura

      Ho presentato la mia candidatura tramite segnalazione di un dipendente. La procedura ha richiesto 4 settimane. Ho sostenuto un colloquio presso Philo (San Francisco, CA) nel mese di giu 2019

      Colloquio

      After a couple of phone conversations with the recruiter and one of the leads, they sent me a homework assignment, with flexible timeline, which is great compared to live/whiteboard coding, since you can demonstrate your coding and problem solving skills in a more realistic manner. After submitting the code and passing the test cases, I was invited for an on-site interview. I was given a site tour and a product tour, and then was interviewed with 4 of the engineers and the recruiter. These interviews were more focused on dealing with different scenarios I had faced before, and potentially at Philo. One interviewer went through my homework code with me. The interview included a lunch break with the staff, which was a great opportunity to talk and learn about company's vibe and culture. Everybody was very nice and welcoming. A few days after the on-site interview, I had a video call with the company's CTO, which included more general questions about priorities, long-term goals, and expectations. It also included a short live-coding exercise. The CTO was very patient, honest, and open-minded. I got an offer a few days later.

      Domande di colloquio [1]

      Domanda 1

      What's the biggest issue you have confronted in a previous project, and how did you overcome it?
      Rispondi alla domanda
      2

      Altre recensioni di colloqui per Software Engineer, Backend presso Philo

      Colloquio per Backend Software Engineer

      19 feb 2021
      Dipendente anonimo
      San Francisco, CA
      Offerta accettata
      Esperienza positiva
      Colloquio nella media

      Candidatura

      Ho presentato la mia candidatura online. Ho sostenuto un colloquio presso Philo (San Francisco, CA) nel mese di ago 2020

      Colloquio

      After I first applied for this job I was contacted by the recruiter who then scheduled a call between him, an engineer and myself. The call went great and we got a chance to talk over a bit about myself, Philo as a company and the role. Then, the engineer and I dived into a technical conversation about a past project of mine. Following that call I got a home assignment to complete in about 2 weeks (though I think it took me a bit more but there was no pressure from their side) and I was invited to a slack channel for any questions I might have. I really liked the way the assignment was built and it allowed me to write code and show my skills in a real scenario and timeframe. The “onsite” (virtual due to COVID) part took place after I handed in my assignment. It consisted of 5 interviews. 2 technical interviews (1 design and 1 was more of a pair programming style), 1 interview in which we discussed the specifics of the assignments and thought of any needed improvements to it, 1 demo of Philo’s product and 1 behavioral interview. Through all of these interviews I really got a good feel of the culture of the company and the people within it. It felt really different (in a good way) than any other interview I did during that time. The last part of the process was an interview with the CTO about was mainly about making sure that what I’m looking for and my goals align well with what Philo are looking for and has to offer (It also included a very small coding question). Overall process was a little long for me, around 2 months (part of it was due to the amount of time that took me to hand in the home assignment) but enjoyable, respectful and felt like you’re being tested for actual skills rather than solving “Leetcode” questions.

      Domande di colloquio [1]

      Domanda 1

      Q: Tell me about a project you worked on (in detail)
      Rispondi alla domanda
      3

      Colloquio per Software Engineer, Backend

      6 set 2019
      Dipendente anonimo
      San Francisco, CA
      Offerta accettata
      Esperienza positiva
      Colloquio nella media

      Candidatura

      La procedura ha richiesto 8 settimane. Ho sostenuto un colloquio presso Philo (San Francisco, CA) nel mese di mag 2019

      Colloquio

      The interview process took 8 weeks from the first call to getting the offer. The first call was with the recruiter followed by an engineer, who were both very friendly. I was given a take home assignment that was optional, and scheduled an on site as well. A Slack invitation was sent to me so that if I was stuck on the take home assessment, I would be able to get help/clarification from an engineer. Ultimately, I did not complete the assessment, but that wasn't a problem to them; instead of a code review session as a part of the on-site interview, I did live coding. During the on-site, I was given a demo of the product and had 1-1 with multiple engineers, who asked me technical questions. Instead of the questions being leetcode-styled, where they would ask you a question and just sit there silently, watching you explain and code on a white board, the questions that they asked were more open ended and pertained to real use cases, such as system design/architecture, and felt more like pair programming. My interviewers encouraged clarification questions and discussions, and we talked about issues and improvements to my solutions. After the on site, there was a final round with the CTO that was done remotely, where we went over my experience and what I was looking for, and there was another technical question asked, which included live coding through coderpad. About a week later, I received an offer

      Domande di colloquio [1]

      Domanda 1

      System design/architecture of a website
      Rispondi alla domanda
      3

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

      avatar
      HENNGE
      3.8★Stipendio e benefit
      avatar
      xneelo
      3.8★Stipendio e benefit