Senior Test Engineer Radio Frequency IRC

Description

Willing to relocate to Madrid.

• 2-4 years of experience in GUI/UI test automation (any platform).
• Practical Swift skills—comfortable reading and writing production Swift code.
• Experience with XCUITest / XCTest on macOS or iOS, including the Page Object pattern.
• Working knowledge of SwiftUI—accessibility identifiers, view hierarchy basics, async state.
• Day‑to‑day use of Xcode and xcodebuild, test plans (.xctestplan), schemes.
• Git fluency—branching, rebasing, resolving conflicts, disciplined PR workflow, good commit hygiene, comfortable reviewing and being reviewed.
• JIRA (or equivalent issue tracker)—creating well‑scoped tickets, linking PRs, writing reproductions, keeping statuses current.
• Jenkins CI/CD hands‑on experience—reading and modifying Jenkins files, triaging red builds, understanding declarative pipelines, stages, artifacts, and agents.
• Conda / virtual environment fluency—creating and activating environments, resolving dependency conflicts, understanding how PYTHON PATH, Poetry, and pyproject.toml interact. Awareness that breaking an environment breaks the whole pipeline.
• A systems mindset: understands that a passing local test is not a passing PR, and that coding practices (imports, globals, shared state, flaky waits, dependency bumps) can cascade into CI and team‑wide breakage.
• Debugging mindset for async / flaky UI tests—waits, expectations, race conditions.
• Professional English, written and spoken—the team operates in English and most collaborators are in PST.
• Willingness to overlap ~3-4 hours daily with PST.

• Write and maintain XCUITest automation using the existing Page Object structure.
• Add coverage for new features and user flows as the apps evolve.
• Investigate and fix flaky tests; reproduce, triage, and root‑cause failures.
• Own your changes through CI—debug Jenkins file stages, read pipeline logs, understand how your test affects downstream jobs (build, publish, acceptance).
• Keep Conda / Poetry / npm environments healthy in the repos you touch; avoid dependency drift and lockfile breakage.
• Track work, bugs, and flaky‑test investigations in the team's issue tracker (JIRA or equivalent) with clear reproduction steps and logs.
• Collaborate asynchronously with PST‑based developers via Git code reviews, written specs, and written updates.
• Contribute improvements to the test framework (helpers, utilities, reporting) under guidance from senior engineers.