Staff UI Engineer - Scenario Manager

GreyOrange · Bangalore

Source and collection record

Last observed by our collector: 8 October 2026 at 11:28 pm IST. This is not a manual review or a confirmation from the employer.

Employer requisition: 10631

Job type and experience labels are automated discovery categories. The employer determines eligibility. Original experience wording was not retained separately; check the current employer page.

How sourcing and classification work · Report a discrepancy

Your application evidence checklist

Mark the statements you can support after reading the employer source. This checklist stays on this page; it does not score your eligibility or submit an application.

Attendance and availability: I checked the employer page for work location, office attendance, start date and duration.Current requisition: I checked the current employer requisition and its application requirements.

0 of 2 checks marked. Keep unresolved requirements as questions for the employer.

Collected role description

Own the UI that lets Solution Engineers and customers manage, compare, and track scenarios across the life of an implementation from the multiple options explored pre-sales through the one that eventually ships. What You'll Do Own the Scenario Manager UI: scenario list, version history, side-by-side comparison views, and the "promote to active" workflow. Design comparison views that make it easy to see what changed between two scenarios - BOM differences, layout differences, sizing assumptions. Set UI architecture direction for how scenario data, which spans MFD, Sizer, Layout, and DES/Emulator outputs, is presented coherently in one place. Partner with the Scenario Manager backend engineer on the API contract for scenario versioning and comparison. Mentor engineers building on top of the Scenario Manager surface. What We're Looking For 8+ years building complex, data-dense UI, ideally involving versioning, comparison, or diff views. Strong React/TypeScript fundamentals and experience architecting UI for large, multi-source datasets. Experience designing UI for a product with many interdependent data sources, not just a single API's worth of data. A track record of setting UI architecture direction for a team, not just building features solo. Nice to Have Experience with diff/comparison UI specifically code review tools, design version history, document comparison. Familiarity with warehouse automation or engineering/CAD tools.

Collected experience requirement

8-15 years