Technical Support Engineer III

About the role

This role supports automotive partners in China as Mapbox expands locally. Success depends on collaboration with engineering, documentation, and support teams. The position converts complex customer questions into actionable steps for product teams.

Software engineers turn product ideas into working code. Engineers work in small teams, review each other's work, and ship in small batches. Most teams follow agile practices such as sprints and daily standups. Engineers also write tests, fix bugs, and improve performance. The field values clear communication as much as technical skill. Engineers spend part of every week on planning, code review, and debugging, not just writing new code. The ability to explain a technical decision in plain words separates strong engineers from the rest.

Key facts

What you'll do

Complex customer questions are analyzed, and the Mapbox stack is explored to craft clear, friendly responses for partners. The results of this analysis are shared with product engineers to guide roadmap decisions.

Public-facing accuracy is ensured so partners receive reliable guidance.

Support quality is maintained at a high standard by coordinating with the broader Mapbox support team on shared goals and workflows. User cases are aggregated and translated into clear requirements for internal teams.

User feedback from public channels is collected and converted into clear action steps for product engineers. Each step is tracked to ensure issues are addressed.

Public GitHub issues in Mapbox repositories are tracked, and users and contributors receive timely assistance as needed. Repository activity is monitored to reduce resolution time for reported problems.

Requirements

The posting states a bachelor's degree requirement. A degree is required to demonstrate foundational technical knowledge. Native-level fluency in Mandarin and English is necessary for both written and verbal communication with partners and teams.

Experience supporting automotive OEMs or Tier 1 suppliers is required to understand in-car navigation and connectivity challenges specific to the sector. Hands-on Android SDK experience with Kotlin or Java is required to debug issues and guide customers at the code level.

A background in support engineering or software engineering with a customer-first approach is required to handle complex technical inquiries. Comfort using GitHub and command-line tools is required for effective issue tracking and reproduction.

Experience working with engineering and product management teams during software development is required to align support with product updates. Familiarity with geospatial tools is required to interpret map data and navigation flows.

Desire or ability to learn JavaScript or iOS (Swift) is required to assist customers across major mobile platforms. Formal or informal education experience is required to train partners on platform capabilities.

Practical notes

This role is based in China and follows Mapbox policies. Employment eligibility to work in China is required for this position. Typical interview steps

Hiring for engineering roles usually starts with a recruiter screen, followed by one or two technical rounds. Candidates often solve a coding problem, discuss past projects, and answer system design questions. Some loops include a take-home task. Final rounds typically cover team fit and give candidates a chance to ask questions. Interviewers look for how you break down an unfamiliar problem, not just whether you reach the answer. Practicing a few problems aloud and reviewing your own past projects are the best preparation.

Good to know

Location-aware businesses use real-time data to power navigation for people, packages, and vehicles. High-definition maps and connected vehicle solutions rely on consistent data streams and rapid issue resolution. Automotive sector expertise focuses on cockpit experiences and integration with OEM systems. Android development often involves debugging SDK integrations and providing code-level guidance to partners. Open source workflows through GitHub require monitoring issues and contributing to public repositories. Communication across languages and documentation processes supports consistent product updates.