• Stars
    star
    200
  • Rank 195,325 (Top 4 %)
  • Language
    Objective-C
  • Created about 8 years ago
  • Updated almost 6 years ago

Reviews

There are no reviews yet. Be the first to send feedback to the community and the maintainers!

Repository Details

Interview Demo Project for babylon health

babylon iOS recruitment process

At babylon, we firmly believe that transparency is a core value that should be present in everything we do, and hiring the best person should reflect that belief. That's why we in the iOS team have open-sourced our recruitment process, for a fairer assessment process in which candidates know exactly what to expect, all the way to the questions we may ask during a face-to-face interview.

We also aim to be as flexible as possible by equally accepting applications from candidates who want to work on-site at our office in London, or who want to work remotely, or who have a limited amount of time to write a demo project, or who have open-source contributions.

Our expectations

babylon aims to hire only the most qualified people available at any given time. That doesn't mean that a candidate must have several academic degrees or have years and years of experience. We value potential equally as much as knowledge and experience. Above all, we value one's ability to think independently and to engage. As effective as they may be, we don't want robots.

Additionally, we want to hire people who are reasonable, professional, and fun to work with. After all, they are people we will spend a great deal of time interacting with on a daily basis.

As such, these are the main areas the iOS team will focus our assessment of candidates on:

  • Technical expertise
  • Languages (Swift, Objective-C) and platforms (iOS, watchOS, tvOS, macOS)
  • Architectural design patterns (MVC, MVVM, Viper, etc)
  • Knowledge of iOS APIs
  • Knowledge of the development cycle
  • Knowledge of reactive programming
  • Interview demo project
  • Interest in sharing one's knowledge
  • Interest in learning new knowledge
  • Interest in keeping oneself up to date
  • Ability to think and work independently
  • Ability to work in a large team
  • Professional and personal maturity
  • Overall attitude
  • Likelihood of fitting in well with the company's culture
  • Is the candidate someone we would like to work with on a daily basis?

The iOS recruitment process

Our recruitment process is different for candidates who are interested in working remotely and those who are interested in working on-site at our office in London, in three ways:

  • remote candidates are required to be proficient in reactive programming (ReactiveSwift/ReactiveCocoa or RxSwift) at an above-average level
  • remote candidates are required to use reactive programming in their interview demo projects
  • technical interview sessions differ in number and duration:
    • on-site: initial call -> demo -> 3-hour face-to-face technical interview
    • remote: initial call -> demo -> one or more Skype interviews -> 1 working day with us (at our expense)

As indicated above, we expect all candidates to submit an "interview demo project" but, in order to be accommodating of different schedules, we provide three different ways in which a candidate can submit a demo of their work. Only one of these is required.

  1. The babylon demo project
  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. 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.

We may also focus on more technical aspects and ask a number of highly technical questions. As indicated earlier, we have open-sourced these questions as well since we believe that a fully open recruitment process gives all candidates a fairer chance to prepare themselves, and makes our assessment uniform across all candidates.

Above all, be yourself and thank you for taking the time to apply to babylon health! 🌈

Oh, and if you happen to know someone who might be interested in applying for a position with us, please point them to our careers page.

We look forward to hearing from you!

More Repositories

1

fastText_multilingual

Multilingual word vectors in 78 languages
Jupyter Notebook
1,195
star
2

DrawerKit

DrawerKit lets an UIViewController modally present another UIViewController in a manner similar to the way Apple's Maps app works.
Swift
780
star
3

ios-playbook

Ruby
397
star
4

orbit-mvi

An MVI framework for Kotlin and Android
Kotlin
384
star
5

Bento

Swift library for building component-based interfaces on top of UITableView and UICollectionView 🍱
Swift
372
star
6

certificate-transparency-android

Certificate transparency for Android and Java
Kotlin
198
star
7

ReactiveFeedback

Unidirectional reactive architecture
Swift
158
star
8

rgat

A TensorFlow implementation of Relational Graph Attention Networks, paper: https://arxiv.org/abs/1904.05811
Python
114
star
9

hmrb

Python
70
star
10

android-playbook

Babylon Health Android Team Playbook
68
star
11

Stevenson

Stevenson is a Vapor framework designed to build integrations between Slack apps, GitHub, JIRA and CI services (CircleCI).
Swift
58
star
12

counterfactual-diagnosis

Python
54
star
13

Tota11y

Accessibility visualization toolkit for web content creators and editors.
JavaScript
44
star
14

fuzzymax

Code for the paper: Don't Settle for Average, Go for the Max: Fuzzy Sets and Max-Pooled Word Vectors, ICLR 2019.
Python
43
star
15

corrsim

Code for the papers: Correlation Coefficients and Semantic Textual Similarity, NAACL-HLT 2019 & Correlations between Word Vector Sets, EMNLP-IJCNLP 2019.
Python
35
star
16

primock57

Dataset of 57 mock medical primary care consultations: audio, consultation notes, human utterance-level transcripts.
Python
35
star
17

lit-fhir

Opinionated library for easily constructuring FHIR (http://hl7.org/fhir) resources in Scala and Java.
Scala
35
star
18

Wall-E

A bot that monitors and manages your pull requests.
Swift
32
star
19

github-proxy

A minimal caching proxy to GitHub's REST & GraphQL APIs
Python
29
star
20

neuralTPPs

Shell
27
star
21

medisim

Medical Similarity Dataset creation from SNOMED
Python
27
star
22

simba

Semantic similarity measures from Babylon Health
Python
16
star
23

decoding-decoders

Python
12
star
24

EHR-Rel

Biomedical concept relatedness benchmark sampled from electronic health records
10
star
25

multiverse

MultiVerse: Probabilistic Programming Language for Causal Reasoning
Python
9
star
26

TwinNetworks

A library for handling Structural Causal Models and performing interventional and counterfactual inference on them.
Python
9
star
27

MCSG

Python
8
star
28

web-interview

JavaScript
6
star
29

nameko-extras

Nameko run with autoloading, logging file CLI option
Python
6
star
30

event-stream-registry-ui

A React component for observing and monitoring event streams.
TypeScript
5
star
31

slack011y-bus

Python
4
star
32

sticky-layoutmanager

Java
2
star
33

fhir-hydrant

FHIR templating engine
Scala
2
star
34

snow-owl

🦉 Snow Owl - production ready, scalable terminology server (SNOMED CT, ICD-10, LOINC, dm+d, ATC and others)
Dockerfile
2
star
35

terraform-provider-aws-babylon

Go
1
star
36

laymaker

1
star