Product Manager Connected Vehicle

Job Description

Product Manager – Connected Vehicle & Digital
Platforms

(Instrument Cluster, IoT Backend, Mobile App, OTA)

Company: Ultraviolette Automotive

1. Role Overview

Ultraviolette Automotive is building a deeply connected,
software‑defined electric motorcycle platform. The Product Manager – Connected
Vehicle & Digital Platforms will own the end‑to‑end product lifecycle of
the instrument cluster, vehicle‑to‑cloud (IoT) backend, mobile
application, and internal dashboards, ensuring a cohesive, reliable,
and scalable user experience across riders, service teams, factory operations,
and business stakeholders.

This role bridges hardware, embedded software, cloud,
mobile apps, UX, service operations, and GTM, translating real‑world EV use
cases into crisp product requirements and executable roadmaps.

2. Product Scope

• Digital
  Instrument Cluster (Android / Linux based)
  
• Vehicle
  Telemetry & IoT Platform (Cloud ingestion, APIs, analytics)
  
• Mobile
  App (Rider app)
  
• Web
  Dashboards (Service, Factory, Ops, Management)
  
• OTA
  Updates (Cluster, ECUs, firmware, configs)
  
• Diagnostics,
  Logs, Remote Commands
  

3. Responsibilities by Product Lifecycle Phase

3.1 Product Discovery & Vision

• Define
  product vision for Ultraviolette’s connected vehicle ecosystem aligned
  with brand positioning (performance‑driven, aviation‑inspired, premium
  EV).
  
• Identify
  rider, service, factory, and business pain points through field data,
  service feedback, and ride analytics.
  
• Convert
  IoT telemetry possibilities into meaningful rider features (range
  confidence, performance insights, safety alerts).
  
• Own
  long‑term roadmap for cluster, app, and backend platforms.
  

3.2 Requirements & User Stories

• Create clear, testable user stories with acceptance criteria for:
  
• Cluster
  UI/UX flows
  
• App‑to‑vehicle
  interactions
  
• Vehicle‑to‑cloud
  data pipelines
  
• Server‑side
  dashboards
  
• Explicitly
  capture edge cases:
  
• Network
  loss / intermittent connectivity
  
• Partial
  OTA failures
  
• Vehicle
  power cycles mid‑operation
  
• Region‑specific
  regulations (India / EU)
  
• Maintain
  Product Requirement Documents (PRDs) and epics across multiple teams.
  
• Act
  as a single source of truth for product behavior.
  

3.3 UX & Experience Ownership

• Own
  end‑to‑end UX consistency across:
  
• Instrument
  cluster
  
• Mobile
  app
  
• Web
  dashboards
  
• Define
  UX principles for riding scenarios (glanceability, safety, latency
  sensitivity).
  
• Work
  with design teams to validate flows using real riding and service
  scenarios.
  
• Ensure
  cluster and app behavior remains intuitive under degraded conditions.
  

3.4 IoT & Backend Product Ownership

• Define
  telemetry schemas (what data, frequency, priority).
  
• Own
  API contracts between vehicle, cloud, and apps.
  
• Prioritize
  scalability, security, and data integrity.
  
• Define
  analytics requirements for:
  
• Rider
  behavior
  
• Vehicle
  health
  
• Warranty
  and failure prediction
  

3.5 OTA & Software Lifecycle Management

• Own
  OTA strategy across cluster and ECUs:
  
• Full
  vs delta updates
  
• Rollback
  and recovery strategies
  
• Region‑specific
  releases
  
• Define
  release trains and update eligibility rules.
  
• Coordinate
  staged roll outs and monitor post‑OTA health metrics.
  
• Ensure
  OTA flows align with service and also comply with homologation constraints.
  

3.6 Factory & Manufacturing Collaboration

• Define
  factory software workflows:
  
• Vehicle
  provisioning
  
• VIN
  binding
  
• Software
  flashing and validation
  
• Ensure
  traceability of software versions to vehicle batches.
  
• Support
  factory dashboards for diagnostics and audit readiness.
  
• Collaborate
  with manufacturing teams to minimize line disruptions due to software.
  

3.7 Service & After‑Sales Collaboration

• Partner
  with service teams to define:
  
• Remote
  diagnostics
  
• Error
  code interpretation
  
• Log
  access and tooling
  
• Translate
  service pain points into backlog items.
  
• Enable
  predictive maintenance use cases using telemetry.
  
• Support
  dealer and service SOPs with digital tools.
  

3.8 Go‑To‑Market (GTM) & Launch Readiness

• Own
  feature readiness for vehicle launches and software drops.
  
• Coordinate
  with marketing on feature narratives and rider communication.
  
• Ensure
  app, backend, and cluster features are launch‑ready and region‑compliant.
  
• Support
  launch metrics tracking and post‑launch issue triage.
  

3.9 Metrics & Continuous Improvement

• Define
  KPIs for connected products:
  
• OTA
  success rate
  
• App
  engagement
  
• Cluster
  stability metrics
  
• Telemetry
  coverage
  
• Use
  data to refine roadmap and backlog prioritization.
  
• Drive
  continuous improvement culture across digital platforms.
  

4. Stakeholder Management

• Engineering:
  Embedded, Android/Linux, Cloud, Mobile
  
• Design
  & UX
  
• Service
  & After‑Sales
  
• Factory
  & Operations
  
• Quality
  & Homologation
  
• Marketing
  & GTM
  
• Leadership
  team
  

5. Skills & Experience

• 6–10+
  years in product management for embedded, IoT, or automotive systems.
  
• Strong
  understanding of:
  
• Connected
  vehicles / IoT architectures
  
• OTA
  systems
  
• Embedded
  software constraints
  
• Proven
  ability to write crisp user stories and PRDs.
  
• Experience
  working with cross‑functional hardware and software teams.
  
• Data‑driven
  mindset with strong analytical skills.
  

6. Mindset & Cultural Fit

• Systems
  thinker who understands vehicle + cloud + user holistically.
  
• Comfortable
  dealing with ambiguity and complex edge cases.
  
• Strong
  ownership mentality—bias for clarity and execution.
  
• Passion
  for EVs, performance engineering, and rider experience.