2

Principal Backend Engineer (.NET / C#)

247Bet
Lagos, Lagos State, Nigeria 🇳🇬 Nigeria
Live
Full Time
Senior
Technology
Posted 12 days ago (24 Aug 2026) Deadline: 20 Feb 2027 Updated 10 days ago

Job Description

The Principal Backend Engineer will lead the design and implementation of the core backend platform for 247Bet’s betting and gaming services. As the most senior individual contributor, the engineer will own architecture across .NET, PostgreSQL, Redis, Kafka and AWS, ensuring high‑availability, data consistency and fault‑tolerant processing of financial transactions. The role also includes setting technical standards, mentoring senior engineers and collaborating with founders on the product roadmap.

Qualifications & Requirements

  • • 8+ years of backend engineering experience, with several years at staff or principal level
  • • Deep, current expertise in C#/.NET and the surrounding ecosystem
  • • Proven track record architecting distributed, event‑driven systems handling monetary transactions
  • • Strong understanding of data consistency, transactions, idempotency and exactly‑once processing
  • • Production experience with PostgreSQL, Redis, Kafka and AWS
  • Kubernetes/EKS preferred
  • • Ability to lead through influence via design docs, code reviews and mentorship
  • • Sound judgement on technical trade‑offs and ability to balance rigor with shipping speed
  • • Excellent written and verbal communication for both technical and non‑technical audiences

Required Skills

Responsibilities

  • • Own the backend architecture across .NET 8+, PostgreSQL, Redis, Kafka and AWS/EKS
  • • Design critical systems such as the double‑entry wallet ledger, bet placement, settlement, cash‑out and payment flows
  • • Establish standards for event‑driven design, idempotency, consistency and failure handling across services
  • • Lead the most complex technical work, including high‑risk integrations and performance optimisation
  • • Conduct architecture and design reviews and mentor senior engineers to improve system design
  • • Define non‑functional requirements such as latency budgets, availability targets and capacity plans for peak events
  • • Drive observability, incident‑response practices and post‑mortem culture for backend services
  • • Evaluate build‑vs‑buy decisions and assess third‑party providers for trading feeds, payments and fraud solutions
  • • Collaborate directly with the founders and Head of Engineering on the technical roadmap