Solution Architect

Nux Game 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.

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

• 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.

• 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 over engineering.
• 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.

• 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.

• 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.

• 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.

• 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.

• 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…