Pleo Software Engineer, Backend interview questions

This company's interview process is the biggest joke I have ever experienced. I would strongly recommend never to apply to them. First of all, they took a very long time to get in touch with me after my application. I made my application on 5th August, and they got back to me more than a month later - on 13th September. Despite their tardiness, I somehow agreed to proceed with the interview, not realizing that things would go downhill pretty swiftly. The initial screener call, which took approximately 30 min with one of their Talent Acquisition Specialists mostly went well, but took a bizarre turn when, at the end of the interview, I was given a take home assignment. The take home assignment is not timed, and it involves adding some functionality to a Github repo named Anteus . If you view the forks of this repo, it has been attempted quite a number of times by many developers for the last 3 years (at the time of writing). What was weird was that the challenge involves writing code in Kotlin, and this is a non negotiable. Since the job I had applied to mentioned Typescript, I tried to request for a typescript repo instead but this was denied. After two weeks, despite not being experienced in Kotlin, I managed to submit the challenge, but to my utter shock and dismay my code was not reviewed by an engineer but by another Talent Acquisition Specialist (different from the one who initially contacted me). Predictably, her review of my code was very slipshod, and haphazard. I received a rejection letter barely 10 minutes after she reviewed my code. The reasons for the rejection were bizarre, and even after inquiring for more detailed feedback, was left even more confused. Avoid at all costs.

Interview process was very clear. Had a good initial chat which was more of an informal introduction. I then received a technical challenge todo in my owntime, the documentation is quite good for this. I do not know Kotlin but was able to submit code based on what was already there + looking at the Kotlin documentation. I then had a team interview to go over my challenge, it's focused on justifications for implementations and how they could be improved. It was then followed by walking through how I would solve an example requirement. Finally I had an interview with a hiring manager to discuss common values and also compensation.