Python Engineer

The initial focus will be building and maintaining Python daemons and backend services supporting the customer identity and access management layer. The core platform is Django-based, with surrounding Python services using Flask and related tooling.

You will need to become productive quickly in an existing production environment. This is not a long ramp-up training role. We are looking for someone with strong Python judgement, good debugging instincts and the ability to work effectively on production-facing services from the start.

As the role develops, you will work more broadly across the platform, building new features and integrations with the wider product ecosystem.

Responsibilities

You will:

• Design, build and maintain production Python services, daemons and backend components.
• Build reliable integrations between identity, customer platform and product systems.
• Work with Flask-based services and a Django-based CIAM platform.
• Develop APIs, background workers and internal services that are robust, observable and maintainable.
• Work in an OpenAPI schema-driven workflow, using schemas as part of service design, implementation and integration.
• Work with relational databases, data models and transactional workflows.
• Contribute to customer-facing platform features used by players, leagues and administrators.
• Improve system reliability, logging, monitoring, error handling and operational tooling.
• Write clean, tested Python code that other engineers can understand and safely extend.
• Review existing code, rapidly understand new functionality, and adopt established patterns where appropriate.
• Participate in technical design, code review and production support.
• Work closely with a small senior team where individual judgement and ownership matter.

Do you have experience in UNIX?, We are looking for evidence of strong engineering capability rather than a fixed number of years.

You should be able to demonstrate:

• Strong Python engineering skills in production or production-like environments.
• Comfort explaining Python internals in detail, including runtime behaviour, packaging, dependency management, object model, concurrency trade-offs and performance implications.
• Familiarity with Flask and/or Django, ideally with practical experience building or maintaining production services.
• Good understanding of HTTP APIs, backend service design and integration patterns.
• Experience working with OpenAPI schemas as part of a schema-driven development workflow.
• Experience building daemons, workers, scheduled processes or long-running services.
• Strong SQL and relational database skills, ideally PostgreSQL.
• Good instincts around authentication, authorisation, sessions, tokens or customer identity flows.
• Familiarity with Unix-like operating systems, process models and service operation.
• Strong understanding of Unix filesystem security, including discretionary access controls, and how these affect the security model upheld by D-Bus and other daemons.
• Experience writing tests and debugging complex backend behaviour.
• Familiarity with Linux environments and deploying or operating backend services.
• Ability to reason about reliability, data consistency, failure modes and edge cases.
• Strong ability to rapidly learn, understand and safely adopt unfamiliar code or new functionality.
• Clear communication skills and the ability to explain technical decisions.

Security mindset

Security is not an afterthought in this role.

We are looking for someone with a security-driven mindset who can reason clearly about how systems fail, how privileges are controlled, and how services should be hardened.

You should be comfortable discussing a broad range of security architectural concepts, such as:

• Defence in depth.
• Least privilege.
• Authentication and authorisation boundaries.
• Secrets management.
• Service isolation.
• Secure daemon design.
• Filesystem permissions and ownership.
• Process privileges and escalation risks.
• API security.
• Auditability and traceability.
• Secure-by-default engineering practices.

You do not need to be a dedicated security engineer, but you should be able to identify risks, challenge weak assumptions and propose practical improvements to strengthen the platform.

Technical areas that would be useful

You do not need all of these, but strong candidates are likely to have experience in several:

• Python 3.x
• Flask
• Django and Django ORM
• PostgreSQL or another relational database
• Redis, queues, background workers or task scheduling
• REST APIs, OpenAPI and schema-first development
• Webhooks and third-party integrations
• OAuth2, OpenID Connect, SSO, CIAM or account management systems
• Unix/Linux service management
• D-Bus or daemon-based architectures
• Docker and containerised development
• Azure, AWS or another major cloud platform
• CI/CD pipelines and automated testing
• Observability tooling, logging, metrics and alerting
• Security-conscious backend development
• SaaS, gaming, sports-tech, IoT, connected devices or customer platform experience

Experience level

We care more about proven capability than a fixed number of years.

This role is best suited to someone who has already built, maintained or significantly contributed to production Python systems. We will consider candidates earlier in their careers, but only where they can show exceptional aptitude through shipped work, serious technical projects, open-source contributions or strong commercial experience.

A computer science degree is not required, but the ability to work effectively in a real production environment is essential., We are particularly interested in examples that show how you think: debugging, security trade-offs, API design, daemon design, Python internals, or taking ownership of difficult production code.