Skip to content
Open
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
18 changes: 10 additions & 8 deletions README.md
Original file line number Diff line number Diff line change
Expand Up @@ -19,19 +19,21 @@ We leave it to you to decide how to transmit the data between the client and the

You should use engineering best practices where appropriate. Principles we value include: security, performance, readability, testability, scalability, simplicity. You should also aim to achieve a clean separation of concerns between components of your solution; using the MVC pattern, for example.

## The Deliverable
### The Markup

* A bundled/archived repository showing your commit history or a link to an accessible private repository with your work in (Github can host private repositories at a cost; there is no charge for doing so with Bitbucket). You could fork this repo in git, but any VCS is fine. Git example for sending us a standalone bundle:
An example of the initial HTML form is [provided in this repository](markup.html).

git bundle create <yourname>.bundle --all --branches
## The Deliverable

* A covering note explaining the technology choices you have made.
* Any instructions required to run your solution and tests in a Linux environment.
Replace the contents of this README.md with:

## The Markup
1. A covering note explaining the technology choices you have made.
1. Any instructions required to run your solution and tests in a Linux environment.

An example of the initial HTML form is [provided in this repository](markup.html).
Email as an attachment or a link the git bundled repository showing your commit history with all your commits on the master branch:

git bundle create <anything>.bundle --all --branches

## Assessment Policy
## Equality & Diversity

We consider all candidates equally, fairly and without bias. To that end, we ask that you do not leave any personally identifying information in your submission (such as your name within an author field or file, or in use as test data). We run all VCS-based submissions through an anonymiser before assessment, so that there is no identifying information in the commit history, but this will only remove references in the committing author and email address, not deep in the code submitted.