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

      Xelix

      Engaged employer

      About
      Reviews
      Pay and benefits
      Jobs
      Interviews
      Interviews
      Related searches: Xelix reviews | Xelix jobs | Xelix salaries | Xelix benefits
      Xelix interviewsXelix Python Backend Developer interviewsXelix 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. Indeed, Inc. "Glassdoor," "Worklife Pro," "Bowls" and logo are proprietary trademarks of Indeed, Inc.

      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.

      Python Backend Developer Interview

      Jul 2, 2026
      Anonymous interview candidate
      London, England
      No offer
      Neutral experience
      Average interview

      Application

      I applied online. I interviewed at Xelix (London, England) in Jun 2026

      Interview

      The interview is made up of 4 stages. First interview is a chat with someone from the talent team. Lasted around 15 minutes. Basic generic questions. Why do you want to work here? Tell me about yourself. What do you know about Xelix? What technologies have you used? I got an email saying the I've moved to the second stage. The email stated, it was going to be a 20 minute interview diving deeper into my experience. When I had the interview with the hiring manager, they didn't really asked about my previous experience, it was more about ways of working, culture. Some of the questions asked. What something you learnt new about Python and where have you implemented it (be it personal or work)? How do you approach learning new technologies? How do you make sure a pull request is ready to be merged? There were probably some other questions but I can't remember. I wanted to asked some questions at the end of the interview, but the hiring manager was like at this stage it's usually to check culture fit etc. The next stage is where you can ask questions. The hiring manager did allow me to still ask some questions but I felt a bit akward so I only ask 2 short questions. I then was moved onto the third stage, which was a 2.5 hour technical test. Essentially, this is broken down into couple segments. Before the actual interview (15 minutes to be exact), I got sent a zip file containing the test that I needed to set up before the actual interview. Then I was on the call with 2 engineers. The first 30 minutes, is just going over the test and making sure I understand the tasks. You then work on the task for an 1 hour alone, time flies real quick. (I didn't manage to complete all the tasks on time). After that, I jumped back on a call with the engineers and discuss my approach and what I did. Questions were based on the task. Why did you this? What's the time complexity on this? How would you improve it to be more performative? Why did you decide to use data type? Could there be a problem using such data type? The test was made up of 2 parts. The first part is just to check your python knowledge. The second part is more around checking your Django knowledge. This tasks involved, building a model based on some csv file. Then creating a managment command to populate the data model based on the data in the csv file. Then lastly to create an API endpoint, that returns that data. I didn't passed this stage, so I don't know what's the last stage is like.