Software Development Engineer in Test

Every Aspora release moves real money for customers across multiple markets. This role exists to make sure no release breaks that trust. You'll own quality end-to-end: the automation frameworks, release validation systems, and observability practices behind our mobile apps, web experiences, and backend services. You'll sit inside the engineering team, not beside it. You'll work with developers, product managers, and designers to ship releases that meet our bar for reliability, performance, and customer experience. The systems you build become the quality standard for a fast-growing global platform.

Responsibilities:

• Own automation frameworks across Android, iOS, Web, APIs, and backend services, built on Appium, REST Assured, and TestNG.
• Drive end-to-end testing strategies covering customer money journeys across mobile apps, microservices, message queues, and data pipelines.
• Build CI/CD-integrated test suites in GitHub Actions, validating every change from PR through staging to production.
• Own release validation: mobile builds, feature flags, A/B tests, beta rollouts, and phased production releases.
• Establish contract, schema, and non-functional testing that keeps APIs backwards-safe and the platform fast, resilient, and reliable.
• Leverage observability tools (Crashlytics, Sentry, Grafana) to catch regressions early, drive RCAs, and push AI-driven test automation forward.

Requirements:

• 1 to 3 years in QA or SDET roles, ideally automating mobile and backend testing for a consumer product.
• Proficient in Java, with clean coding habits and hands-on Appium and REST Assured experience.
• Strong grasp of API design, data contracts, microservices, and async workflows: queues, cron jobs, pub/sub.
• Comfortable debugging with Charles Proxy, ADB, logs, and observability platforms when something breaks in production.
• High ownership. You treat quality problems as yours until they're solved.
• Bias for execution: you ship, learn, and iterate.
• Strong advantages: JMeter or K6 Kafka or SQS, and AWS exposure.