Lead/Senior Software Engineer

The Role

We’re looking for a Senior Backend Engineer with deep experience in Golang, distributed systems, and Linux environments — someone who thrives on solving complex problems, learns fast from documentation, and can work independently within a high-autonomy engineering culture.

You will build resilient, scalable backend services that interface with blockchain nodes, handle real-time data streams, and expose APIs to other microservices and clients.

Who You Are

• You’ve built and owned production-grade systems in Go.
• You’re fluent in Linux, containerization, and CI/CD pipelines.
• You understand gRPC, microservice design, and data modeling (SQL + NoSQL).
• You write clean, testable, maintainable code, and can take a feature from design → deployment → monitoring.
• You’re an independent learner who reads documentation, experiments, and ships solutions.
• You’ve worked on distributed or high-availability systems (fintech, infra, blockchain, or data platforms).
• Bonus: experience with Terraform, Ansible, or validator operations.

Why Lithium Digital

• Build real blockchain infrastructure, not just prototypes.
• Join a tight, high-performance team with ownership over architecture and execution.
• Collaborate with engineers running production validators, RPC endpoints, and microservices across ecosystems
• Grow with a company positioning itself as a top-tier blockchain infrastructure provider in Africa and globally.
• Earn above-market compensation for engineers who can think, design, and deliver independently.

Compensation: Competitive, senior-level package (₦500K+ range depending on experience and impact)

Job Type: Full-time

Pay: From ₦600,000.00 per month

Application Question(s):

• Describe a backend system or service you built or owned end-to-end.

What problem did it solve, and what were the biggest technical challenges you faced in scaling or maintaining it?

• In your own words, explain how Go handles concurrency.

Give one example of a race condition you’ve encountered (or could occur) in production, and how you would prevent it.

• Describe a time you solved a problem purely by reading documentation (not tutorials or Stack Overflow).

What was the issue, which documentation did you use, and how did you verify your understanding?

• You’re designing a service that processes thousands of blockchain transaction updates per second.

Outline your approach to ensure scalability, reliability, and message consistency.
(Keep your answer high-level—architecture, data flow, and technologies.)

• Imagine one of your Go microservices suddenly starts consuming high CPU and memory.

Walk us through your step-by-step process to diagnose and resolve the issue.

• What’s your preferred deployment pipeline for a Go microservice?

Explain how you manage configuration, secrets, and database migrations across environments.

• You’re assigned to integrate a completely new protocol (no internal expertise).

Explain how you’d approach learning, testing, and implementing it within a week using documentation alone.

• What does technical ownership mean to you, and how have you demonstrated it in previous roles?

Education:

• Undergraduate (Preferred)

Experience:

• Golang: 5 years (Preferred)