Join the Charge. Create the Future.
At Ultraviolette, we're more than a company—we're a movement. A movement that's pushing the boundaries of what's possible in electric mobility. From engineering India's Fastest Motorcycle to designing The World's Most Advanced Electric Scooter, we thrive on innovation, audacity, and the relentless pursuit of performance.
We're a diverse team of trailblazers, engineers, designers, creatives and visionaries—united by a shared obsession: to craft machines that are not only sustainable but exhilarating. Here, radical design meets intelligent technology, and every line of code or bolt of hardware brings us closer to reshaping the future of mobility.
Our mission is to accelerate the evolution of mobility across the globe - and we're just getting started.
If you're driven by purpose, inspired by possibility, and ready to build something that truly matters, Ultraviolette is the place where your ambition becomes impact. Let's create the future—together.
1. Role Overview
Ultraviolette Automotive is building a software-defined, Android-based digital instrument cluster for high‑performance electric motorcycles. The Test Automation Lead – Android Cluster will own the test automation strategy, tooling, and execution to ensure stability, performance, safety, and release confidence of the cluster software.
This role is focused on system-level Android testing on real hardware, covering UI behavior, Android framework services, vehicle signal interactions, OTA updates, and long‑run reliability.
2. Product Scope
- Android-based Instrument Cluster (AOSP / Android Automotive)
- Cluster UI, animations, alerts, and critical ride screens
- Android system services and background processes
- Vehicle signal integration (CAN, ECUs)
- OTA updates (A/B updates, rollback, recovery)
3. Key Responsibilities
3.1 Automation Strategy & Ownership
- Define and own the end-to-end automation strategy for the Android cluster
- Decide what must be automated vs manual based on safety, risk, and stability
- Define automation coverage targets and release gating criteria
- Ensure automation is designed for embedded hardware, not emulators alone
3.2 Automation Framework Development
- Design and maintain automation frameworks for:
- Cluster UI screens, alerts, and transitions
- Android system services and background components
- Boot, suspend, resume, and reboot scenarios
- Enable hardware‑in‑the‑loop (HIL) based automation for realistic testing
3.3 Android System & Stability Testing
- Automate validation of:
- Cold boot and warm boot performance
- ANRs, crashes, watchdog resets
- Memory leaks, CPU/GPU load, and thermal limits
- Measure and track application launch time (cold / warm start)
- Validate touch response latency and input-to-render timing
- Work closely with Android developers to improve testability and observability
3.4 Power, Performance & Connectivity Metrics
- Define and automate power measurement and tracking for the cluster
- Measure current consumption across key states:
- Boot, idle, ride, standby, sleep
- Track performance KPIs:
- Touch response latency
- UI frame rate and jank
- App launch time
- Automate validation of connectivity performance:
- Bluetooth pairing, reconnect, latency, and stability
- Wi-Fi scan, connect, throughput, and recovery
- Network loss and recovery scenarios
3.5 Vehicle Signal & State Validation
- Automate cluster behavior against:
- CAN signals and ECU inputs
- Vehicle state transitions (ride, park, charge, fault)
- Fault injection and degraded‑mode scenarios
- Ensure deterministic and safe behavior for safety‑critical displays
3.6 OTA & Release Validation
- Automate OTA validation for:
- A/B updates and slot switching
- Interrupted updates (power or network loss)
- Rollback and recovery scenarios
- Validate post‑OTA stability, data integrity, and performance
3.7 Service & Field Issue Support
- Convert field and service issues into regression automation tests
- Enable reproducible failure validation on benches
- Support root‑cause analysis using logs, traces, and automation data
3.8 CI/CD & Reporting
- Integrate automation into CI pipelines (Jenkins / GitLab CI)
- Enable unattended test execution on hardware benches
- Publish clear, actionable reports for engineering and leadership
- Track regressions and prevent recurrence
4. Test Tools & Automation Stack
Android UI & App Automation
- UI Automator – Primary framework for system‑level UI and cluster screens
- Espresso – App‑level automation for system applications
- Monkey / MonkeyRunner – Input stress and endurance testing
Android System & Compliance
- CTS (Compatibility Test Suite)
- VTS (Vendor Test Suite)
- GTS (Google Test Suite)
- Android Test Station (ATS) for orchestrating CTS/VTS on hardware
Performance & Stability
- Perfetto / Systrace – System tracing and latency analysis
- Simpleperf – CPU profiling
- dumpsys (gfxinfo, meminfo, activity, power)
- logcat, tombstones, ANR traces
Stress, Reliability & Power Testing
- Monkey (long‑run execution)
- stress‑ng (where supported)
- Automated reboot, suspend–resume, and power‑cycle loops
OTA & Update Validation
- A/B OTA testing tools
- adb sideload and OTA simulation scripts
- update_engine logs, rollback and recovery validation
Connectivity & Network Testing
- adb network tools
- tc (traffic control) for latency and packet loss
- iptables for network drop scenarios
- Modem AT‑command tools
CI & Orchestration
- Jenkins / GitLab CI
- Custom Python‑based test runners
- Automated reporting (Allure / HTML dashboards)
5. Skills & Experience
- 7–12+ years in test automation for Android or embedded systems
- Strong experience testing Android AOSP / Android Automotive at system level
- Excellent coding skills in Python (mandatory)
- Working knowledge of Java / Kotlin for Android integration
- Understanding of vehicle signals, CAN, diagnostics, and ECU behavior
- Strong debugging skills using logs, traces, and performance tools
- Excellent coding skills in Python (mandatory) for automation frameworks, HIL control, and CI integration
- Hands-on experience with: UI Automator (mandatory) for system-level UI testing , Espresso for system/app-level validation , Monkey / MonkeyRunner for stress and endurance testing
- working Knowledge of YOCTO is huge plus
