Skip to content

Commit

Permalink
Added emphasis to the fact that we have no submission deadline. (#11)
Browse files Browse the repository at this point in the history
  • Loading branch information
wltrup committed Sep 16, 2017
1 parent 90c0cf9 commit c12f858
Show file tree
Hide file tree
Showing 2 changed files with 4 additions and 1 deletion.
4 changes: 3 additions & 1 deletion README.md
Expand Up @@ -50,7 +50,9 @@ As indicated above, we expect all candidates to submit an ["interview demo proje
2. A project you've already done
3. An open source project you've done or contributed to

A demo project should be an example of one's **best** work. We don't just want to see a technically good project; we want to be *wowed* by a candidate's technical skills and creativity. If we then think the demo project is interesting enough, we'll proceed to a face-to-face step, either on Skype (for remote candidates) or in person (for on-site candidates).
A demo project should be an example of one's **best** work. We don't just want to see a technically good project; we want to be *wowed* by a candidate's technical skills and creativity. Note that we don't have a submission deadline so take your time to polish your demo project.

If we then think the demo project is interesting enough, we'll proceed to a face-to-face step, either on Skype (for remote candidates) or in person (for on-site candidates).

That face-to-face step, which normally lasts 90 minutes per session (there may be more than one), typically starts with a discussion around the candidate's project. We normally ask the candidate to implement a new feature (even if it's just using pseudo-code), or to refactor and unit-test a particular component, and in general we aim to have an informal discussion about the candidate's approach.

Expand Down
1 change: 1 addition & 0 deletions demo.md
Expand Up @@ -28,6 +28,7 @@ Before proceeding to the section of your choice, please consider the following t
* **Be consistent in your code**. We advise using something like [raywenderlich's swift style guide](https://github.com/raywenderlich/swift-style-guide) while doing the demo. It's absolutly fine to use any other style, as long as you are consistent.
* Clean the file project structure and remove any unused methods (e.g., from `AppDelegate`). This shows attention to detail.
* Be opinionated regarding any architecture you use and take your time to make it a reflection of your thought process.
* We don't have a submission deadline so take your time to polish your project.

### 1. The babylon demo project

Expand Down

0 comments on commit c12f858

Please sign in to comment.