They made the horizontal cuts evenly spaced between the cutting surface and the top of the onion, which is nonsensical to me. I believe that a single horizontal cut at around 15-20% height would be better for uniformity than a horizontal cut at 50% height.
This way of calculating doesn't take into account the creative ways you can make cuts. You could also do mostly vertical slices, and then slightly angle inwards when you do the final few cuts. That would get you a more optimal distribution as well.
1 - Too much chatter. Part of the assignment is using judgment and working in ambiguity. I probably would have ran with what was given enough to knock out something small and local in an evening or two. Asking questions is usually fine, they even welcomed it, but seems counter to the original ask.
2 - Writing and sharing a proposal seemed like way overkill. You have to remember that these companies are now getting hundreds if not thousands if not tens of thousands of applicants, that is a lot to deal with if everyone does so. I think it's a bit of a disconnect...you feel like you're going above and beyond and being thorough, they feel like it's being a bit long winded and wasting time. That probably explains the nonresponse.
3 - The finished product seemed functional, but seemed a bit overkill on the infra and polish. This is probably a good thing to work with you, but ended up wasting a lot of your time if not being selected, which was the case.
4 - Maybe I missed something, but the requirement asked for terminal inspired. I'm not quite sure precisely what they meant by that, but didn't see any possible interpretation of that in the result.
Anyways, hope you don't take it too negatively or personally - you obviously are a talented individual and moreso seem to really care about your work. Just wanted to play a little devil's advocate with a different perspective.
"Create a terminal inspired email client so we can do an alpha test with some customers" is a reasonable ask for an engineer at an early stage startup. Of course, there would be a bit more specification, but a lot of the details would still be up to the engineer. This applicant wants more certainty than they can get.
This is illustrated by the line: "I would like to know what kind of response I could expect from Kagi if I drive it to completion." This is not a great request to make. There's no way they can answer that question, because there is no certainty available. They're probably getting a few hundred or a few thousand more submissions to evaluate.
Hi, I'm William, the co-founder and CEO of Maestro AI. We're building an all-knowing chief of staff for engineering and product leaders. Maestro provides real-time, comprehensive insights, synthesized from Slack conversations, Jira tickets, and more. We allow leaders to stay in control of deadlines, accelerate their team, and understand and prioritize work.
Our goal is to eliminate information silos and become the OS that helps run engineering teams (and later every type of team).
Here's a recent demo video: https://www.youtube.com/watch?v=Xd7_0fURLxU
We're an early-stage, venture-backed startup, and you'll have the opportunity to shape our product and culture from the ground up.
We're looking for someone who takes pride in their craft, pushes their limits, and takes action to create something new. Our stack is Python on the backend and React/Redux/Typescript on the frontend. We're training our own models in addition to using existing LLMs.
To apply: Please email will+hn at getmaestro.ai with your resume, your Github, and a short note detailing a project you've enjoyed working on. View a full list of our roles here: https://maestroai.notion.site/Maestro-AI-Careers-51385f9fca9...
Abstractly, it's like the model is dreaming of a game that it played a lot of, and real time inputs just change the state of the dream. It makes me wonder if humans are just next moment prediction machines, with just a little bit more memory built in.
Hi, I'm William, the co-founder and CEO of Maestro AI. Throughout my career in software engineering, I've repeatedly witnessed how fragmented workflows and broken processes can stifle even the most brilliant teams. That's why I started Maestro AI. Our mission is to streamline the process of software development, turning chaos into clarity so that teams can accomplish more.
Maestro AI provides real-time, comprehensive insights for teams so everyone can easily see what's happening, how projects are progressing, and where people are blocked. We eliminate information silos by aggregating data from multiple collaborative tools like Slack, Jira, Notion, and Github, enabling seamless communication and informed decision-making across the entire organization.
Here's a recent demo video: https://www.youtube.com/watch?v=Xd7_0fURLxU
We're an early-stage, venture-backed startup, and you'll have the opportunity to shape our product and culture from the ground up.
We're looking for someone who takes pride in their craft, pushes their limits, and takes action to create something new. Our stack is Python on the backend and React/Redux/Typescript on the frontend. We're training our own models in addition to using existing LLMs.
To apply: Please email careers+hn at getmaestro.ai with your resume, your Github, and a short note detailing a project you've enjoyed working on. View a full list of our roles here: https://maestroai.notion.site/Maestro-AI-Careers-51385f9fca9...