Define the function
Translate system and customer needs into clear behavior, interfaces, and aligned requirements.
FUNCTION OWNER · VEHICLE ACCESS & SENSING
Turning access and sensing concepts into clear vehicle functions.
I bring embedded engineering depth to function roadmaps, system integration, and customer–supplier alignment across Digital Key and in-cabin sensing.
10+Years in automotive software
C++ → SystemsEngineering depth to function ownership
ASPICE L2Process-led cross-team delivery
Access should feel invisible.
The engineering behind it cannot be.
My role is to hold the complete function together: the intended vehicle experience, the technical dependencies beneath it, and the teams responsible for making it real.
Across UWB, BLE, NFC, Digital Key, and in-cabin sensing, I connect requirements, architecture, software, integration, validation, suppliers, and stakeholders throughout the feature lifecycle.
Connect the system
Manage dependencies across access technologies, sensing functions, and vehicle integration.
Steer delivery
Align development, test, suppliers, and stakeholders around priorities, risks, and milestones.
Protect quality
Maintain ASPICE-aligned traceability, review discipline, and delivery readiness.
02 · SYSTEM VIEW
One journey.
One journey.
Multiple technologies.
This is a simplified view of the vehicle access experience—not a product specification. It shows the behavior and handoffs a Function Owner must keep coherent.
Approach
Discovery and proximity awareness begin the experience.
BLEWelcome
Vehicle behavior responds to the authorized user.
BLE · UWBAccess
Presence and access intent are coordinated securely.
UWB · NFCAuthorization
Entry transitions into an in-vehicle driving context.
UWB · Digital KeyDeparture
The connected journey closes as the user moves away.
BLE · UWBDigital Key ecosystem
Coordinating device discovery, proximity, authorization, fallback paths, and vehicle response across UWB, BLE, and NFC.
In-cabin intelligence
Driving sensing functions through requirements, interfaces, integration, validation, and stakeholder alignment.
03 · SELECTED WORK
Evidence from the work.
Selected engagements that shaped how I approach architecture, integration, quality, and ownership today.
01
VOLKSWAGEN MIB3 · LEAD DEVELOPER
Multilingual input on embedded hardware
How do you make Chinese, Japanese, and Korean input feel immediate inside a constrained automotive system?
THE MOVE
Designed a modular C++ integration layer using reusable patterns, separated supplier linguistics from application logic, and built validation around API and transformation behavior.
THE RESULT
A production-grade IME supporting Pinyin, Romaji, and Hangul workflows for Volkswagen vehicles in Asian markets.
02
AR-CORE · FUNCTION OWNER
Creating delivery confidence across a lifecycle
THE MOVE
Aligned project management, requirements, development, and testing while leading reviews, risk tracking, and process discipline.
THE RESULT
ASPICE Level 2 with more consistent cross-team execution and quality records.
03
VOLKSWAGEN CNS · DEVELOPER
Making security understandable in the HMI
THE MOVE
Designed a real-time password scoring algorithm and translated complexity checks into clear user feedback.
THE RESULT
A production security feature released across China, North America, and South America.
Built close to the code.
Now working across the vehicle system.
I’m Mastan Shaik, Function Owner for Vehicle Access & Sensing, backed by more than a decade in embedded automotive software.
I shape function roadmaps, clarify functional requirements, evaluate technical concepts, and support customer–supplier alignment across Digital Key and in-cabin sensing. Within Digital Key, my work includes technical discussions around UWB, BLE, NFC, Secure Element integration, interfaces, and vehicle integration concepts.
My earlier experience in embedded C++ and Linux—across infotainment, multilingual input, augmented reality, and security-related features—helps me evaluate roadmap decisions against implementation reality: interfaces, dependencies, failure behavior, and validation needs.
Embedded C++System IntegrationRequirements EngineeringArchitectureASPICESupplier SteeringValidationTechnical Documentation
Outside my core role: I explore MCP and LLM workflows as a personal technical interest.
Automotive systems are built through good interfaces—between technologies and between people.
Always glad to connect with professionals working across vehicle access, sensing, embedded systems, and technical leadership.