Backend Engineer - Real-Time Esports Data (m/f/x)
At a glance
Mid-level Backend Engineering role at GRID eSports GmbH. Remote, Poland · full-time.
Pay not stated Backend Engineer salary
remoteroles summary, based on the employer's posting.
What you'll do
- Build new mission-critical services and improve the dependability of existing backend systems
- Shape technical direction with experienced colleagues and contribute feedback during architecture discussions
- Work with product stakeholders to share progress and explain technical considerations
- Use automated tests, monitoring, alerting and CI/CD to support robust services
What you bring
- At least three years of professional experience and deep knowledge of a strongly typed language such as Kotlin or Go
- Experience with REST or GraphQL APIs, microservices, and container or orchestration platforms such as Docker or Kubernetes
- Knowledge of API design, including clear documentation and small, extensible contracts that limit breaking changes
- Understanding of fault tolerance and complexity trade-offs, plus familiarity with JIRA, Agile and Scrum
Who this fits
This mid-level remote role is based in Wroclaw, Poland, and requires you to work in the CET time zone. It suits an engineer who enjoys building reliable, well-tested systems and communicating clearly with remote colleagues.
From the employer
Are you passionate about building event-driven systems?
Do you have a strong grasp of Kotlin or Go?
Do you enjoy finding solutions for significantly impactful challenges?
If the answers to the above questions are yes, then this role could be ideal for you!
What you will do
Build greenfield mission-critical services and expand the reliability of existing ones
Help to shape GRID's technological landscape together with experienced colleagues
Participate in architectural discussions, providing feedback to coworkers and ensuring good practices
Work closely together with product stakeholders to communicate progress and considerations effectively
Your skills will include (must have)
Minimum of 3 years of commercial experience
Deep knowledge of a strongly typed language (preferably Kotlin / Go)
Explicit (nullable) types
Strong, minimal contracts
Helpful abstractions and class hierarchies / compositions (introduced at an appropriate time)
Ambition to build robust, high-quality mission-critical systems, leveraging the power of:
Automated testing
Automated monitoring and alerting
CI/CD infrastructure
Know-how of good API design (preferably REST / GraphQL), paying attention to:
Documentation
Self-documenting naming and structures
Minimal and extendable contracts (while minimizing breaking changes)
Experience with GraphQL/REST APIs, micro-service architecture and container / orchestration systems (preferably Docker / Kubernetes), while bearing in mind:
Complexity trade-offs
Fault-tolerance design
Knowledge of JIRA, Agile and Scrum
Good communication skills, especially when working with remote teams
Good attention to detail
Being able to work CET time-zone
Nice to have
Production experience with designing and maintaining GraphQL APIs.
Knowledge of eSports and gaming.
The ability to thrive in a fast-paced software startup that has incredible potential
A passion for software engineering while writing clean, well-tested code
Enthusiasm for working in a Lean, fully Agile environment
Comfortable using AI tooling where necessary (ex. open code, github copilot, claude code)
Knowledge of modern AI workflows
What you can expect from GRID’s Engineering Team
Impactful: With a robust CI/CD process, and a full suite of automated tests our engineers ship daily, allowing you to make impact on the product from day one with peace of mind
Agile & Inclusively: We’ve developed our own kanban-based way of working that is constantly being improved and adapted by the self-organizing product-engineering teams. Opinions and ideas are valued from all
Quality: Achieved by ensuring detailed stories and epics, high test coverage, a thorough code-review process, consciously taking on technical debt and an open culture of sharing opinions
Organized: We strive for considered decisions, creating software that lasts. We document them in decision records, which any engineer in any team can drive