/algomo-coding-challenge

Coding challenge for Algomo engineering interviews

Primary LanguageTypeScriptMIT LicenseMIT

coding-challenge

Paired Programming Coding Challenge for Algomo Engineering Interviews

Hi! Thank you for taking the time to complete our coding challenge. The objective is is to build an application for triaging issues, during a paired programming interview session

Depending on the role you have applied for, the focus will be full-stack or front-end focused.

We want to understand how you work and get a view into your thought process/problem solving skills. As with all interviews this is a two-way street - it's also an opportunity for you to evaluate working with us! 🙂

tl;dr

  • The paired-programming session should take around 1.5 hours
    • Expect around 1 hour of coding, and 30 minutes at the end for technical questions about your solution
  • We're not expecting you to develop the entire application within the timeslot!
    • It's up to you to decide how to break the problem into smaller features/what to build during the session
    • Ultimately we want to assess your technical skills and problem-solving abilities

Instructions

  • Fork this repository in GitHub
  • Make sure you have VSCode installed, along with the LiveShare extension
  • The back-end should be written using NodeJS/TypeScript, and the front-end using React
    • If you are more comfortable using other languages, please let us know before arranging the interview!
  • Before the interview, you should bootstrap your repository fork with a basic scaffold for the application.
    • You are free to structure the repository how you see fit
      • If you're not sure where to start, we recommend running yarn create vite for the front end or using https://github.com/mantinedev/vite-template
      • For the back-end (if applicable) there are plenty of choices (Nest.js, Express, Koa, Fastify, just to name a few), again if you're not sure which to use, then we suggest Express
    • You do not need to worry about choosing a database - it is completely fine to use stub data instead
    • You should include instructions on how to run the application (e.g. docker-compose up), along with any pre-requisites for installation

Application Requirements

We want you to build an issue triaging board (think something along the lines of JIRA/Linear)

This application should consist of two main services: UI and Issue Management (back-end).

If you are applying for a front-end role, you can ignore the back-end service and instead stub network requests.

Build an application with the following functionality (you may use the layout below for inspiration):

  • Display a list of all Issues to be Triaged
  • Filter the list of Issues
  • View details for the selected Issue
  • Accept or Decline Issues

Issue triaging

Final Thoughts

This exercise leaves you a fair amount of flexibility. This emulates the way we work. We are a dynamic start-up and a successful candidate will often have to deal with similar uncertainty.

Above all, we hope this test is enjoyable! We'd love to hear your feedback too.