3 ms·
I highly doubt you can produce something that would get you an offer in 2 hours for this task, given its breadth and human nature to worry and attempt perfectio
by drewbitt 1y ago
I highly doubt you can produce something that would get you an offer in 2 hours for this task, given its breadth and human nature to worry and attempt perfection to impress. You are likely competing with much more engineered solutions.
- thiht 1y agoDamn now I’m curious what I could do in 2 hours, this is the kind of things where you can easily get carried away so 4 hours feel like 2. I don’t have 2 hours (or 4) to waste to do this but it itches a little bit. Anyway in 2 hours I’m pretty sure I can write some Go code that would get me an offer. This is not about the amount of features, it’s about giving them what they want.
- josecodea 1y ago> Anyway in 2 hours I’m pretty sure I can write some Go code that would get me an offer. This is not about the amount of features, it’s about giving them what they want. Please do it, get the offer that I didn't, maybe you could even write a blog post about how easy it is and how wrong I am! ;)
- thiht 1y agoI’m sorry I didn’t want to offend you. The thing is I did a few interviews for Go positions last year and I have a lot of experience with Go so yeah, I’m confident in my skills. I’ve also been on the other side of the process many times and I know exactly what they look for. I’m not saying this test is easy, I’m saying I’m good at it and prepared for these kinds of take homes. I don’t agree that it’s a bad technical test though, and reading your article I can say your approach was suboptimal. If you keep interviewing for startups you need to put yourself in their shoes. To quote the test: > This project tests your ability not only to code, but to deal with ambiguity and open-endedness