Mobile QA: market
Data as of November 19, 2026: 42 open Mobile QA jobs, 57% remote among jobs that state a work format; median advertised salary $11,264/mo (from 5 postings that state a salary). Source: Zorky, updated daily.
Mobile QA — mobile application testing engineer for iOS and Android: checks quality of native and cross-platform apps with mobile environment specifics — device fragmentation, OS versions, screen sizes, gestures, network conditions, interruptions and system resource work. Main difference from web QA — fragmentation: thousands of Android models, different iOS / Android versions, different screen sizes and densities, manufacturers with own skins. Role family: Mobile QA Engineer (general — manual + automation), Mobile QA Automation Engineer (focus on autotests), Mobile Manual QA (deep manual and exploratory testing), often with iOS / Android specialization. Cloud device farms: BrowserStack, Sauce Labs, AWS Device Farm, Firebase Test Lab — access to hundreds of real devices. Network debugging: Charles Proxy, Proxyman. Infrastructure: Android Studio + Xcode, emulators / simulators and real devices, ADB, Firebase Crashlytics (crash analysis), CI/CD for mobile builds. Testing specifics: gestures and touch interactions, interruptions (call, notification, focus loss), network conditions (3G / offline / switching), battery and memory, permissions, push notifications, deep links, App Store / Google Play release testing, localization. Top stack: appium, java, agile, kotlin, ci/cd. Among jobs with a stated work format, 57% are remote. Mobile QA — in-demand specialization: mobile applications exist at almost every product, and environment specifics require separate expertise.
Data as of:
Key numbers for the Mobile QA market: open jobs, median salary, observed talent pool and remote share.
The Mobile QA market currently has 42 open roles, 36 of them freshly observed. Median salary $11,264/mo.
Among jobs with a stated work format, 57% are remote. Most work done remotely; nuance — real device access solved by cloud farms (BrowserStack / Sauce Labs) or shipping key devices.
⚠ salary known for 5 of 42 jobs; remote share from 35 with a stated format; 36 counted as fresh observations; trend and hiring difficulty are not shown
Timeline: postings and sources
How many Mobile QA postings appeared each week since Jun 1, and from how many sources. The lower chart separates market growth from coverage growth: a jump in the week new sources were connected means we started seeing more, not that the market grew.
New postings per week
Chart data
| Period | New postings per week |
|---|---|
| 2026-06-01 | 0 |
| 2026-06-08 | 1 |
| 2026-06-15 | 1 |
| 2026-06-22 | 6 |
| 2026-06-29 | 4 |
| 2026-07-06 | 9 |
| 2026-07-13 | 2 |
| 2026-07-20 | 5 |
| 2026-07-27 | 7 |
| 2026-08-03 | 7 |
| 2026-08-10 | 6 |
| 2026-08-17 | 0 |
| 2026-08-24 | 2 |
| 2026-08-31 | 2 |
| 2026-09-07 | 3 |
| 2026-09-14 | 6 |
| 2026-09-21 | 5 |
| 2026-09-28 | 11 |
| 2026-10-05 | 4 |
| 2026-10-12 | 28 |
| 2026-10-19 | 13 |
| 2026-10-26 | 10 |
| 2026-11-02 | 11 |
| 2026-11-09 | 6 |
Active sources per week
Sources over the period: 55. ▲ — a week with a large batch of new sources.
Chart data
| Period | Active sources |
|---|---|
| 2026-06-01 | 0 |
| 2026-06-08 | 1 |
| 2026-06-15 | 1 |
| 2026-06-22 | 5 |
| 2026-06-29 | 4 |
| 2026-07-06 | 9 |
| 2026-07-13 | 2 |
| 2026-07-20 | 5 |
| 2026-07-27 | 6 |
| 2026-08-03 | 6 |
| 2026-08-10 | 4 |
| 2026-08-17 | 0 |
| 2026-08-24 | 2 |
| 2026-08-31 | 2 |
| 2026-09-07 | 2 |
| 2026-09-14 | 6 |
| 2026-09-21 | 5 |
| 2026-09-28 | 8 |
| 2026-10-05 | 4 |
| 2026-10-12 | 8 |
| 2026-10-19 | 9 |
| 2026-10-26 | 8 |
| 2026-11-02 | 10 |
| 2026-11-09 | 6 |
New sources connected: Jun 22 +4 · Jul 6 +7 · Aug 3 +4 · Sep 21 +4 · Oct 12 +4 · all weeks (21) in the table
| Week | New sources | New postings |
|---|---|---|
| Jun 8 | +1 | 1 |
| Jun 15 | +1 | 1 |
| Jun 22 | +4 | 6 |
| Jun 29 | +2 | 4 |
| Jul 6 | +7 | 9 |
| Jul 13 | +2 | 2 |
| Jul 20 | +2 | 5 |
| Jul 27 | +3 | 7 |
| Aug 3 | +4 | 7 |
| Aug 10 | +1 | 6 |
| Aug 24 | +2 | 2 |
| Aug 31 | +2 | 2 |
| Sep 14 | +1 | 6 |
| Sep 21 | +4 | 5 |
| Sep 28 | +3 | 11 |
| Oct 5 | +2 | 4 |
| Oct 12 | +4 | 28 |
| Oct 19 | +3 | 13 |
| Oct 26 | +2 | 10 |
| Nov 2 | +2 | 11 |
| Nov 9 | +3 | 6 |
The current week is not over yet and is not shown: an incomplete week would look like a drop.
Week = posting first-seen date, all statuses; postings are selected by the same rule as this page's counter. Sources are distinct collection channels; their names are not published.
Chart data
| Week | New postings per week | Active sources |
|---|---|---|
| 2026-06-01 | 0 | 0 |
| 2026-06-08 | 1 | 1 |
| 2026-06-15 | 1 | 1 |
| 2026-06-22 | 6 | 5 |
| 2026-06-29 | 4 | 4 |
| 2026-07-06 | 9 | 9 |
| 2026-07-13 | 2 | 2 |
| 2026-07-20 | 5 | 5 |
| 2026-07-27 | 7 | 6 |
| 2026-08-03 | 7 | 6 |
| 2026-08-10 | 6 | 4 |
| 2026-08-17 | 0 | 0 |
| 2026-08-24 | 2 | 2 |
| 2026-08-31 | 2 | 2 |
| 2026-09-07 | 3 | 2 |
| 2026-09-14 | 6 | 6 |
| 2026-09-21 | 5 | 5 |
| 2026-09-28 | 11 | 8 |
| 2026-10-05 | 4 | 4 |
| 2026-10-12 | 28 | 8 |
| 2026-10-19 | 13 | 9 |
| 2026-10-26 | 10 | 8 |
| 2026-11-02 | 11 | 10 |
| 2026-11-09 | 6 | 6 |
Remote work over time
Share of Mobile QA postings offering fully remote work, per week.
Remote postings, %
Chart data
| Period | Remote |
|---|---|
| 2026-10-12 | 36.4 |
| 2026-10-19 | 41.7 |
| 2026-10-26 | — |
| 2026-11-02 | 72.7 |
| 2026-11-09 | — |
The series starts on Oct 12: there is no data before that.
The share is among postings that state a format (remote, hybrid, office). Weeks with fewer than 10 such postings are left blank.
Chart data
| Week | Remote |
|---|---|
| 2026-06-01 | — |
| 2026-06-08 | — |
| 2026-06-15 | — |
| 2026-06-22 | — |
| 2026-06-29 | — |
| 2026-07-06 | — |
| 2026-07-13 | — |
| 2026-07-20 | — |
| 2026-07-27 | — |
| 2026-08-03 | — |
| 2026-08-10 | — |
| 2026-08-17 | — |
| 2026-08-24 | — |
| 2026-08-31 | — |
| 2026-09-07 | — |
| 2026-09-14 | — |
| 2026-09-21 | — |
| 2026-09-28 | — |
| 2026-10-05 | — |
| 2026-10-12 | 36.4 |
| 2026-10-19 | 41.7 |
| 2026-10-26 | — |
| 2026-11-02 | 72.7 |
| 2026-11-09 | — |
Clean market: hiring index
The same 7,505 employer job boards; the posting count comes from the board itself. Connecting new sources does not move this index — it shows the market, not our coverage. This is the whole panel market, not just Mobile QA.
Hiring index, Oct 16 = 100
Chart data
| Period | Hiring index |
|---|---|
| 2026-10-16 | 100 |
| 2026-10-17 | 100.03 |
| 2026-10-18 | 99.76 |
| 2026-10-19 | 99.68 |
| 2026-10-20 | 99.27 |
| 2026-10-21 | 98.6 |
| 2026-10-22 | 99.07 |
| 2026-10-23 | 97.4 |
| 2026-10-24 | 97.41 |
| 2026-10-26 | 97.33 |
| 2026-10-27 | 96.76 |
| 2026-10-28 | 96.21 |
| 2026-10-29 | 95.17 |
| 2026-10-30 | 95.13 |
| 2026-10-31 | 93.65 |
| 2026-11-01 | 93.33 |
| 2026-11-02 | 92.67 |
| 2026-11-03 | 92.65 |
| 2026-11-04 | 92.41 |
| 2026-11-05 | 92.13 |
| 2026-11-06 | 90.44 |
| 2026-11-07 | 90.48 |
| 2026-11-08 | 90.45 |
| 2026-11-10 | 90.29 |
| 2026-11-11 | 90.22 |
| 2026-11-13 | 90.12 |
| 2026-11-14 | 89.7 |
| 2026-11-15 | 89.68 |
| 2026-11-16 | 89.62 |
| 2026-11-18 | 88.91 |
| 2026-11-19 | 88.02 |
Chain index: each day compares only boards polled on both that day and the previous one; outliers and platform-wide polling outages are excluded. Days with no comparable pairs are left blank.
Chart data
| Day | Hiring index |
|---|---|
| 2026-10-16 | 100 |
| 2026-10-17 | 100.03 |
| 2026-10-18 | 99.76 |
| 2026-10-19 | 99.68 |
| 2026-10-20 | 99.27 |
| 2026-10-21 | 98.6 |
| 2026-10-22 | 99.07 |
| 2026-10-23 | 97.4 |
| 2026-10-24 | 97.41 |
| 2026-10-26 | 97.33 |
| 2026-10-27 | 96.76 |
| 2026-10-28 | 96.21 |
| 2026-10-29 | 95.17 |
| 2026-10-30 | 95.13 |
| 2026-10-31 | 93.65 |
| 2026-11-01 | 93.33 |
| 2026-11-02 | 92.67 |
| 2026-11-03 | 92.65 |
| 2026-11-04 | 92.41 |
| 2026-11-05 | 92.13 |
| 2026-11-06 | 90.44 |
| 2026-11-07 | 90.48 |
| 2026-11-08 | 90.45 |
| 2026-11-10 | 90.29 |
| 2026-11-11 | 90.22 |
| 2026-11-13 | 90.12 |
| 2026-11-14 | 89.7 |
| 2026-11-15 | 89.68 |
| 2026-11-16 | 89.62 |
| 2026-11-18 | 88.91 |
| 2026-11-19 | 88.02 |
How many open Mobile QA jobs there are and how many matching specialists Zorky observes.
Demand and observed supply
Chart data
| Metric | Value |
|---|---|
| Open demand | 42 |
| Open demand | 42 |
| Observed supply | — not published |
Mobile QA — stably in-demand specialization: mobile apps exist at almost every B2C product. Drivers 2026: growth of mobile app complexity (banks, super-apps), device fragmentation, tool development (Maestro), automation requirement. Demand even and wide.
⚠ candidates matching a vacancy are not counted yet: demand and the observed pool are shown
How salaries in Mobile QA jobs are distributed, in US dollars per month.
Salary distribution
Chart data
| Metric | Value |
|---|---|
| <$1k | 0 |
| $1–2k | 0 |
| $2–3k | 0 |
| $3–4k | 0 |
| $4–5k | 0 |
| $5–6k | 0 |
| $6–7k | 0 |
| $7–8k | 1 |
| $8–9k | 0 |
| $9–10k | 1 |
| $10–12k | 2 |
| $12–15k | 0 |
| $15–20k | 1 |
| $20k+ | 0 |
- usable for the calculation: 5 (11.9%)
- stated but not converted to USD/month: 4 (9.5%)
- not stated: 33 (78.6%)
One in ten postings offers under $7,507, one in ten over $15,505. Half of the postings offer between $9,583 and $11,666. Sample: 5.
⚠ percentiles from 5 salaries out of 42 jobs — a guide on a small sample
Chart data
| Metric | Lower bound | Upper bound | Count |
|---|---|---|---|
| <$1k | 0 | 1,000 | 0 |
| $1–2k | 1,000 | 2,000 | 0 |
| $2–3k | 2,000 | 3,000 | 0 |
| $3–4k | 3,000 | 4,000 | 0 |
| $4–5k | 4,000 | 5,000 | 0 |
| $5–6k | 5,000 | 6,000 | 0 |
| $6–7k | 6,000 | 7,000 | 0 |
| $7–8k | 7,000 | 8,000 | 1 |
| $8–9k | 8,000 | 9,000 | 0 |
| $9–10k | 9,000 | 10,000 | 1 |
| $10–12k | 10,000 | 12,000 | 2 |
| $12–15k | 12,000 | 15,000 | 0 |
| $15–20k | 15,000 | 20,000 | 1 |
| $20k+ | 20,000 | — | 0 |
Which countries have the most open Mobile QA jobs.
Demand geography
| country | jobs | share |
|---|---|---|
| Ukraine | 7 | 18.4% |
| Poland | 7 | 18.4% |
| United States | 6 | 15.8% |
| Russia | 4 | 10.5% |
| France | 1 | 2.6% |
| Romania | 1 | 2.6% |
| Malaysia | 1 | 2.6% |
| Georgia | 1 | 2.6% |
| Moldova | 1 | 2.6% |
| India | 1 | 2.6% |
| Other countries | 8 | 21.1% |
Leader by Mobile QA job count — Ukraine (7 positions). Demand wide — banks / fintech, marketplaces, ecosystems and services, delivery, travel, media, gaming. International companies hire Russian-speaking Senior Mobile QA on full-remote.
⚠ job counts only: salary by country is not published
Chart data
| Country | Jobs |
|---|---|
| UA | 7 |
| PL | 7 |
| US | 6 |
| RU | 4 |
| FR | 1 |
| RO | 1 |
| MY | 1 |
| GE | 1 |
| MD | 1 |
| IN | 1 |
Which technologies are most often required in the same job as Mobile QA.
Used together with
Share — how many of the 42 jobs in the Mobile QA market mention this technology. Ordered by job count, not by “strength of association”. Umbrella terms like cloud are not a specific cloud (AWS, Azure).
Common pairs: Appium + Python / Java, Espresso + Kotlin, XCUITest + Swift, Appium + cloud device farm, Maestro for fast UI scenarios. Learning roadmap: QA basics → iOS / Android structure → manual mobile testing (emulators + real devices, ADB, Charles) → automation (Appium or native) → programming language → CI/CD → pet project with autotests on device farm.
Chart data
| Name | Count |
|---|---|
| appium | 17 |
| java | 10 |
| kotlin | 10 |
| cloud | 7 |
| postman | 6 |
| jenkins | 5 |
| playwright | 5 |
| react | 5 |
| selenium | 5 |
| swift | 4 |
| cypress | 3 |
| flutter | 3 |
How many Mobile QA jobs there are at each level, from junior to principal.
Demand by grade
| grade | jobs |
|---|---|
| senior | 12 |
| middle | 7 |
| lead | 2 |
| principal | 1 |
Career flow: Mobile Manual QA → Mobile QA Automation → Senior → Mobile QA Lead, or transition to general Automation / SDET. Mobile QA Automation (with autotests) valued noticeably higher than purely manual.
⚠ demand side only: the grade of the observed pool is unknown for most of it
Chart data
| Level | Count |
|---|---|
| senior | 12 |
| middle | 7 |
| lead | 2 |
| principal | 1 |
Who hires the most for Mobile QA and how concentrated demand is among the largest companies.
Employers
Demand is spread across 33 employers. The largest accounts for 7.9%, the top ten for 39.5%; the remaining 60.5% is long tail.
| share | value |
|---|---|
| top-1 | 7.9% |
| top-3 | 18.4% |
| top-10 | 39.5% |
| long tail | 60.5% |
⚠ names are not shown: staffing agencies and end employers are not yet told apart by the classifier
Which company sites and job boards Zorky collects Mobile QA jobs from.
Where Zorky sees this market
Observed across 20 sources; the largest accounts for 11.9% — this market does not rest on a single channel.
Mobile QA vacancies: hh.ru («mobile QA» / «mobile app testing engineer» / «mobile app QA Automation»), Habr Career, getmatch, Djinni, LinkedIn, Telegram (QA channels and mobile QA communities). Part of positions go as general «QA Engineer» with mobile lean in responsibilities.
Chart data
| Class | Name | English name | Count | Share |
|---|---|---|---|---|
| ats | ATS и карьерные сайты | ATS & career sites | 23 | 0.5476 |
| board | джоб-борды и агрегаторы | job boards & aggregators | 15 | 0.3571 |
| telegram | Telegram | Telegram | 4 | 0.0952 |
The newest Mobile QA jobs from company career sites.
Recent openings
- Mobile QA Engineer · UA
- Mobile QA Automation Engineer (DRWN) · FR
- Mobile QA Automation · UA
- Mobile QA Engineer · US · $9,583
- Mobile QA Automation Engineer · RU
- Mobile QA Engineer · PL
- Lead Mobile QA Automation Engineer · US · $11,264
- Lead Mobile QA Automation Engineer | 7 year(s) | Senior | Lead · $11,667
Latest open Mobile QA jobs — most recent 10 positions with adequate description quality. Full list — in our CRM or via the «see all» link below.
Adjacent markets
Mobile QA borders mobile development (iOS / Android — cross-link to /research/mobile), general QA Automation and API QA (testing app integration with backend). Inside QA neighbors Automation and Manual QA. Comparison of QA specializations — in the SiblingSubnichesChart above.
⚠ adjacent markets for comparison are not defined yet
How this is measured
- Vacancy
- an open job that cleared the quality gate and lists at least two technologies
- Observed candidate
- a candidate whose stack contains this technology; an aggregate — not a single record leaves the perimeter
- Matchable candidate
- not counted yet
- Window
- jobs open at the moment the snapshot was built
About the data
- Some breakdowns are hidden: their data coverage is not yet sufficient.
- Statistics are shown only where the sample clears a quality gate.
- A missing block does not mean a value of zero.
Breakdowns currently hidden: 8.
Direction: QA / Testing
Related specializations
Inside Mobile QA: Mobile QA Engineer (general — manual + automation), Mobile QA Automation Engineer (focus on autotests — valued higher), Mobile Manual QA (deep manual and exploratory testing), often with iOS or Android specialization. Adjacent QA specializations — Automation, API QA. Comparison — in the bar below.
Frequently asked questions
The most common questions about Mobile QA: pay, grades, tools (Appium vs Espresso vs XCUITest vs Maestro), real devices vs emulators and device farms, mobile testing specifics (fragmentation / interruptions / network / permissions), remote, companies, how to start, Senior skills. Answers recompute automatically.
What tools are most often required from Mobile QA?
Top-5: appium, java, agile, kotlin, ci/cd. Cloud device farms: BrowserStack, Sauce Labs, AWS Device Farm, Firebase Test Lab. Network debugging: Charles Proxy, Proxyman (traffic interception and substitution). Infrastructure: Android Studio + Xcode, ADB (Android Debug Bridge), emulators / simulators and real devices, Firebase Crashlytics (crash analysis), CI/CD for mobile builds (Fastlane, GitHub Actions, Bitrise). Languages: for automation — Java / Kotlin (Android, Espresso), Swift (XCUITest), JavaScript / Python (Appium). Knowledge: mobile platform structure, App Store / Google Play guidelines, test design with fragmentation.
Appium vs Espresso vs XCUITest vs Maestro — what to choose?
Appium — cross-platform: one set of tests and one tool work on both iOS and Android (under the hood uses Espresso / XCUITest). Plus — savings on double codebase, familiar WebDriver protocol. Minus — slower and less stable than native tools. Espresso — native Android automation from Google: fast, stable, synchronizes with app's UI thread; tests in Java / Kotlin, live next to app code. XCUITest — native iOS automation from Apple: analog for iOS, tests in Swift. Maestro — modern tool 2024–2026: simple YAML-like syntax, low entry threshold, cross-platform, fast gaining popularity; suitable for fast UI scenarios, but less flexible for complex logic. Strategy: if one tool needed for both platforms and team is small — Appium or Maestro (Maestro — if simplicity and start speed matter). If separate iOS and Android teams exist and test speed and stability matter — native Espresso + XCUITest (often written by developers themselves). Many products use a combination. Knowing Appium worth in any case — it's in vacancies most often.
Real devices vs emulators — and why are device farms needed?
Emulators (Android) and simulators (iOS) — virtual devices on computer: start fast, convenient for development and running autotests, free, easily scale. Minuses — don't reproduce real hardware: performance, camera / GPS / sensor behavior, manufacturer skin specifics (Samsung One UI, MIUI / HyperOS, etc.), real network conditions, battery drain. Real devices — mandatory for final testing, performance check, gestures, specific vendor specifics and rare bugs. Problem — keeping large physical device park is expensive and inconvenient. Cloud device farms (BrowserStack, Sauce Labs, AWS Device Farm, Firebase Test Lab) solve this: give network access to hundreds of real devices with different models and OS versions — both for manual testing and for autotest runs in CI. Practice 2026: emulators / simulators for development and fast autotests; real devices (own key models + cloud farm) for fragmentation coverage and final check. Competent device matrix choice (which models / OS versions to cover) — separate Mobile QA skill, based on product audience analytics.
What's specific to mobile testing?
Mobile QA checks much that's not in web: Fragmentation — thousands of Android models, different iOS / Android versions, screen sizes and densities, manufacturer skins; thoughtful device matrix needed. Interruptions — incoming call, notification, alarm, app backgrounding, focus loss; app should correctly save and restore state. Network conditions — 3G / slow network / offline / Wi-Fi↔mobile network switching; behavior at connection loss. App lifecycle — background / return, system memory unload, cold and warm start. Permissions — camera, geolocation, contacts, notifications; "granted / denied / revoked" scenarios. Device resources — battery drain, memory, heating, behavior on weak devices. System integrations — push notifications, deep links, sharing, biometrics, payment (Apple Pay / Google Pay). Gestures — swipes, multitouch, scroll, pull-to-refresh. Localization — different languages, RTL, formats. This specificity makes Mobile QA separate expertise, not "web testing on phone".
What share of jobs are remote?
Among jobs with a stated work format, 57% are remote. Jobs without a stated format are excluded from the denominator; hybrid work is not counted as remote.
How to start a Mobile QA career in 2026?
Mobile QA — good entry to testing (can start with manual). Roadmap: 1) QA basics — test design, types of testing, bug reports, checklists and test cases, bug lifecycle. 2) Mobile platform structure — how iOS and Android work, app lifecycle, permissions, types of apps (native / cross-platform / hybrid). 3) Manual mobile testing — learn to test app accounting for specifics (interruptions, network, fragmentation, gestures); master emulators / simulators and real devices, ADB, log capture, Firebase Crashlytics. 4) Network debugging — Charles Proxy / Proxyman (traffic interception, app API requests check). 5) Automation — choose direction: Appium (cross-platform, on Python / Java / JavaScript) or native (Espresso + Kotlin for Android, XCUITest + Swift for iOS); Maestro as simple start. 6) Programming languages — for automation need at least one (Kotlin / Java / Python / JavaScript). 7) CI/CD — how mobile builds and autotests run in pipeline. 8) Pet project: take open-source app, write set of autotests on Appium or Espresso, run on device farm. Mobile QA Automation valued noticeably higher than manual — move toward automation.
How many open jobs are in this sample?
The published sample contains 42 open jobs after merging reposts. This is the same count shown in the main indicator. The geography section describes the sample coverage; this is not an estimate of the entire market.
What skills does a Senior Mobile QA need?
Senior Mobile QA owns quality strategy of mobile product. Deep platform knowledge: iOS and Android structure, app lifecycle, OS version and manufacturer skin features, App Store / Google Play guidelines and release processes. Test design with specifics: device matrix / OS versions building based on audience analytics, coverage of mobile-specific risks (interruptions, network, resources, permissions, deep links, push). Production-level automation: autotest architecture design (Appium and / or native Espresso / XCUITest), Page Object and stable locators, fighting flaky tests (mobile autotests are especially unstable), parallel runs. Device farms: effective work with BrowserStack / Sauce Labs / Firebase Test Lab, reasonable balance of real devices and emulators. CI/CD: autotest integration in mobile build pipeline (Fastlane, Bitrise), test gates. Programming: confident code in automation language (Kotlin / Java / Swift / Python / JavaScript). Debugging: log reading, ADB, crash analysis (Crashlytics), network debugging (Charles / Proxyman), app performance and memory profiling. API: backend understanding, testing of app integration with API. Processes: building mobile release testing process, beta channels, work with product and development. Soft: autotest code review, mentoring, communication.
Leave a request
Describe the task and leave a contact — the request goes to our CRM and we reply at the contact you provide.