Lead Backend Engineer Node.js / DevOps / AI

Full time
Remote/UAE
01. ABOUT THE COMPANY
Dizzaract is a product-driven company operating at the intersection of gaming, digital platforms, and AI. We build and scale multiple products, including FAR Labs & Gamed - each exploring a different space, yet united by a shared approach: moving fast, staying curious, and focusing on things that people actually use. We operate as a collaborative, non-hierarchical team where ideas are valued based on their impact, not their origin, and where AI is embedded across everything we build, from infrastructure to product decisions.
02. ABOUT THE ROLE
We're looking for aLead Backend Engineer to take technical ownership of the backend and lead the backend engineering team. This is ahands-on engineering role. You'll still spend a significant part of your time designing systems, writing and reviewing code, while also setting engineering standards, helping the team make technical decisions, and driving delivery. You'll work closely with the Tech Lead, Frontend, Game and Product teams on systems serving hundreds of thousands of users.
03. RESPONSIBILITIES

Own backend architecture and technical decisions.
Design, build and maintain backend services using TypeScript, Node.js and NestJS.
Lead the backend team day-to-day and help engineers unblock complex technical problems.
Review code and maintain strong engineering and quality standards.
Design systems for high availability, performance and scale.
Own database architecture and optimisation across PostgreSQL, Redis and MongoDB.
Build integrations with internal services, external APIs, payment and gaming platforms.
Improve system reliability, observability and fault tolerance.
Work with the Tech Lead on CI/CD, deployments and infrastructure.
Support the integration of AI/LLM capabilities into production products.
Contribute directly to planning, estimation and technical direction.

04. REQUIREMENTS

5+ years of backend engineering experience, with strong hands‑on coding skills
Strong production experience with TypeScript and Node.js.
Experience with NestJS, Express or Fastify.
Previous experience leading backend engineers and owning technical delivery.
Strong understanding of system design, distributed systems and event‑driven architecture.
Experience with PostgreSQL, MongoDB and Redis.
Experience with message brokers/queues such as Kafka, RabbitMQ, SQS or BullMQ.
Good understanding of Docker and CI/CD.
Experience designing and operating scalable production systems.
Strong ownership and ability to work in a fast-moving environment.

05. NICE TO HAVE

Experience building high-load or real-time systems.
Kubernetes and cloud infrastructure experience.
Infrastructure as Code experience with Terraform or Pulumi.
Experience with AWS, GCP or Azure.
AI/LLM engineering experience - LLM APIs, RAG, embeddings, vector databases or agents.
Gaming or player-facing product experience.

07. WHAT WE OFFER

Real technical ownership and influence over architecture.
A Lead role where youstill build, rather than move into pure management.
High-load and technically challenging products.
Exposure to AI/LLM development across our ecosystem.
Fast decision-making and low bureaucracy.
Competitive salary + performance-based incentives.
24 days annual leave + public holidays.
Health insurance.
Modern office at Yas Creative Hub, Abu Dhabi.
•

Back to blog

Other Jobs To Apply

No other job posts for this day.

Common Interview Questions And Answers

1. HOW DO YOU PLAN YOUR DAY?

This is what this question poses: When do you focus and start working seriously? What are the hours you work optimally? Are you a night owl? A morning bird? Remote teams can be made up of people working on different shifts and around the world, so you won't necessarily be stuck in the 9-5 schedule if it's not for you...

2. HOW DO YOU USE THE DIFFERENT COMMUNICATION TOOLS IN DIFFERENT SITUATIONS?

When you're working on a remote team, there's no way to chat in the hallway between meetings or catch up on the latest project during an office carpool. Therefore, virtual communication will be absolutely essential to get your work done...

3. WHAT IS "WORKING REMOTE" REALLY FOR YOU?

Many people want to work remotely because of the flexibility it allows. You can work anywhere and at any time of the day...

4. WHAT DO YOU NEED IN YOUR PHYSICAL WORKSPACE TO SUCCEED IN YOUR WORK?

With this question, companies are looking to see what equipment they may need to provide you with and to verify how aware you are of what remote working could mean for you physically and logistically...

5. HOW DO YOU PROCESS INFORMATION?

Several years ago, I was working in a team to plan a big event. My supervisor made us all work as a team before the big day. One of our activities has been to find out how each of us processes information...

6. HOW DO YOU MANAGE THE CALENDAR AND THE PROGRAM? WHICH APPLICATIONS / SYSTEM DO YOU USE?

Or you may receive even more specific questions, such as: What's on your calendar? Do you plan blocks of time to do certain types of work? Do you have an open calendar that everyone can see?...

7. HOW DO YOU ORGANIZE FILES, LINKS, AND TABS ON YOUR COMPUTER?

Just like your schedule, how you track files and other information is very important. After all, everything is digital!...

8. HOW TO PRIORITIZE WORK?

The day I watched Marie Forleo's film separating the important from the urgent, my life changed. Not all remote jobs start fast, but most of them are...

9. HOW DO YOU PREPARE FOR A MEETING AND PREPARE A MEETING? WHAT DO YOU SEE HAPPENING DURING THE MEETING?

Just as communication is essential when working remotely, so is organization. Because you won't have those opportunities in the elevator or a casual conversation in the lunchroom, you should take advantage of the little time you have in a video or phone conference...

10. HOW DO YOU USE TECHNOLOGY ON A DAILY BASIS, IN YOUR WORK AND FOR YOUR PLEASURE?

This is a great question because it shows your comfort level with technology, which is very important for a remote worker because you will be working with technology over time...