Front-End (UI) Platform Engineer-Retail Point of Sale Systems

Note: Toshiba Global Commerce Solutions will not be providing visa sponsorship for this position now or in the future. Therefore, in order to be considered for this position, you must have the ability to work in the United States without a need for current or future visa sponsorship.
Must be local to Raleigh/Durham, NC Area or Bentonville, AR Area. This is a hybrid role at least 3 days a week in person.
Toshiba Global Commerce Solutions is seeking a Front-End (UI) Platform Engineer-Retail Point of Sale Systems to own and evolve the ELERA point-of-sale client – the Vue 3 and TypeScript application framework behind our fixed-lane, self-checkout, kiosk, specialty, associate-mobile, and customer-display experiences. This is a successor role on a defined architect track: the person hired will be trained to become the architect for the ELERA POS client.
This is a platform role, not a feature role. Most of the work is not screens. It is the framework other teams build their screens out of: a dependency-injection and plugin system that retailers and partners extend through, a configuration merge chain that resolves customer overrides, a device layer that talks to lane hardware, a legacy Dojo application that must keep shipping beside the modern client, and the build train that releases all of it together.
The role requires experience building solutions on Vue.js and Java enterprise technologies with a focus on complex browser-side functionality. The ideal candidate will excel in our fast-paced, collaborative, customer-first environment, and is looking for a path into architecture rather than a larger backlog.
Responsibilities:
Design, develop, and test/debug client UI and client framework code in Vue 3 and TypeScript, and mentor the team doing the same
Design with other developers in mind – both the internal team and the retailer, partner, and services engineers who extend the platform from outside
Own and extend the client extensibility model: dependency injection and decorator-based registration, plugin loading, UI slot injection, and the base/TGCS/partner/customer configuration merge chain
Maintain backward compatibility for plugins and customizations built against earlier framework versions
Publish versioned shared packages consumed by other teams, with real semantic-versioning and deprecation discipline
Keep two UI generations shippable at once, migrating the legacy Dojo layer incrementally rather than by flag day
Extend the device integration layer – scanners, scales, printers, payment terminals, cash recyclers, customer display – including the mock device harness that lets the full client run on a laptop
Maintain the client release train: hybrid Maven/npm builds, monorepo publishing, Jenkins multi-branch pipelines across the framework dependency chain, and constrained or air-gapped customer environments
Own client-side quality: unit and component tests under a coverage gate, and a browser-automated BDD suite that gates the build
Write and defend architecture decision records, component analyses, and solution designs; represent the client stack at the Architecture Review Board
Maintain the client Self-Enablement Guide and generated extension catalogs, and serve as a technical interface to key technology partners