https://blog.takehome.io/post/ Recent content in Posts on Takehome.io Blog Hugo en-us Tue, 08 May 2018 09:03:17 +1000 https://blog.takehome.io/post/conway/ Tue, 08 May 2018 09:03:17 +1000 https://blog.takehome.io/post/conway/ “organizations which design systems … are constrained to produce designs which are copies of the communication structures of these organizations.” — M. Conway Your software architecture reflects your org chart. The interview process you put candidates through reflects your organisational culture. This process sends a loud message about what your company will be like to work for. By definition, the people getting this message are the candidates you’re most interested in hiring. https://blog.takehome.io/post/good_challenges/ Fri, 04 May 2018 14:42:10 +1000 https://blog.takehome.io/post/good_challenges/ Last time we established why code challenges are important. Now it’s time to talk about what separates a good challenge from a bad challenge. Stick to the following principles and you’ll get something great. Concise. You want great people. Everyone wants great people. Therefore, it’s pretty unlikely that your candidates are only going to be interviewing with you. If someone has time to do a five-day unpaid technical challenge as part of an interview process that’s probably not a positive signal. https://blog.takehome.io/post/why_code_challenges/ Thu, 22 Feb 2018 14:46:03 +1100 https://blog.takehome.io/post/why_code_challenges/ When you’re hiring software developers, it’s vital to assess that they can actually solve problems with code. In my experience, this is harder to get right than you may think. Let’s take a look at four popular solutions to this problem, and try to work out the best option. A quick chat Most interviewers first try a general, fairly freeform conversation about code and technical matters. As they talk, they’ll use their intuition, experience and common sense to get a feel for how experienced and competent the candidate is.