[autotune]

Honestly I kind of enjoy take home tests as long as they align with what I'm learning and looking to learn. I've had to do a couple take home interviews as well at this point as part of the initial phone screen, although they revolve more around config management tools/Ruby DSL and buildout work so far. So far the tests I've taken have been relevant to what I'm hoping to move into ("DevOps"/automation) so they've been a pleasure to complete. Not only that, but also a base to build on for playing with additional tools in the chain.

The biggest problem with these though is definitely the time crunch. The first one I hadn't realized how long it would take so rushed through it at the end and made mistakes. Second one gave myself a full week rather than 4 days and that's proceeding to an in-person interview, so you need to be taking as much time as they'll allow in order for it to go smoothly.

Also, another project means more documentation added to the repo so that's pretty nice too. If the project didn't align to my interests, which thankfully happen to be stupidly in-demand right now if you have "senior" experience with them, and the position, I'd nope out of the project right away.