Laravel Developer (Night Shift)

Laravel Backend Engineer (PHP / Laravel / MongoDB / Redis / RabbitMQ) Working Hours: 7:00P.M-3:00A.M Drop-off provided I’m looking for a Backend Developer (Laravel) to join our team and help us level up a high-volume, real-time transactional platform built on a multi-service architecture. We’re running a system split into multiple services/APIs , with real-time updates and heavy wallet / transaction logic. It’s not a simple CRUD app – we need someone who can think, design, and make decisions, not just write code. Tech Environment You’ll Be Working In Core stack (PHP/Laravel side): Laravel (PHP) as the main backend framework MongoDB as the primary database (shared across multiple services) Redis (shared cache + per-project cache) RabbitMQ as a message broker Nginx as web server Cron + Supervisor for scheduled jobs & workers What You’ll Do Own and design backend features in Laravel from idea → architecture → implementation → deployment Work on transactional & wallet-related logic with a strong focus on data consistency and integrity Design and optimize inter-service communication (HTTP + RabbitMQ) Improve and maintain caching layers (Redis) and real-time flows (Reverb websockets / Go websockets) Collaborate on DB modeling and performance, especially in MongoDB and ClickHouse Help shape infrastructure decisions: queues, workers, scaling patterns, monitoring points, etc. ✅ What We’re Looking For 4+ years of backend experience with PHP & Laravel Strong problem-solving skills and ability to reason about complex flows Solid experience with: Laravel (queues, events, jobs, service container, etc.) MongoDB (indexes, schema design, performance basics) Redis (cache, queues, patterns like locks / rate limiting are a plus) REST APIs (design, versioning, security best practices) Good understanding of networking & infrastructure basics: Nginx, reverse proxies, load balancing concepts Background workers, cron jobs, Supervisor (or equivalents) Comfortable working with message brokers (RabbitMQ or similar) Ability to read/understand Go code is a plus (not mandatory, but nice to have) Mindset of ownership: you care about the system end-to-end, not just “your function/class” Nice to Have: Experience with ClickHouse or other analytics/OLAP databases Experience in high-traffic, real-time, or financial/transaction-heavy systems Familiarity with horizontal scaling and sharding patterns