3

Hey! Just curious, is it normal that a technical test/challenge takes me more than a day to do?

I have been interviewed for a front-end role, and was given a react challenge. They said that it shouldn't take more than 2 hours ('hopefully' is what they added at the end). But i've been doing this challenge for a day now and it's only 60-70% done.

It's not complicated, and I do know how to do it, and, even, do it properly, it just takes a lot of time for me to code, i.e. develop components, change webpack when needed, read react materialize-ui (css framework) docs, then destructure json response from the api they provided and put this information on a page, then try to compile to the right format (they want single .html element with inline js and css as a deliverable).

So my question is, am I shit or is it unreasonable for a company to ask do so much coding or a little bit of both?

What's your experience usually when looking for a job in 'hip' and 'cool' startups?

Comments
  • 1
    It is just a strategy to test your endurance
  • 2
    Typically I try to approach these problems in a way that clearly demonstrates that I know what I'm doing, but while doing the absolute bare minimum to get it done. For example, I intentionally don't handle edge cases that aren't specified and then I put a TODO note to mention I didn't cover it. Write these sorts of problems as a proof of concept rather than an MVP.
  • 1
    They way you describe it, I think it sounds totally reasonable. I guess it's two hours if you wrote the test and/or know all the stuff by heart, kinda like when people put text on their videos and leave you one second to read five paragraphs because THEY know what it say... Don't worry about it.
  • 1
    Thank you, all! Really appreciate your tips and wisdoms! :)
Add Comment