I applied through a recruiter. The process took 2 weeks.

I am approached by their director. I am not looking for a job but I still gave it a try as the founders are my alumni. Phone interview with their recruiter about the company and the position. 45 mins of zoom chat with team leads. It's all good till here. Take home code challenge of intermediate level difficulty. You are expected to complete the test within 4 hours. But if you really timebox your solution as I did, you will be punished.

They are probably looking for engineers who can work independently without asking any questions to an incompetent project manager. The requirements are poorly defined with typos. I have to code with a lot of pre-assumptions and I put all the questions in the README. As a result, the feedback from the reviewers is basically what I wrote in the README. I got rejected as they said although my code is correct and performant, I've neglected some detail.

Turns out they intentionally give the faulty requirements as part of the test. As in the requirements, it says "You may assume that the inputs are streamed at a constant rate of one per second. ie. for two consecutive entries in the input file, they will have timestamps that differ by one second". I optimized my solution based on this statement with a comment, but the feedback said "didn't handle the scenario where the inputs are not streamed at a constant rate". Lol jokes on me.

In the requirements, it says:

• correctness
• code structure
• clean, readable code
• performance

Although not mentioned in the requirements, my submission is assessed by the test coverage (they are not happy about the 75% test coverage on my submission as part of the feedback). The recruiter said he would call me the next day 9am, he didn't. Then he said he would call me at 1 pm, I didn't get the call until 3 pm. He didn't respect my time as a candidate.

Take home code challenge of intermediate level difficulty algorithms. You are expected to complete the test within 4 hours. But if you really timebox your solution as I did, you will be punished.

They are probably looking for engineers who can work independently without asking any questions to an incompetent project manager.

The requirements are poorly defined with typos. I have to code with a lot of pre-assumptions and I put all the questions in the README. As a result, the feedback from the reviewers is basically what I wrote in the README.

I got rejected as they said although my code is correct and performant, I've neglected some detail. Turns out they intentionally give the faulty requirements as part of the test as in the requirements, it says:

"You may assume that the inputs are streamed at a constant rate of one per second. ie. for two consecutive entries in the input file, they will have timestamps that differ by one second"

I optimized my solution based on this statement with a comment but the feedback said "didn't handle the scenario where the inputs are not streamed at a constant rate" : lol jokes on me.

In the requirements, it says: Submissions will be assessed on:

• correctness
• code structure
• clean, readable code
• performance

Although not mentioned in the requirements, my submission is assessed by the test coverage (they are not happy about the 75% test coverage on my submission as part of the feedback).

Talk about some technical problems you have encountered and how you solved the problem. Easy algorithm questions and some technical details.