Lead Full-Stack Engineer (Node.js & Vue)

🏢 ОфисSeniorПолная занятость

Зарплата не указана

Вилки нет, про деньги придётся договариваться с нуля.

Нажмите на сигнал, чтобы увидеть, на чём он основан

Наша компания

IDT Corporation is a global communications company founded in 1990 and headquartered in Newark, New Jersey. We are industry leaders in prepaid communication and payment services and one of the largest international voice carriers. We are listed on the NYSE, employ over 1800 people across 20 countries, and have over $1.5 billion in revenues. We are not ”another big IT corporation”— we encourage and support in-house entrepreneurs in developing their ideas into business actions. National Retail Solutions (NRS) is a leading provider of point-of-sale, payment, and digital solutions to tens of thousands of independent retailers across the United States and Canada. NRS is now expanding into a completely new vertical: restaurant technology. We are building a brand-new Restaurant POS platform, a modern and highly capable system designed specifically for restaurant operations. This is one of the most significant product expansions in NRS history and will open a major new market for the company. This is a real opportunity to help build something new and important. It seems like you are interested if you are here, so let’s chat!

Чем предстоит заниматься

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

Наши требования

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: our team 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 existing platform are PHP

AI first. You use AI tooling as a core part of how you engineer: mapping an unfamiliar codebase in hours instead of weeks, pressure testing your own designs, moving faster without lowering the bar

You apply it across the whole lifecycle: shaping a design before any code exists, writing and refactoring, reviewing your own work, as well as automated PR reviews

You jump in. Handed a large, complex, unfamiliar repository, your instinct is to open it and start reading. Complexity and sensitivity are reasons to be careful, not reasons to wait for someone else

You build services that stay maintainable. Clear boundaries, readable code, tests that earn their keep, observability that makes production legible. The next engineer should be able to operate what you built without a tour guide

You think about the person on the other side. During a rush, a confusing screen or one extra tap is not a cosmetic problem. It is a slower line and a worse night for the staff

You go the extra mile. You follow a problem to its actual end, including the parts nobody assigned to you. You take pride in the work and you care how it lands for the merchant on the other side of the screen

Мы предлагаем

A real chance to help build a major new product for the U.S. market

Collaboration with strong engineering teams across Minsk, Israel, and the U.S

Opportunities to grow as the team scales

Hybrid/on-site/remote in Minsk work opportunity!

Stable job with long-term growth perspective

Competitive salary with annual performance review

Top-tier hardware to support your productivity

Compensation for professional training, seminars, and conferences

Referral program – get rewarded for helping us grow the team with talented people

Sports activities reimbursement

Medical insurance

26 vacation days & 5 fully covered sick days without sick leave required per year

Superb corporate English lessons

Дополнительно

Experience deploying services that scale horizontally, tolerate a failed instance or a slow dependency, and automatically add or shed capacity

Comfortable on Linux, and fluent with Git and CI and CD workflows

Excellent written and spoken English

You will be in daily conversation with teams in the United States and Israel, and will often be the person explaining a technical decision to people who did not attend the design discussion