Technical Hiring Process

Technical hiring is an investment for all parties involved. At, we pledge to iterate and improve the process for a positive applicant experience.

Stage 1 - Online Application

Resume Evaluation

Resumes should be a snapshot of the work YOU contributed to a project. This is your chance to brag about your work, not just the project.

Keep it short - 2 pages maximum.

Keep it simple - photos, family, or demographic information is neither necessary nor encouraged.

We don’t use keyword matching software. Simply mention technologies relevant to the position you’re applying for.


  • Instead of “Worked on food delivery app using Kotlin”, say “Architected and implemented the delivery tracking feature for a food delivery application using Kotlin”.

  • There’s no need to list every technology you’re familiar with as long as you can demonstrate familiarity with the ones relevant to the position you’re applying for.

Evaluation Criteria

  • Clearly communicates your contributions on past projects

  • Demonstrates ability to learn on the job

Questionnaire Submission

User-centricity is a core value of our tech team - which is why follows an offline-first architecture. Adopting this philosophy requires commitment and close collaboration from both our frontend and backend teams.

The questionnaire is a way for you to tell us more about your approach to delivering software that’s both reliable and easy to use.

Your responses to the questions will help us determine whether to move forward with the next stage.


  • Answers should be 3-4 sentences each

  • Give examples from prior experience, when possible

Evaluation Criteria

  • Clear communication style

  • Mission-driven

Stage 2 - Alignment

Call with Talent Team


Once the hiring manager reviews the resumes and questionnaires, passing candidates will be referred to the Talent Team to schedule a phone conversation. We want to make sure we’re having a conversation about role, compensation, schedule and any other expectations sooner than later. This is your chance to ask any questions about the organization, our values, way of working, etc.

Stage 3 - Assessment

Technical Assessment

Take home + 90 minutes

This stage will consist of testing your skills as a developer. The exercise will be tailored to the skills needed for the job - not theoretical questions about computer science.

  1. Take home exercise. This will be tailored to the position and level being considered. We recommend giving yourself no more than 2 hours to complete the exercise. Remember, we don’t expect this to be perfect. This exercise helps start the technical discussion and gives you a flavor of the types of problems we work on solving.

  2. Technical discussion. Use this time to tell us more about your approach to the take-home exercise, what assumptions you made, and anything you would have done differently if you had more time. This is also the time to have a conversation and tell us about past projects and accomplishments you’re most proud of.


  • We recommend taking some time preparing for the interview by reading about our users and associated workflows.

  • Details about our tech stack can be found here and will be helpful to understand the types of technology solutions we are working on

Evaluation Criteria

  • Code quality

  • Attention to quality of software

  • Focus on end users

Final Interview

30 minutes

Frontline workers are the most critical part of the healthcare delivery system. Our product features are designed to keep their focus on patient care, not on their smartphones. This obsession with building the most user-friendly and offline application runs through every member of the team, whether you’re a designer, frontend developer, or backend engineer.

The final stage of the interview is your chance to demonstrate user-centricity in your craft. This stage will also be a place to ask questions about the project, work culture, etc.

The final interview will be a casual conversation with the hiring manager, an engineer, and schedule-permitting a designer. Cross-team collaboration is very important to our culture, so we want to give you a chance to meet a cross-section of the team and ask questions about how we work across disciplines.

Last updated