Lead Full-Stack Engineer

We are seeking a **Lead Full\-Stack Engineer** to join our distributed engineering team. IDT/NRS builds the Point of Sale platform that runs tens of thousands of independent retail stores across the United States. We are now expanding that platform into restaurants. If you like challenges where the hard part is getting it right at scale rather than getting it working once, this is that job! **Primary location \- Minsk, Belarus (hybrid)!** ### **What you will own:** * Architecture and delivery of new restaurant facing services, from data model to API to the screens merchants actually touch * The merchant facing restaurant surfaces: kitchen display and everything staff touch across the life of an order * Extending and hardening existing production services without destabilizing them * Correctness under concurrency: transactional integrity, isolation levels, idempotency, race conditions, retries, and honest tradeoffs where perfect guarantees are not available * Behavior when the connection drops. A store keeps serving whether or not the network is up, which means offline capable clients, local state, sync on reconnect, and reconciling what happened while the system was split * Queueing and asynchronous processing, background jobs, and event driven flows * Safe rollout of releases that reach tens of thousands of users * Working directly with product managers and designers to shape what gets built, not just receiving requirements and implementing them * Technical direction and code review for other engineers, including the judgment to say when a design is wrong and the credibility to make that stick ### **Required Qualifications:** * **8\+ years building full\-stack products**, including time as the senior person on the work * **Deep Node.js and TypeScript experience across the full\-stack**, with production services you designed and still stand behind * **Deep understanding of REST API design and microservices** * **Strong relational database skills, Postgres or MySQL**: schema design, indexing, query tuning, transactions, and what actually happens under load. Comfort with non relational stores such as Redis or MongoDB, and with caching and invalidation * Experience with queues and streaming, whether Kinesis, Kafka, RabbitMQ, SQS, BullMQ, or similar, including the failure modes that come with them: ordering, duplicates, replay, and consumer lag * **Front\- end skill that matches the environment:** Restaurant staff use these screens during a rush, on a terminal or a tablet, with no time to think and no tolerance for a bad interaction. **We use Vue**. **Experience with React or Angular is fine**, as long as it includes component architecture, state management, and progressive web apps * Real time interfaces built on websockets, ideally socket.io. Order flow and kitchen display depend on it * Excellent debugging. You can take an unfamiliar production failure and reason your way to root cause instead of guessing * Parts of the exi