Platomics interview questions

1. Talk with a lead developer. They asked me to prepare some code that was written in relevant technologies for the position. He was just looking for a sign that I am capable of thinking for myself and writing normal code. Interviewer was very nice and considerate. In the end interviewer answered my questions 2. Second interview was 30 minutes coding test. Questions are harder Leetcode easy problems, the only hard part is time pressure, but you don't have to do 100%. Interviewer was very nice and friendly. They just want to see how a candidate is thinking, the end result is not as important. 3. I was given a home assignment. That we have reviewed on the third meeting. We went over my code and interviewer really took into consideration the small details that I have added. Anybody who spent 5+ years working with these technologies should be capable of doing this task. 4. The last phase was meet the team interview. Where I spoke with two interviewers. We exchanged some questions about previous experiences and expectations. The whole process lasted less than 20 days. I sincerely think that anybody who did their job well in the past would do well. I have left this review because the other reviews don't reflect my experience at all.

Three calls, all with technical people. No clear description of what the company does, who their customer base is and no mentions of vision, culture and processes. All 3 parts of the interview were technical. First call involved me showing them a piece of code I had worked on. That's not a nice thing to ask from people that have signed NDAs with their employers/clients. Not all of us have open source projects. Second interview contained the typical algorithmic puzzles. These should have been left behind years ago. Final step was a take home assignment. Interviewers expectations were not explicitly stated in the assignment description. He focused a lot on unimportant details and presented his team's conventions as general truths that should be followed by everyone. Terrible interviewing experience with engineers fixating on unnecessary and unimportant details on all three calls.