Back-End Developer Johan Sports

Your routine work could consist in:

• contributing to project specifications and assessing project impact in terms of resources and time;

• designing back-end code and infrastructure solutions;

• spotting candidate technologies to support our development;

• when necessary, setting up contracts between developer parties (e.g API, Doc);

• Implement the solutions. Write code Mainly in Elixir, sometimes in python;

• A minimum of security and observability (e.g monitoring) must be considered in the solutions;

• Ensuring tests, documentation and good practices via code reviews;

• Improving/Supporting preexisting code.

Some example projects you could be working on:

• Various user-facing APIs (WEB application, live monitoring application, Mobile application etc…).

• Various downstream services inter-communication.

• External API (e.g data synchronisation with third-party companies).

• Data-pipeline: Ingestion/transformation of objective/subjective data collected from players’ wearables or web/mobile forms.

• Transformation of objective/subjective player data into actionable human advice.

• Help data scientists build ML models providing access to the data they need and integrating their models.

• Reporting engine from aggregated data destined to team managers (e.g CSV/XLSX/PDF).

• Back-office features to support operations (e.g firmware releases, hardware management).

• The modernisation of our system migrating key features from our legacy system.

While limited infrastructure knowledge is required to get started on the job, let us give you an idea of our back-end stack in which you will operate:

The entire infrastructure: applications, storage and domain routing is hosted on AWS. For our storage layer, we use S3, RDS instances (MySql) and DynamoDB. Our computing layer is either based on dockerized applications hosted on EC2 instances (monitored under ECS Custers) or AWS lambdas for ephemeral computing.

Services reside under VPCs and resilient inter-services communication is generally ensured via a combination of queues and event notifications. Most of our infrastructure is maintained and versioned via terraform or the serverless framework. We provision our servers using Ansible and the code release cycle is done via CI/CD.

You could get involved in working/learning Infrastructure development:

• Setting up new infra resources to support new projects

• Setting up appropriate alarms and logging for our various resources

• Cost optimisation (e.g Resources lifecycle purging/archiving stale or less-frequently used objects)

• Automated or manual monitoring/investigation of our system

• Maintenance of our infrastructure as code

• Working on continuous integration/deployment workflow

• Find a good cost/efficiency compromise