If you rely on people to work independently, you just can't hire someone who wants feedback everyday to see if they are still on the right track.
You need to have discussions to talk about things like:
* common UX language
* common API expectations
* programming language choice
(because you will not be the only person to work on it)
* in-app / domain language choice
(because your users need to know what a word means.)
* library choice (because you will not be the only person to work on it)
* storage strategy (because there may be legal requirements here)
Ignoring all that and letting all the engineers just run wild is a great way to make a very painful company to work with and cross-collaborate on.This isn't exactly the same as if I give people a test on their ability. It's different. In here you pass if you did something that scores well in a metric that you're not told about. It's not very different than if I gave you a take home assignment which is just literally "code something - you have to be good at ambiguity!" Joking, you just have to guess the thing I had in mind. It's very inconsiderate to people, and doesn't tell me anything good about this Vlad person.
> To him, submitting a long design doc where you go "I am going to use Galactor. I will make sure the project is florp-ready. I will fleem." is the exact opposite of cool.
Am I supposed to guess this much?
Do they expect me to creep on their social media to figure this out or something?
Finally, I made it abundantly clear that I am uncool, so giving me the "go ahead", simply to satisfy their curiosity... I hope they are treated the same as they treat other people.
No ill will against you, if anything you are giving me a plausible explanation where I have none. I just wish I had come across a post like mine earlier, and I hope that we, as a collective, start categorizing any job with a "take-home" as a job for the "cool kids". That way, all of us boring and experienced engineers may force companies to adapt if they actually want our labor. And those that do not adapt, we can infer the type of company that "offers" the role.
Quite frankly: yes, I am pretty sure they did. You said you "had heard about Kagi Search as a reputable company" but the point is that they make a specific product for a specific group of people and if you don't "get" that they are not going to hire you. There are a lot of startups like this, mind you, and many of them are weird cults so I understand the hesitation to spend the time learning what everyone's gimmick is. But Kagi is not one of those companies where you get in without knowing what they want. It's not Google where you can get in by knowing some algorithms or your local medical startup that just wants anyone who can write React. Notably I say this without making a value judgement of whether it is "better" or "worse" than those companies. That's just…how it is. Smaller companies, and ones that are more founder driven, tend to have more unusual and specific things they are looking for.
Re: the rest of your post; I think you deserve to be upset that you wasted your time here, and that they didn't communicate clearly with you. That much is pretty obvious. Regardless, I feel like you're still missing something here, and that makes me a little sad. Kagi is definitely not the right place for you, and they should have done better here. You are not "uncool" and take-homes are not for "cool kids". You just have a different working style or stack or whatever than what Kagi was looking for. I am sure your work is fine and that there is someone out there that thinks your project is cool and what Kagi was looking for was boring. Kagi thought my work was interesting but I assure you that a lot of people would find it incredibly tedious and uninteresting.
My goal here was to give you my view of what I think their view was. I'm not really here to condemn or praise it as there are plenty of other people doing that. I just want you to understand it, rather than it leaving you confused and upset.
When I went through the process the company was very small and Vlad personally reviewed applicants, and he used take home projects like this one. It seems like the company has grown larger so now he isn't looking at them himself anymore, but the essence seems the same. If you ever talk to him you'll find that he's basically the Hacker News commenter stereotype and his interview is really a vibe check to see if you seem cool. To him, submitting a long design doc where you go "I am going to use Galactor. I will make sure the project is florp-ready. I will fleem." is the exact opposite of cool. When the assignment says "I want a terminal-inspired email client" the project that passes with flying colors has keyboard shortcuts for everything and comes with a paragraph explaining how it never takes more than 2ms to draw a frame. I suspect the interviewer thinks you are too "enterprise-brained" to work at Kagi.
Now, is this actually a good way to screen people? A bunch of other people here have opinions on it, so I won't rehash it too much. There are obvious problems with it. Vlad basically wants people who think like him. This kind of interview has a lot of problems that have been discussed and studied at length. But if you understand that and are privileged enough to go through that process, the task will actually make sense to you. I think Kagi could do a better job at communicating this. It's unfortunate that you had to waste a bunch of your time to get to this point but I hope you can find something else that matches your working style better.