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

      Deel

      Engaged Employer

      About
      Reviews
      Pay & benefits
      Jobs
      Interviews
      Interviews
      Related searches: Deel reviews | Deel jobs | Deel salaries | Deel benefits | Deel conversations
      Deel interviewsDeel Backend Engineer interviewsDeel interview
      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 personalized job recommendations and updates by starting your searches.

      Deel interviews FAQs

      • Backend Engineer applicants have rated the interview process at Deel with 2.8 out of 5 (where 5 is the highest level of difficulty) and assessed their interview experience as 20% positive. To compare, the company-average is 51.9% positive. This is according to Glassdoor user ratings.
      • Candidates applying for Backend Engineer roles take an average of 19 days to get hired, when considering 5 user submitted interviews for this role. To compare, the hiring process at Deel overall takes an average of 20 days.
      • Common stages of the interview process at Deel as a Backend Engineer according to 5 Glassdoor interviews include:

        Phone interview:  29%

        Skills test:  29%

        Group panel interview:  14%

        Presentation:  7%

        Other:  7%

        Personality test:  7%

        One on one interview:  7%

      • Here are the most commonly searched roles for interview reports -

        1. Sales Development Representative (SDR)(216) ;
        2. Account Executive(139) ;
        3. Customer Support Specialist(83) ;
        4. Payroll Expert(68) ;
        5. Backend Engineer(56) ;
        6. Software Engineer(44) ;
        7. Customer Success Manager (CSM)(41) ;
        8. Senior Software Engineer(37) ;
        9. Sales Manager(29) ;
        10. Customer Success Manager(28) ;
        11. Payroll Specialist(26) ;
        12. Payroll Manager(24) ;
        13. Customer Service Representative(21) ;
        14. Frontend Engineer(21) ;
        15. Team Lead(21) .


      Glassdoor

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

      Employers

      • Free Employer Account
      • Employer Center
      • Employers Blog

      Information

      • Help
      • Guidelines
      • Terms of Use
      • Privacy & 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.

      Jobs at Deel

      3 jobs in United States
      Software Engineer – Network
      United States
      ·
      $130K - $170K /yr
      (Employer provided)
      View job
      Software Engineer – Control Systems
      United States
      ·
      $130K - $170K /yr
      (Employer provided)
      View job
      Automation Engineer
      Phoenix, AZ
      ·
      $130K - $200K /yr
      (Employer provided)
      View job
      View all Backend Engineer Jobs

      Backend Engineer Interview

      Dec 20, 2023
      Anonymous Interview Candidate
      No offer
      Negative experience
      Easy interview

      Application

      I applied online. I interviewed at Deel

      Interview

      An initial call with an HR person regarding your professional experience—here, you can expect HR-related questions. No big deal. After that, you will be assigned a technical test consisting of building an API with various endpoints, some of which are broken, and some are missing. You need to be familiar with Sequelize ORM. I could pass this phase by linting and moving the project to an MVC-inspired structure (controller, models, repositories, services, etc.). Very easy, to be honest. The third phase is an interview with a technical person, who in my case was someone who could barely speak English, making it difficult to communicate with him. He also seemed tired, like a person who didn't want to be there. My willingness to join the company started decreasing here, and I was afraid of somehow joining this guy's team and getting bored quickly. He will go through your technical test and start asking questions about how you could improve certain parts of the application. The number of questions depends on how well you structured your project at a given time. I was eliminated because he asked a question about concurrency, which I thought I had already addressed, so it wasn't going through my head at the moment. (I should have answered by locking the tables to prevent two requests dealing with the table at the same time.) I have basic knowledge about SQLite, and I thought the lock operation would happen automatically when starting a transaction. My conclusion is that the challenge in the third phase is to guess what your interviewer is trying to talk about. However, if you keep asking questions for clarification, he can understand as if you don't know the answer. Don't blame yourself if you were not able to pass. I have 10+ years of experience and couldn't pass. Sometimes it's just luck and having a good interviewer.

      Interview questions [3]

      Question 1

      Why do want to work at Deel?
      Answer question

      Question 2

      As the project grows up, what changes would you make to not become a mess?
      Answer question

      Question 3

      If two requests are done at the same time, how would you address concurrency?
      Answer question
      13