Enterprise Architect

This is a foundational individual contributor hire. You will not manage a team. You will define the architecture that the team builds the canonical data models, API contracts, event schemas, and integration patterns that NuPilot's retail domain is built against. The best way to describe who we're looking for: a tenured IC who chose depth over management and has spent the better part of a decade going extremely deep into enterprise retail systems not as a consultant who blueprints and moves on but as a builder who ships software that real retailers run.

The core responsibilities for the job include the following:

Own the core retail architecture:

• Define and own the architecture for NuPilot's foundational retail primitives: Order, Inventory, Product Catalog, Pricing Engine, Fulfillment, Returns, Allocation.
• Design the data models, API contracts, and event schemas that every NuPilot module builds against.
• Establish the integration boundary layer: how NuPilot ingests data from incumbent retail systems as it replaces them.
• Define patterns for AI-native retail operations: how LLM-driven decisions plug into deterministic retail workflows without creating consistency failures.

Be the domain authority:

• Be the internal oracle for enterprise retail complexity, the person engineers and PMs go to when they hit a design decision with retail-specific constraints.
• Build NuPilot's internal retail architecture knowledge base: what the incumbents got right, what they got wrong, and how NuPilot does it differently.
• Review and shape architectural decisions across the NuPilot stack that touch retail domain logic.

Shape the long-term strategy:

• Contribute to the roadmap for how NuPilot displaces Blue Yonder, Manhattan Associates, SAP Retail, and Sterling OMS at enterprise scale.
• Define the modular replacement strategy: how a retailer adopts NuPilot incrementally without a big-bang cutover.
• Nurix AI (Nurix.ai ), Bengaluru, India Identify the design decisions that create a durable competitive moat vs. those that can be iterated on.

Requirements:

• 8+ years of hands-on architecture, not counting years spent primarily in delivery management or people management. You've designed systems, shipped them to production, watched them break, and iterated.
• Deep retail domain expertise you've worked on one or more of the core enterprise retail systems below, past the level of configuration or customization. You understand the internals.
• End-to-end ownership you've taken at least one system from architectural design through production and post-launch iteration. Not just scoped or blueprinted.
• Individual contributor identity you are currently, or have recently been, working as a Principal / Distinguished / Chief Engineer. This is a builder role.
• Distributed systems fundamentals you have practical knowledge of event-driven architecture, eventual consistency, and saga/orchestration patterns as applied to retail order management or inventory. You've used these as design tools, not just cited them.