About the role

ABOUT THE TEAM & MISSION The 42dot Vietnam subsidiary of 42dot serves as a strategic QA hub dedicated to ensuring the quality and reliability of automotive software. Working in close collaboration with 42dot HQ and global R&D centers, the entity will lead testing, validation, and quality enhancement efforts for vehicle software systems. This position is responsible for HMI quality validation for in-vehicle infotainment (IVI) systems. You will verify that the screens users see and interact with—including layouts, text, icons, screen transitions, and input responses—are implemented according to design specifications and perform consistently under real-world conditions such as multilingual environments, driving scenarios, and extended use. Rather than measuring the electrical characteristics of individual components or validating control logic, this role focuses on evaluating the quality of the complete user-facing experience—how the interface looks, behaves, and responds to users. RESPONSIBILITIES - Core Focus — HMI Quality Validation - A key responsibility of this role is to compare the implemented UI against UX guidelines and screen specifications, identify discrepancies, and assess their impact on the user experience. - Since UI defects can be difficult to resolve without clear reproduction conditions, we highly value the ability to clearly document what went wrong and how to reproduce it, supported by screenshots, videos, logs, and step-by-step reproduction procedures. - Responsibilities - Test Case Design: Develop test cases and scenarios based on screen specifications, UX guidelines, and system requirements. - Test Environment Setup: Configure IVI devices and bench environments, displays and touch equipment, vehicle-signal simulation, and validation tools. - Test Execution: Perform new-feature validation and regression testing across the verification areas described above. - Defect Reporting: Report defects with clear reproduction steps, screenshots/videos, and relevant logs such as logcat, and verify fixes. - Traceability Management: Maintain traceability between screen/system requirements and test cases using tools such as DOORS. - Reporting & HQ Communication: Prepare test reports, analyze issues, communicate results to the Korea HQ, and incorporate feedback from HQ. Some feedback may be provided in Korean. - Test Automation: Automate UI interactions using adb scripts, Appium, or UI Automator; implement screenshot comparison and OCR-based UI validation; and integrate regression automation into CI/CD pipelines. - Verification Scope - Visual Accuracy - Verify layouts, alignment, spacing, icons, image assets, colors, and typography against screen specifications. - Validate text display, including typos, missing or untranslated strings, line breaks, truncation, and overflow. - Validate multilingual UI behavior, including string replacement, missing glyphs, font fallback, and layout issues caused by different string lengths across languages. - Verify regional formats such as date/time (12/24-hour), units (km/mile, °C/°F), numbers, and currencies. - Validate day/night themes, display brightness levels, color contrast, and overall visibility. - Interaction & Responsiveness - Identify stuttering, frame drops, ghosting, flickering, and tearing during screen transitions and animations. - Validate response latency from touch input to screen response and verify touch-coordinate accuracy. - Verify multi-touch and gesture recognition, including swipe, pinch, and long press. - Validate focus navigation and highlighting for hard keys, steering-wheel controls, and rotary inputs. - Verify time to first screen after boot and proper restoration of UI and system states after wake-up. - State & Scenario Validation - Verify