Should I be worried about overengineering programming assignments given during interview process?

Posted by DormoTheNord on Programmers See other posts from Programmers or by DormoTheNord
Published on 2013-06-19T11:14:57Z Indexed on 2013/07/02 17:14 UTC
Read the original article Hit count: 540

I recently had a phone interview with a company. After that phone interview, I was told to complete a short programming assignment (a small program; shouldn't take more than three hours). I'm only directly instructed to complete the assignment and turn in the code. I was given complete freedom to use any language I wished and was not told exactly how to turn in the code.

Immediately I planned on throwing it on Github, writing a test suite for it, using Travis-CI (free continuous integration for public Github repositories) to run the test suites, and using CMake to build the Linux makefiles for Travis-CI. That way, not only can I demonstrate that I understand how to use Git, CMake, Travis-CI, and how to write tests, but I can also simply link to the Travis-CI page so they can see the output of the tests. I figured that'd make it a tiny bit more convenient for the interviewer.

Since I know those technologies well, it would add essentially no time to the assignment.

However, I'm a bit worried that doing all this for a relatively simple task would look bad. Although it wouldn't add much more time at all for me, I don't want them thinking I spend too much time on things that should be simple.

© Programmers or respective owner

Related posts about interview

Related posts about unit-testing