{"id":19493608,"url":"https://github.com/datapane/be-systems-hiring-challenge","last_synced_at":"2026-03-01T18:34:14.101Z","repository":{"id":55516323,"uuid":"312687251","full_name":"datapane/be-systems-hiring-challenge","owner":"datapane","description":"Hiring challenge for Backend Python / Linux Engineer","archived":false,"fork":false,"pushed_at":"2020-12-01T14:55:19.000Z","size":3,"stargazers_count":0,"open_issues_count":0,"forks_count":3,"subscribers_count":4,"default_branch":"master","last_synced_at":"2025-02-25T20:24:24.084Z","etag":null,"topics":[],"latest_commit_sha":null,"homepage":null,"language":null,"has_issues":true,"has_wiki":null,"has_pages":null,"mirror_url":null,"source_name":null,"license":null,"status":null,"scm":"git","pull_requests_enabled":true,"icon_url":"https://github.com/datapane.png","metadata":{"files":{"readme":"README.md","changelog":null,"contributing":null,"funding":null,"license":null,"code_of_conduct":null,"threat_model":null,"audit":null,"citation":null,"codeowners":null,"security":null,"support":null}},"created_at":"2020-11-13T21:25:02.000Z","updated_at":"2020-11-14T14:07:38.000Z","dependencies_parsed_at":"2022-08-15T02:10:48.713Z","dependency_job_id":null,"html_url":"https://github.com/datapane/be-systems-hiring-challenge","commit_stats":null,"previous_names":[],"tags_count":0,"template":false,"template_full_name":null,"purl":"pkg:github/datapane/be-systems-hiring-challenge","repository_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/datapane%2Fbe-systems-hiring-challenge","tags_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/datapane%2Fbe-systems-hiring-challenge/tags","releases_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/datapane%2Fbe-systems-hiring-challenge/releases","manifests_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/datapane%2Fbe-systems-hiring-challenge/manifests","owner_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/owners/datapane","download_url":"https://codeload.github.com/datapane/be-systems-hiring-challenge/tar.gz/refs/heads/master","sbom_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/datapane%2Fbe-systems-hiring-challenge/sbom","scorecard":null,"host":{"name":"GitHub","url":"https://github.com","kind":"github","repositories_count":286080680,"owners_count":29978794,"icon_url":"https://github.com/github.png","version":null,"created_at":"2022-05-30T11:31:42.601Z","updated_at":"2026-03-01T16:35:47.903Z","status":"ssl_error","status_checked_at":"2026-03-01T16:35:44.899Z","response_time":124,"last_error":"SSL_connect returned=1 errno=0 peeraddr=140.82.121.5:443 state=error: unexpected eof while reading","robots_txt_status":"success","robots_txt_updated_at":"2025-07-24T06:49:26.215Z","robots_txt_url":"https://github.com/robots.txt","online":false,"can_crawl_api":true,"host_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub","repositories_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories","repository_names_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repository_names","owners_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/owners"}},"keywords":[],"created_at":"2024-11-10T21:26:43.393Z","updated_at":"2026-03-01T18:34:14.083Z","avatar_url":"https://github.com/datapane.png","language":null,"funding_links":[],"categories":[],"sub_categories":[],"readme":"# Backend Python/Linux Systems Hiring Challenge\n\n# Introduction\n\nDatapane is an API-driven product for building analytics reports in Python - part of this includes running user's Python scripts and controlling their execution from a central server. This project simulates some of the necessary tasks required in developing such a system.\n\n# Task\n\nFor this task we'll be building a small distributed system, consisting of a server and client, both in Python, that can communicate uni-directionally to send structured data and commands.\n\nThe system must run on Linux, and can make use of any distributed technologies of your choice, for instance for IPC you could look at HTTP, gRPC, zeromq, redis, unix sockets, etc. and for data marshalling you could look at JSON, protobufs, pickle, msgpack, XML, or anything else.\n\n## Server\n\nThe server simply loops taking input from the user via the terminal, and sending commands to the running client.\n\n## Client\n\nThe client should listen for commands form the server and act upon them - it should always be able to accept new messages.\n\n## Commands\n\nThe client must support the following commands that can be sent by the server - the server may send multiple commands and the client should accept these.\n\n### Control commands\n - `start()` - move to `ready` state to start accepting data commands\n - `stop()` - move to `unready` state and stop accepting data commands\n - `terminate()` - immediately stop and exit cleanly, preferably cleaning up any resources first\n\n### Data commands\n\nThese can only be executed when the client is in the `ready` state\n\n - `ping() -\u003e int` - return the current unix timestamp\n - `calculate(x: float, msg: str)` - simulate a long-running computation that takes `x` seconds to run and prints `msg` upon completion\n\nThe following state diagram describes the control commands and how they affect the client state,\n\n![State diagram](./state_diag.svg)\n\n## Technologies\n\n- Build systems, tools, and scripts of your choice, e.g. poetry, `setup.py`, docker, etc.\n- The system must run on Linux and be presented as a set of Docker containers that run using docker-compose.\n- Any libraries you may find useful to help your task, we prioritise using existing libraries to accomplish tasks rather than building in-house and/or writing custom code that wouldn't scale to larger use-cases\n\n## Requirements\n\n- You do not need to worry about client/server service discovery - the locations of the systems can be hard-coded, provided as env vars, command-line parameters, etc.\n- Instructions should be provided on how to build / bundle / start the system\n- You should aim to use the latest Python language features, ecosystem, tooling, and libraries where possible\n\n### Optional Features\n\n- Messages may be untrusted, you should consider how you can defend against that\n- Consider how you would implement bi-directional communication, such that the client could send messages to the server\n- Tests\n\n# Review\n\nPlease don't spend more than 2-4 hours on this - we're looking to see how you approached the problem and the decisions made rather than a complete solution. This should be a fun challenge rather than a stressful endeavour.\n\nThere is no right answer as such, we will mainly be looking at code quality, software architecture skills, completeness of the solution from a software engineering perspective, and clarity of thought.\n\nOnce completed, please create a PR containing your work, send us an email, and schedule a [second follow-up interview](https://calendar.google.com/calendar/selfsched?sstoken=UU1sbG9QV1hfcHlGfGRlZmF1bHR8ODI1ZjRlZWJlZTY0ZTQ1ZTI4MzNkZThhOGQ5MjZkNzg).\n\n","project_url":"https://awesome.ecosyste.ms/api/v1/projects/github.com%2Fdatapane%2Fbe-systems-hiring-challenge","html_url":"https://awesome.ecosyste.ms/projects/github.com%2Fdatapane%2Fbe-systems-hiring-challenge","lists_url":"https://awesome.ecosyste.ms/api/v1/projects/github.com%2Fdatapane%2Fbe-systems-hiring-challenge/lists"}