Director, Software Engineering: Retail Platform Delivery (ELERA)

Toshiba Global Commerce Solutions; Cincinnati (OH); On-site; USD 180,000 - 260,000; Full time

Job summary

Toshiba Global Commerce Solutions is seeking a Director of Software Engineering: Retail Platform Delivery to own end-to-end delivery across global retail partners, including Fortune 100 accounts. The role unifies Development, Test, and Professional Services Engineering into one accountable function.

You will lead AI-native development workflows, set telemetry, and ensure production reliability, performance, and cost targets while shaping architecture and implementation across POS, payments, and

Qualifications

• Experience leading cross-functional software delivery for large-scale retail platforms.
• Ability to define success criteria, rollout strategy, and risk posture for customer programs.
• Strong focus on software quality, release governance, and telemetry.

Responsibilities

• Own end-to-end delivery of the retail platform across global partners.
• Define and enforce DORA metrics, deployment frequency, MTTR, and change failure rate.
• Lead customer-facing engineering authority for strategic accounts.

Skills

AI-assisted engineering

PR review

Job description

• AI-assisted engineering: requirement decomposition, design-to-code, test generation, refactoring at scale, PR review

Must be located near or within the area of Cincinnati, Ohio.

Toshiba Global Commerce Solutions is seeking a Director, Software Engineering: Retail Platform Delivery (ELERA) to own end-to-end delivery of the ELERA retail platform across our strategic global retail partners, including Fortune 100 grocery, warehouse club, and general merchandise accounts.

This role collapses Development, Test, and Professional Services Engineering into a single accountable function and operates as the customer-facing engineering authority for strategic programs. You own what ships, how it scales, how it recovers, and how quickly the team learns.

This role runs on Toshiba’s agentic AI development ecosystem as the default way of working, not a side experiment. Agents participate in requirement decomposition, code generation, test authoring, PR review, defect triage, and release scoring. You are expected to measure and compound that leverage.

What You Own

• Delivery velocity AND production reliability (DORA metrics with published targets)
• Unified engineering and quality accountability in one org
• Customer-facing technical authority for strategic retail accounts
• AI-native development workflows that compound team output quarter over quarter
• Production outcomes: what ships, how it performs, how it recovers, what it costs to run

This is not an engineering-only or QA-only role. You own the outcome, the telemetry that proves it, and the workflows that compound it.

Key Responsibilities

Customer-Facing Engineering Leadership

• Primary engineering authority for customer programs spanning POS, payments, loyalty, and store systems
• Partner with customer leaders to define success criteria, operational acceptance, rollout strategy, and risk posture
• Translate real-world retail workflows into architecture decisions, API contracts, and system behavior
• Maintain architecture decision records (ADRs) and a visible technical debt register tied to delivery plans

End-to-End Delivery Ownership (DORA-Native)

Own The Four DORA Metrics As Published, Measurable Targets

• Deployment Frequency: on-demand for services, scheduled-safe for store edge
• Lead Time for Changes: under 24 hours for services
• Change Failure Rate: under 10% trending down
• MTTR: under 1 hour for customer-impacting incidents
• AI-built feature branches with pre-merge release testing: agents build the full feature on an isolated branch; release-grade testing (functional, performance, security, integration) runs on that branch and must pass before merge. Main stays releasable at all times.
• Progressive delivery is mandatory: feature flags, canary, blue/green, shadow traffic. Decouple deploy from release.
• Zero scheduled-downtime windows for cloud services; store edge deploys are non-disruptive to live lanes

Unified Engineering + Quality Model

• Test-Driven Development is the baseline. Tests exist before code. No exceptions for new code paths.
• Quality gates block merges: coverage thresholds, mutation score, static analysis, SAST, dependency and license scanning, SBOM generation
• Contract testing (consumer-driven) between every service boundary; OpenAPI and AsyncAPI versioned and governed
• Chaos engineering in staging, quarterly game days, production-like load testing ahead of peak retail events
• Shift-right validation: synthetic monitoring, canary analysis, error budget enforcement
• Own metrics: defect leakage, change failure rate, cycle time, escape rate, production incident rate

AI-Native Development (Agentic Delivery