Solution Architect

NuxGame; United States; Remoto; USD 150.000 - 210.000; Tempo pieno

Vantaggi offerti da questo lavoro

Remote & Flexible work

Time-off policy: 24 vacation days + 5/

Knowledge sharing & community

Descrizione del lavoro

NuxGame is seeking a Solution Architect to join our Global Core Team. You will design how our platform evolves, own its production behavior, and drive reliability, performance, and scalability.

You will collaborate with the CTO, product leads, and Core Solution Engineer to turn architecture into reusable libraries and standards. Ideal candidates have 7+ years in backend development, strong system design skills, and hands-on experience with Kafka, SQS, Kubernetes, and cloud-native tech.

Competenze

• 7+ years of commercial backend development, incl. architect-level experience.
• Experience designing high-load systems with microservices/monoliths and domain boundaries.
• Proficient with Kafka and SQS messaging, event-driven architectures.

Mansioni

• System Design & Architecture: define service boundaries and interactions.
• Production Health & Troubleshooting: own production behavior, analyze latency and error rates.
• Technical Initiatives & Implementation: drive idempotency, async flows, caching, and boundary redesign.
• Standards & Governance: define API rules, versioning, and adoption across teams.
• Support for Teams: unblock and collaborate with CTO and Core Solution Engineer.

Conoscenze

Backend development

System design

Distributed systems

Kafka / SQS

Laravel / Go

English communication

Formazione

Bachelor's in Computer Science

Strumenti

Kafka

SQS

Kubernetes

AWS

gRPC

Laravel

Go

MySQL/Aurora

Descrizione del lavoro

NuxGame is a dynamic IT company delivering top-tier software solutions for the iGaming industry. We empower operators of all sizes to expand into new markets, strengthen their existing brands, and achieve ambitious business goals.

We are looking for a Solution Architect to join our Global (Core) Team. This is a hands-on architecture role: you will design how our platform evolves, own its behavior in production, and drive real improvements in reliability, performance, and scalability. You will work closely with the CTO, Tech Leads of product teams, and the Core Solution Engineer, who turns architecture into reusable libraries and standards.

Tech Stack

• PHP 8, Laravel, Go, Vue 3, MySQL / Aurora, ClickHouse, Redis, Memcached, SQS, Kafka, gRPC, Kubernetes, AWS, Cloudflare, nginx.

Context

• a multi-tenant platform, a hybrid architecture (Laravel monolith + growing Go services) and an ongoing shift from HTTP to event-driven (Kafka) and gRPC communication.

Your Responsibilities

1. System Design & Architecture

• Service Boundaries: design systems, define service interactions and domain boundaries.


• Monolith vs Services: decide what stays in the monolith and what becomes a separate service, avoiding a distributed monolith and overengineering.


• Communication & Events: define event flows and rules for sync vs async communication (HTTP, Kafka, gRPC, SQS).


• Multi-tenancy: design config-driven, scalable client configuration without tenant-specific hacks in the core system.

2. Production Health & Troubleshooting

• System Health Ownership: own the behavior of the system in production, participate in incident analysis and find real root causes.


• Metrics-Driven Analysis: analyze latency (p95/p99), error rates, queue lag and retries to understand where the system breaks.


• Stability: fix bottlenecks, reduce queue lag, stabilize critical flows and reduce the number of incidents.


• Data over Opinion: validate decisions with real metrics, not assumptions.

3. Technical Initiatives & Implementation

• Initiatives: drive improvements such as an idempotency layer, reliable async flows, caching and service boundary redesign.


• Prototyping (POC): validate ideas and performance before rollout.


• Critical Code: implement complex parts, create reference implementations and help fix critical production issues.

4. Standards & Governance

• Engineering Standards: define API rules, event structure and versioning, and communication patterns.


• Adoption: introduce standards across teams without blocking delivery and measure their adoption.


• Architecture Review: review architecture-level decisions in code: service boundaries, async flows, DB usage and critical paths. The focus is \"Will this break in production?\", not code style.


• Authority: enforce architectural decisions and block system-level solutions that harm the platform.

5. Support for Teams

• Unblocking: help Team Leads with complex technical problems and resolve system-level issues.


• Collaboration: work closely with the CTO, who owns final cross-system decisions, and with the Core Solution Engineer on turning designs into shared libraries.

Approximate time split: 25-30% design, 25-30% troubleshooting & analysis, 20-25% implementation / fixes, 10-15% discussions, ~10% reviews.

This role does not include: feature delivery, sprint management or people management.

What We Expect From You

• Experience: 7+ years of commercial backend development, with at least 2 years in an architect, principal or staff-level role designing high-load systems.


• System Design: microservices, monolith and modular monolith; service boundaries; API design (contracts, versioning, backward compatibility).


• Distributed Systems: eventual consistency, idempotency, retries / DLQ, outbox and saga patterns; hands-on experience with Kafka and SQS (or RabbitMQ / NATS).


• Databases: relational DB design, indexing, transactions and isolation levels (including money operations), zero-downtime schema changes, replicas, partitioning and sharding.


• Performance & Scaling: caching strategies (Redis, CDN), bottleneck analysis, horizontal scaling and safe profiling in production.


• PHP & Go: deep knowledge of Laravel internals (queues, DI, structure) and practical experience with Go service architecture.


• Infrastructure & Observability: Kubernetes, nginx, load balancing and request flow; logs, metrics and tracing (Sentry, New Relic, Grafana or similar).


• Reliability: designing for failure, fallback strategies and safe deployment strategies (rolling, blue-green, canary).


• DDD: practical understanding of bounded contexts and domain separation.


• Trade-off Thinking: ability to balance complexity vs speed, cost vs performance, flexibility vs simplicity.


• Communication: ability to align multiple teams around technical decisions and explain them to both engineers and business.


• English: B1 (Intermediate) or higher.

It Will Be a Plus

• Domain: experience in iGaming, fintech or payments.


• Multi-tenant SaaS: experience designing platforms for many clients with tenant isolation.


• Analytics: experience with ClickHouse or other analytical databases and OLTP to analytics data pipelines.


• Edge & Cloud: experience with Cloudflare (WAF, CDN, DDoS protection) and AWS architecture.


• Migrations: experience migrating from a monolith to services or introducing event-driven architecture.


• Frontend Architecture: understanding of SPA to SSR migrations and micro frontend trade-offs.


• AI-Assisted Workflow: experience with AI coding tools. We welcome a smart approach to AI to streamline complex tasks, from architectural design to documentation, development, and code refactoring.

What we offer

• Remote & Flexible: work from anywhere. Our core hours are 09:00/10:00 to 17:00/18:00 (Kyiv time), Mon-Fri.


• Financial Stability: timely payment for compensation for services.


• Personal Equipment Policy: equipment is provided for use to ensure comfortable and efficient work.


• Knowledge Sharing: we regularly gather to discuss new trends, share insights, and elevate one another.


• Community: at NuxGame, you will work in a team of like-minded people who are ready to support, inspire, and tackle complex challenges together.


• Creative Freedom: we encourage initiative. With us, you have the freedom of professional expression and the space to implement your ideas.


• Time-off Policy: 24 vacation days per year + 5 sick days (without medical confirmation).


• Atmosphere: a friendly environment focused on results and mutual respect, free from unnecessary bureaucracy and pressure.