The hiring process starts with a 1 hour talk with the SVP of engineering. This is a set o presentation about product / teams / hiring process / etc. The presentation were generally interesting and useful. What I missed is that the talk was a bit of a one sided conversation. They do not want to learn about you, your experience or skills at this point. The next step is a code project. The task is to build a (seemingly) simple web application, based on a set of instructions in a PDF. The project is expected to "take about twelve hours to complete". You have 4 days to submit a solution. The project is needed to be done is a given web framework. This was a new framework for me. But nothing seemed wrong with that, until I submitted a solution. After submitting a solution, they rejected my application. After I asked for feedback, it turned out their actual requirements and expectations, were not really clear and far from what was in the provided instructions: - what they expect is a fully polished, fully (/over) tested, production ready and bug-free project - you're expected have tests from unit to top-level app tests (requirements only mentions "some automated test coverage") - you're supposed to implement some use cases which are not clear and not even possible according to what is in the given instructions Until this point in the hiring process, they showed like zero interest to learn more about my experience or skills. It is a bit unfortunate that they expect you to take a considerable amount of time doing the code project, but then they do no even take the effort to have a meaningful face-to-face conversation with you. This feels like a bit of a lack of respect towards the candidate.