Hello! 👋

Welome to the repository that we send to candidates interviewing for technical roles. This is a public facing repository, and if you find this and are interested in working with us, please get in touch - we're pretty much always hiring.

If you stumble upon this repository, are looking for work, and think that you might be a good fit, please get in touch.

1. First stage interview - low tech, meet and greet.
2. Technical test - take home, in your own time.
3. Final interview and interactive code review / demo of technical test
4. Decision / Offer

We strongly believe that seeing some code you've written is the best way for us to understand your skillset, and if we'll be happy working together. That said, we understand people have different kinds of constraints on their time and personal life, so we offer the following options for technial asssesment:

1. A technical test that you can take home and do in your own time. (Most common)
2. A show and tell where you bring some code you have already written that you believe is interesting and exemplifis your skillset. (Second most common)
3. A pairing excercise on the technical test with one of our engineers. (Least common)

We have no bias or preference as to which of the above options you choose - though most candidates tend to prefer the take home technical test.

Included in this repository is The Diamond Kata - our default technical test for engineering roles.

The kata shouldn't take longer than about 60 minutes to complete - while we're not going to check, please don't spend more than about an hour or two solving this problem, we don't believe in labourious and long technical test processes and would rather have a conversation with you about your approaches if you struggle to complete the test.

We expect that your solution is supported by tests - TDD and unit testing are at the heart of our engineering culture at NewDay, and we're very much looking for people who are able to write tests that are easy to understand and maintain.

The diamond kata is well known, with many different solutions that are well documented - but we're looking to learn about how your code rather than just if you can complete the kata. We understand we live in the real world, and we won't penalise you for researching solutions, but equally, we'd recommend doing your own implementation!

Good luck <3

We accept test results in any way!

• Send us a link to your fork on GitHub
• Send us a zip file or archive
• Send us a link to a codepen / interactive sandbox

We would advise against opening a pull request though, as this is a public facing repository.