Senior Manual QA Engineer, B2C

About the role

This role strengthens the Quality Engineering team by validating complex financial flows on mobile and web platforms. The position safeguards user trust and platform reliability for millions of European customers. It collaborates closely with product and design to reduce release risk and uphold quality standards.

Software engineers turn product ideas into working code. Engineers work in small teams, review each other's work, and ship in small batches. Most teams follow agile practices such as sprints and daily standups. Engineers also write tests, fix bugs, and improve performance. The field values clear communication as much as technical skill. Engineers spend part of every week on planning, code review, and debugging, not just writing new code. The ability to explain a technical decision in plain words separates strong engineers from the rest.

Key facts

What you'll do

Testing strategies for intricate mobile and web flows are designed and executed, with end-to-end testing lifecycles managed by integrating exploratory methods with structured regression and smoke testing. The outcomes ensure resilient user experiences across diverse devices and network conditions.

Complex architectural issues and high-stakes financial integrations are debugged using Postman, Android Studio, and Xcode, with stability maintained under real transaction loads. Results validate that money movements and data remain accurate and reliable for customers.

This practice reduces rework and aligns development with user and regulatory expectations.

Actions target root causes to improve platform robustness and test coverage over time.

Standards guide work from planning through delivery to protect release integrity.

Requirements

Experience in fast-growing mobile and web environments is demonstrated, with fintech or highly regulated sectors preferred for context and compliance awareness. Candidates understand constraints and opportunities in these domains.

Mastery of Postman, JIRA/Xray, Android Studio, and Xcode is essential, including navigating logs, proxying traffic, and inspecting databases to isolate issues. These tools enable deep validation of client and server behavior.

Technical risks are translated into clear business impact for stakeholders, and high-level feedback is provided to developers in a constructive manner. Communication focuses on outcomes, trade-offs, and quality implications for products and users.

Performance in fast-paced, multicultural settings is effective, with ambiguity navigated to deliver secure and stable products. Adaptability and calm problem-solving support continuity across distributed teams and evolving requirements.

Practical notes

Country-based restrictions or security clearance may be required for this role, and onsite presence in Barcelona is expected on designated days. Occasional business travel may be necessary for collaboration or validation activities. 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

QA in fintech depends on strict compliance, precise test design, and secure handling of financial data. Manual validation remains critical where automated checks cannot cover nuanced user workflows. Collaboration across time zones demands clear communication and shared quality standards. Toolchains often include mobile simulators, API clients, and version control systems. Continuous learning keeps quality practices aligned with evolving regulatory expectations.

Career growth

Engineering careers usually progress from individual contributor to senior, staff, and principal levels. Some engineers move into management and lead teams of five to twenty people. Others stay on the technical track. Growth follows demonstrated impact, not tenure alone. A typical engineering ladder has clear levels with defined expectations for scope, quality, and mentorship. Moving up usually requires owning outcomes end to end rather than completing assigned tickets.