Skip to contentSkip to footer
  • Community
  • Jobs
  • Companies
  • Salaries
  • For employers
      Notifications

      Loading...

      Elevate your career

      Discover your earning potential, land dream jobs, and share work-life insights anonymously.

      employer cover photo
      employer logo
      employer logo

      Popsa

      Is this your company?

      About
      Reviews
      Pay and benefits
      Jobs
      Interviews
      Interviews
      Related searches: Popsa reviews | Popsa jobs | Popsa salaries | Popsa benefits
      Popsa interviewsPopsa Backend Engineer interviewsPopsa interview


      Glassdoor

      • About / Press
      • Awards
      • Blog
      • Research
      • Contact Us
      • Guides

      Employers

      • Free Employer Account
      • Employer Centre
      • Employers Blog

      Information

      • Help
      • Guidelines
      • Terms of Use
      • Privacy and Ad Choices
      • Do Not Sell Or Share My Information
      • Cookie Consent Tool
      • Security

      Work With Us

      • Advertisers
      • Careers
      Download the App

      • Browse by:
      • Companies
      • Jobs
      • Locations
      • Communities
      • Recent posts

      Copyright © 2008-2026. Glassdoor LLC. "Glassdoor," "Worklife Pro," "Bowls" and logo are proprietary trademarks of Glassdoor LLC.

      Company Bowl sample

      Want the inside scoop on your own company?

      Check out your Company Bowl for anonymous work chats.

      Bowls

      Get actionable career advice tailored to you by joining more bowls.

      Followed companies

      Stay ahead in opportunities and insider tips by following your dream companies.

      Job searches

      Get personalised job recommendations and updates by starting your searches.

      Backend Engineer Interview

      20 June 2021
      Anonymous employee
      Accepted offer
      Positive experience
      Average interview

      Application

      I applied through an employee referral. The process took 3 weeks. I interviewed at Popsa in Mar 2021

      Interview

      The whole interview process consisted of 3 stages, from start to finish this took around three weeks. The first stage was a one hour chat with the CTO, along with an Engineer from the Platform Team. This was super laid back and was mostly involved talking about the background of Popsa as a company, as well as my own as an engineer. Shortly after this I was sent a take-home test, this was relatively straightforward - but very open ended, the official guidance given was that it should take no more than 3 hours. I completed the task in Golang, but the team were open to any language here. The final stage was a discussion with two engineers from the team, as well as the head of operations. Again this was fairly relaxed (though the more interviewy of the two), this time with questions focussing on the solution I'd put together for the take-home test. Overall I had a really positive interview experience with Popsa (especially for a remote one). The process was much more conversational than I've had elsewhere, with everyone coming across genuinely interested in hearing my answers / experiences, rather than trying to catch me out with awkward questions.

      Interview questions [2]

      Question 1

      How would you approach the task differently if you had more time?
      Answer question

      Question 2

      What would you do to make your solution production ready?
      Answer question
      3
      avatar
      Popsa response
      4y
      🙌 Thank you for the review — we're always looking to improve our process so any suggestions you have would be very welcome!

      Other Backend Engineer interview reviews for Popsa

      Backend Engineer Interview

      11 May 2021
      Anonymous interview candidate
      No offer
      Negative experience
      Average interview

      Application

      I applied online. The process took 4 weeks. I interviewed at Popsa

      Interview

      Applying for a position at this company is a complete waste of time. They claim to open to the idea of remote work but interviewing with the company very much feels like you are having to convince them that this is a good idea. They talk at length about how well their culture works within an office environment whilst acknowledging they aren't sure whether this will translate well to remote working. They also didn't seem to know whether I would have to go into London on occasion and the answers I received differed depending on who was answering my question. Thus, leading to unnecessary confusion from the get-go and was made worse through (what felt) like a never-ending recruitment process. There are at least four stages to the interview/recruitment process and mine are as follows: - Initial call with the CTO, he clearly passionate and gives an insight into the history of the company and its future plans - Another call with two of the devs to see if you are a good culture fit for the company. This was quite an informal chat discussing your previous experience and generally how you work - A tech test, relatively simple and open-ended exercise with a fixed time limit - Another call going over your implementation details of the tech test with two different devs to the previous stage. It was at the last stage where some major red flags started to become apparent. When I spoke to the two devs, they didn't seem all that keen to talk to me. Their awkwardness meant that the conversation was full of a lot of breaks and pauses and very convoluted questions that they themselves seemed to get confused at throughout the interview. As I explained my tech test and my thought process, it felt as if the devs hadn't read through the readme notes and didn't seem to understand the solution as I explained it to them. This made me feel rather annoyed as this felt like this was due to the lack of experience of the people interviewing me, they would be colleagues had I got the job and not my boss. Considering the many stages of this interview process, being told that the reason you have been rejected for the role is that you aren't interested in the position is quite frustrating. I didn't receive any other feedback despite all the time invested in this process and felt that reason didn't feel satisfactory and a bit of a slap in the face. So, I would say to future candidates, be very wary of applying.

      Interview questions [1]

      Question 1

      How would your solution cope if one of the external providers was not able to fulfil the request?
      Answer question
      6
      avatar
      Popsa response
      4y
      Thank you for this review — we pass a lot of information back to our recruiters so we're sorry if it didn't all get back to you. Unfortunately, the technical task you provided had several issues with it. We have used this task many times before but yours was the least sophisticated implementation we've ever been provided — for example, it even failed to run successfully on the sample files bundled with the task. The final stage meeting was an opportunity to talk about all the future improvements that could hypothetically be made to the tech task; to demonstrate your experience with Go and grasp of software engineering principles, but most importantly, how your decisions affect the wider business and end users. However, when reviewing the task with us, you were unprepared - not even having the task to hand. Instead of being able to take us through your implementation as would be typical, we had to screen-share your task while you instructed us on how to navigate it - this was always going to be a bit awkward and I suspect is what the feedback that you "weren't interested" relates to. Whilst it is unusual for us not to make an offer after candidates complete a technical task (the third and final stage) it does happen very occasionally as a result of the implementation and the discussion around it not quite meeting expectations from the two preceding meetings/calls. We wish you all the best for the future.