<\/div>
1. Role Overview<\/b>
<\/p>
Ultraviolette Automotive is building a deeply connected,\nsoftware\u2011defined electric motorcycle platform. The Product Manager \u2013 Connected\nVehicle & Digital Platforms will own the end\u2011to\u2011end product lifecycle of\nthe instrument cluster<\/b>, vehicle\u2011to\u2011cloud (IoT) backend<\/b>, mobile\napplication<\/b>, and internal dashboards<\/b>, ensuring a cohesive, reliable,\nand scalable user experience across riders, service teams, factory operations,\nand business stakeholders.
<\/p>
This role bridges hardware, embedded software, cloud,\nmobile apps, UX, service operations, and GTM<\/b>, translating real\u2011world EV use\ncases into crisp product requirements and executable roadmaps.
<\/p>
<\/div>
2. Product Scope<\/b>
<\/p>- Digital\n Instrument Cluster (Android / Linux based)
<\/li> - Vehicle\n Telemetry & IoT Platform (Cloud ingestion, APIs, analytics)
<\/li> - Mobile\n App (Rider app)
<\/li> - Web\n Dashboards (Service, Factory, Ops, Management)
<\/li> - OTA\n Updates (Cluster, ECUs, firmware, configs)
<\/li> - Diagnostics,\n Logs, Remote Commands
<\/li><\/ul>
<\/div>
3. Responsibilities by Product Lifecycle Phase<\/b>
<\/p>
<\/div>
3.1 Product Discovery & Vision<\/b>
<\/p>- Define\n product vision for Ultraviolette\u2019s connected vehicle ecosystem aligned\n with brand positioning (performance\u2011driven, aviation\u2011inspired, premium\n EV).
<\/li> - Identify\n rider, service, factory, and business pain points through field data,\n service feedback, and ride analytics.
<\/li> - Convert\n IoT telemetry possibilities into meaningful rider features (range\n confidence, performance insights, safety alerts).
<\/li> - Own\n long\u2011term roadmap for cluster, app, and backend platforms.
<\/li><\/ul>
<\/div>
3.2 Requirements & User Stories<\/b>
<\/p>- Create clear, testable user stories<\/b> with acceptance criteria for:
<\/li>- Cluster\n UI/UX flows
<\/li> - App\u2011to\u2011vehicle\n interactions
<\/li> - Vehicle\u2011to\u2011cloud\n data pipelines
<\/li> - Server\u2011side\n dashboards
<\/li><\/ul> - Explicitly\n capture edge cases<\/b>:
<\/li>- Network\n loss / intermittent connectivity
<\/li> - Partial\n OTA failures
<\/li> - Vehicle\n power cycles mid\u2011operation
<\/li> - Region\u2011specific\n regulations (India / EU)
<\/li><\/ul> - Maintain\n Product Requirement Documents (PRDs) and epics across multiple teams.
<\/li> - Act\n as a single source of truth for product behavior.
<\/li><\/ul>
<\/div>
3.3 UX & Experience Ownership<\/b>
<\/p>- Own\n end\u2011to\u2011end UX consistency across:
<\/li>- Instrument\n cluster
<\/li> - Mobile\n app
<\/li> - Web\n dashboards
<\/li><\/ul> - Define\n UX principles for riding scenarios (glanceability, safety, latency\n sensitivity).
<\/li> - Work\n with design teams to validate flows using real riding and service\n scenarios.
<\/li> - Ensure\n cluster and app behavior remains intuitive under degraded conditions.
<\/li><\/ul>
<\/div>
3.4 IoT & Backend Product Ownership<\/b>
<\/p>- Define\n telemetry schemas (what data, frequency, priority).
<\/li> - Own\n API contracts between vehicle, cloud, and apps.
<\/li> - Prioritize\n scalability, security, and data integrity.
<\/li> - Define\n analytics requirements for:
<\/li>- Rider\n behavior
<\/li> - Vehicle\n health
<\/li> - Warranty\n and failure prediction
<\/li><\/ul><\/ul>
<\/div>
3.5 OTA & Software Lifecycle Management<\/b>
<\/p>- Own\n OTA strategy across cluster and ECUs:
<\/li>- Full\n vs delta updates
<\/li> - Rollback\n and recovery strategies
<\/li> - Region\u2011specific\n releases
<\/li><\/ul> - Define\n release trains and update eligibility rules.
<\/li> - Coordinate\n staged roll outs and monitor post\u2011OTA health metrics.
<\/li> - Ensure\n OTA flows align with service and also comply with homologation constraints.
<\/li><\/ul>
<\/div>
3.6 Factory & Manufacturing Collaboration<\/b>
<\/p>- Define\n factory software workflows:
<\/li>- Vehicle\n provisioning
<\/li> - VIN\n binding
<\/li> - Software\n flashing and validation
<\/li><\/ul> - Ensure\n traceability of software versions to vehicle batches.
<\/li> - Support\n factory dashboards for diagnostics and audit readiness.
<\/li> - Collaborate\n with manufacturing teams to minimize line disruptions due to software.
<\/li><\/ul>
<\/div>
3.7 Service & After\u2011Sales Collaboration<\/b>
<\/p>- Partner\n with service teams to define:
<\/li>- Remote\n diagnostics
<\/li> - Error\n code interpretation
<\/li> - Log\n access and tooling
<\/li><\/ul> - Translate\n service pain points into backlog items.
<\/li> - Enable\n predictive maintenance use cases using telemetry.
<\/li> - Support\n dealer and service SOPs with digital tools.
<\/li><\/ul>
<\/div>
3.8 Go\u2011To\u2011Market (GTM) & Launch Readiness<\/b>
<\/p>- Own\n feature readiness for vehicle launches and software drops.
<\/li> - Coordinate\n with marketing on feature narratives and rider communication.
<\/li> - Ensure\n app, backend, and cluster features are launch\u2011ready and region\u2011compliant.
<\/li> - Support\n launch metrics tracking and post\u2011launch issue triage.
<\/li><\/ul>
<\/div>
3.9 Metrics & Continuous Improvement<\/b>
<\/p>- Define\n KPIs for connected products:
<\/li>- OTA\n success rate
<\/li> - App\n engagement
<\/li> - Cluster\n stability metrics
<\/li> - Telemetry\n coverage
<\/li><\/ul> - Use\n data to refine roadmap and backlog prioritization.
<\/li> - Drive\n continuous improvement culture across digital platforms.
<\/li><\/ul>
<\/div>
4. Stakeholder Management<\/b>
<\/p>- Engineering:\n Embedded, Android/Linux, Cloud, Mobile
<\/li> - Design\n & UX
<\/li> - Service\n & After\u2011Sales
<\/li> - Factory\n & Operations
<\/li> - Quality\n & Homologation
<\/li> - Marketing\n & GTM
<\/li> - Leadership\n team
<\/li><\/ul>
<\/div>
5. Skills & Experience<\/b>
<\/p>- 6\u201310+\n years in product management for embedded, IoT, or automotive systems.
<\/li> - Strong\n understanding of:
<\/li>- Connected\n vehicles / IoT architectures
<\/li> - OTA\n systems
<\/li> - Embedded\n software constraints
<\/li><\/ul> - Proven\n ability to write crisp user stories and PRDs.
<\/li> - Experience\n working with cross\u2011functional hardware and software teams.
<\/li> - Data\u2011driven\n mindset with strong analytical skills.
<\/li><\/ul>
<\/div>
6. Mindset & Cultural Fit<\/b>
<\/p>- Systems\n thinker who understands vehicle + cloud + user holistically.
<\/li> - Comfortable\n dealing with ambiguity and complex edge cases.
<\/li> - Strong\n ownership mentality\u2014bias for clarity and execution.
<\/li> - Passion\n for EVs, performance engineering, and rider experience.
<\/li><\/ul>
<\/div><\/span>
