Source description
About the role

(Senior) QA Engineer - Network and Mobile
Turkey • Istanbul
Engineering
Remote
Full-time
About Roamless
The origin story of Roamless is one that will be familiar to many: we saw something broken, and we decided to fix it for good.
We all travel. We all need to stay connected. And we all hate roaming charges. Existing alternatives were clunky, expensive, and unreliable, so we built something better. We made it easy, reliable and affordable for travellers to get connected and stay connected as they roam the world.
Our truly global mobile connectivity service is up to 90% cheaper than traditional roaming. With one eSIM, you get instant, reliable data anywhere in the world. No SIM swaps, no hunting for Wi-Fi, no choosing countries or data packs. Your balance never expires, so you can use it across trips with zero hidden fees or expiration dates.
In just 3 years, we've grown 4-5x Year on Year and have been trusted by +1.5M users who overall rate us 4.6 on Trustpilot.
🚀 We also recently closed a $12M Series A led by Rasmal Ventures, with participation from Shorooq, Revo Capital, Finberg, and JIMCO, to fuel our mission of becoming the world's first truly global mobile operator.
Hiring globally and fully remote, we're a team of 70, and we're planning to grow to 100+ in the next ~12 months.
About the role
When a Roamless user lands in Tokyo and their eSIM activates in seconds that's because dozens of things went right across our app, our backend, and a global patchwork of carrier systems. When one of them doesn't, it's this team's job to find out why.
We're hiring a Network & Mobile Senior QA Engineer to join a small, high-ownership QA team at a company where quality directly affects whether a traveller stays connected in a foreign country.
The role is responsible for mobile app testing (iOS + Android) and core network and eSIM testing.
What makes this role genuinely different from most QA jobs: a significant part of what you test involves third-party carrier systems that can behave unexpectedly in ways neither you nor we fully control. When something breaks in that layer, you need to trace it, through logs, through API responses, through system behaviour and figure out whether it's our code, their system, or the boundary between them. Strong analytical thinking is the core of this job.
What you will do…
- Test the Roamless iOS and Android apps across real devices and device farms: functional, regression, and smoke testing across every weekly release
- Test core eSIM and network behaviour: eSIM activations, data routing, carrier fallback, and edge cases that emerge from international network scenarios
- Execute and expand integration test coverage across app-to-backend flows
- Debug failures that cross system boundaries: trace root causes through backend logs and API responses, not just surface-level symptoms
- Maintain and extend test documentation in Jira/X-ray
- Integrate AI tooling into your QA workflow (automated ticket creation, MCP-based agents, testing automation)
- Work directly with engineers to surface quality issues early in the release cycle, not just at the end
What you will bring…
Must-haves
- Strong experience testing mobile applications (iOS and/or Android)
- Backend and API testing experience: comfortable using Postman, reading API responses, validating payloads across service boundaries
- Integration testing experience: you've tested flows that cross multiple service or system boundaries
- Ability to read code and understand system logic: you don't need to write production code, but you must be able to trace a failure through backend behaviour and logs
- Strong analytical thinking: especially when debugging third-party systems where failure modes are unpredictable
- High ownership and autonomy: This is a small team and we expect everyone to own their area, not wait for direction
- Strong English and Turkish communication skills
Nice-to-haves
- Experience with Appium or Robot Framework for mobile test automation
- SQL or basic querying skills
- Background in telecoms, eSIM, network testing, or carrier integrations
- Familiarity with automation scripting for mobile testing
To get more context on who we are and how we work, read "Who is a Roamie? Our Core Traits Manifesto". It explains the core traits we look for in everyone we hire.
What we offer
-
💻 Hardware you need to be most productive
-
🌎 Location: Fully-remote anywhere in Turkey
-
💻 Home office budget. $500 on equipment for home office setup (eg. a keyboard, a screen, etc). This is a one-off budget that doesn’t renew every year, but doesn’t expire.
-
🎓 Learning and development budget. Up to $1000 annually to be spent on books, online courses, conferences, etc.
-
🌐 $200 non-expiry yearly Flex credit for data, hotspot, and calls.
-
📱 Annual phone number subscription for $1/year. You get an annual phone number subscription for $1/year. A real phone number (UK, Canada, or Australia) inside the Roamless app.
-
📝 Full-time local contract
🤗 Supportive, diverse, inclusive team
Ready to apply?
Powered by
First name *
Last name *
Email *
LinkedIn URL
Phone number
Location *
Resume *
Click to upload or drag and drop here
Cover letter
Click to upload or drag and drop here
What's your level of English? *
Native Speaker
Fluent
Intermediate
Basic
How many years of experience do you have as a QA? *
Less than one year
1-3 years
3-5 years
5-8 years
More than 8 years
Which best describes your automation experience? *
Haven't written automated scripts
Write/run scripts in an existing framework
Built an automation framework from scratch (Playwright/Selenium etc.)
Built and scaled frameworks across teams, incl. CI/CD
Which best describes your hands-on experience with regression, smoke, and integration testing? *
I understand the difference between these test types but have limited hands-on practice with them
I execute regression/smoke suites that others designed, and do basic integration checks between UI and API
I design and prioritize my own regression/smoke suites (deciding what counts as "core flows" each release) and write integration tests validating frontend–backend contracts
All of the above, plus I decide when a suite needs to expand or shrink as the product evolves, and have caught cross-service integration bugs other tests missed
Describe a situation where you had to test a system involving a third-party dependency (an external API, carrier, or service) that behaved unexpectedly. How did you investigate what went wrong, and what did you find? *
This role doesn't require writing code but does require reading it to trace logic. How would you describe your ability to read code (any language) to understand system behavior? *
Can't read code
Can follow simple logic, need help with complex code
Can independently trace logic through moderately complex codebases
Comfortable reading across multiple services/languages to diagnose issues
Anything else you want to share?
By applying you agree to Gem's terms and privacy policy.
Save your info to apply to other roles faster & help employers reach you.
Apply and saveApply without saving
Req ID: R46
More at Roamless

