add: challenges structure

Author: marluanespiritusanto

README.md

@@ -1,2 +1,43 @@
-# interview-challenge
-Interview challenge for potential candidates.
+<p>
+  <a href="https://refactoring.do" target="blank"><img src="https://refactoring.do/assets/svg/refactoring-logo-full.svg" width="300" alt="Refactoring's Logo" /></a>
+</p>
+
+# Refactoring take-home coding exercises
+
+## Choose your side
+
+1. [Full-Stack](./challenges/full-stack.md)
+2. [Frontend](./challenges/frontend.md)
+3. [Backend](./challenges/backend.md)
+4. [Mobile](./challenges/mobile.md)
+5. [Quality Assurance](./challenges/qa.md)
+6. [Database Administrator](./challenges/dba.md)
+7. [DevOps](./challenges/devops.md)
+
+## What to expect?
+
+We understand that your time is valuable, and in anyone's busy schedule solving these exercises may constitute a fairly substantial chunk of time, so we really appreciate any effort you put in to helping us build a solid team.
+
+## What we are looking for?
+
+Keep it simple. Read the requirements and restrictions carefully and focus on solving the problem.
+
+Treat it like production code. That is, develop your software in the same way that you would for any code that is intended to be deployed to production. These may be toy exercises, but we really would like to get an idea of how you build code on a day-to-day basis.
+
+## How to submit?
+
+You can do this however you see fit - you can email us a link to download your code from somewhere or just a link to a source control repository. Make sure your submission includes a small README, documenting any assumptions, simplifications and/or choices you made, as well as a short description of how to run the code and/or tests.
+
+## The Interview
+
+After you submit your code, we will contact you to discuss your solution. The interview will cover a wide range of technical and social aspects relevant to working at Refactoring, we will also take the opportunity to step through your submitted code with you.
+
+## FAQ
+
+**Is it OK to share your solutions publicly?** Yes, the questions are not prescriptive, the process and discussion around the code is the valuable part. You do the work, you own the code. Given we are asking you to give up your time, it is entirely reasonable for you to keep and use your solution as you see fit.
+
+**Should I do X?** For any value of X, it is up to you, we intentionally leave the problem a little open-ended and will leave it up to you to provide us with what you see as important. Just remember to keep it simple. If it's a feature that is going to take you a couple of days, it's not essential.
+
+**Something is ambiguous, and I don't know what to do?** The first thing is: don't get stuck. We really don't want to trip you up intentionally, we are just attempting to see how you approach problems. That said, there are intentional ambiguities in the specifications, mainly to see how you fill in those gaps, and how you make design choices. If you really feel stuck, our first preference is for you to make a decision and document it with your submission - in this case there is really no wrong answer. If you feel it is not possible to do this, just send us an email and we will try to clarify or correct the question for you.
+
+Good luck!

challenges/backend.md

@@ -0,0 +1 @@
+# Backend Challenge

challenges/dba.md

@@ -0,0 +1 @@
+# DBA Challenge

challenges/devops.md

@@ -0,0 +1 @@
+# DevOps Challenge

challenges/frontend.md

@@ -0,0 +1 @@
+# Frontend Challenge

challenges/full-stack.md

@@ -0,0 +1 @@
+# Full Stack Challenge

challenges/mobile.md

@@ -0,0 +1 @@
+# Mobile Challenge

challenges/qa.md

@@ -0,0 +1 @@
+# QA Challenge