RAVE II, Demo Ops

About the role

The RAVE II, Demo Ops role at Mapbox focuses on functional validation for navigation customers to ensure APK behavior aligns with product expectations before release. You will coordinate issue reporting between RAVE and engineering teams while maintaining detailed documentation that tracks testing coverage and traceability. This position requires hands-on verification of APK behavior through structured testing methodologies and close collaboration with engineering partners. The role emphasizes clear communication as much as technical execution in a fast-paced environment. You will own repetitive tasks with high personal productivity and adapt quickly to different workflows and project requirements. Strong analytical thinking will be applied to identify patterns across large information sets during testing cycles. The position values candidates who can explain technical decisions in plain words and contribute to efficient agile practices.

Key facts

• Degree: stated degree requirement.

-

Location: Mapbox Minsk

-

Engagement: Full-time.

What you'll do

Real customers APK behavior is checked through functional testing to confirm it matches expectations and defined product requirements. Up-to-date test documentation, including test cases and traceability matrix, is created and meticulously maintained to monitor testing coverage across all navigation features. Issues discovered during testing are systematically communicated to the relevant RAVE teams and to the engineering teams for timely resolution and verification. Testing procedures validate that map data and routing logic in navigation apps work correctly through targeted validation scenarios and structured test execution. You will manage work items in Jira, ensuring proper tracking of testing activities, defects, and verification cycles with attention to detail. Experience with AI tools can support test execution in emerging workflows and assist in improving testing efficiency over time. Clear documentation practices help teams understand product behavior, track coverage, and reduce risks associated with navigation functionality. The role requires efficient handling of repetitive tasks while maintaining high personal productivity and quickly learning new processes and project workflows. Analytical thinking is essential to identify patterns across large information sets and to ensure comprehensive test coverage. Strong communication skills in English at B1+ level support clear written and verbal communication with distributed teams during daily interactions.

Requirements

• Manual QA experience is required, and completed courses or demonstrable work samples should be available to discuss during the interview process.
• Basic knowledge of Jira is required to manage work items, track testing activities, and maintain accurate documentation of test results.
• Repetitive tasks are handled efficiently, with high personal productivity, quick learning of new processes, and adaptation to different workflows and projects in a dynamic environment.
• Analytical thinking is applied to identify patterns across large information sets, and teamwork plus communication skills are used daily to collaborate effectively with RAVE and engineering teams.
• English proficiency at B1+ supports clear written and virtual communication, and the level must be indicated on your CV for proper evaluation.
• A driver license is required for the role due to potential office attendance requirements and travel needs within the Minsk area.
• Office attendance is required for the first three months during probation, with periodic visits for team sprints and collaborative sessions.
• Candidates must demonstrate completed courses or demonstrable work samples related to manual QA to discuss during the evaluation process.

Practical notes

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

Testing in an IT context relies on structured test cases and traceability to reduce risk and ensure comprehensive coverage of navigation functionality. Navigation apps often use map data and routing logic that require targeted validation scenarios to verify correct behavior in real-world conditions. Experience with AI tools can support test execution in emerging workflows and help improve testing efficiency over time. Clear documentation helps teams track coverage, understand product behavior, and communicate effectively across distributed teams. Strong communication skills reduce misunderstandings across distributed teams and ensure alignment between RAVE and engineering stakeholders.

Questions to ask

Worth asking in any interview: how the team measures success, who the role works with daily, what the onboarding looks like, and what the company is trying to achieve this year. Asking what past hires did well is a strong final question that can provide insight into expectations and performance. Keep the list short and pick the questions that matter most to you to make the most of your interview opportunity.

Career growth

Engineering careers usually progress from individual contributor to senior, staff, and principal levels, with increasing responsibility for complex navigation validation scenarios. Some engineers move into management and lead teams of five to twenty people, while others prefer to stay on the technical track and focus on deep testing methodologies. Growth follows demonstrated impact, not tenure alone, and is evaluated through consistent delivery of high-quality testing outcomes. A typical engineering ladder has clear levels with defined expectations for scope, quality, and mentorship within the RAVE II framework. Moving up usually requires owning outcomes end to end rather than completing assigned tickets, ensuring that validation activities contribute directly to product reliability and customer satisfaction.