Senior QA Engineer

About the role

This role belongs to an Engineering squad that evaluates and validates a high quality financial suite.

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

Requirements

Bring 10+ years of Software Quality Assurance experience, with a focus on financial technology or a related domain.

Demonstrate strong web service and API testing能力, including reading specs and diagnosing failures at the REST layer.

Work effectively with teams of Software QA Engineers in manual and automated testing environments.

Employ Microsoft SQL Server or similar database skills to retrieve and manipulate data for test validation.

Use tools such as Jira, Zephyr, Bitbucket, GitHub, Jenkins, and Docker in daily workflows.

Drive issues to resolution by digging beyond surface failures and connecting cross-layer causes.

Maintain a positive learning attitude and a strong desire to impact company culture and products.

Show ownership by initiating improvements without waiting for direction and taking pride in delivered quality.

Nice to have

Apply experienced usage of AI tools like Claude Code throughout the QA lifecycle, including test creation and impact analysis.

Leverage Postman or similar API testing tools for designing and executing tests.

Practice integration testing for inbound and outbound file processing, API testing, and configuration testing.

Understand market data platforms such as BETA, APL, FIX, IDC, Reuters, Morningstar, or Bloomberg.

Use log collection and analysis, APM, and DB monitoring tools such as Dynatrace.

Troubleshoot, diagnose, resolve, and explain system-level issues affecting the application.

Write scripts in a language such as Python to support test automation.

Conduct performance testing using tools such as Locust.io.

Collaborate across squads and disciplines to find fair solutions for emerging problems.

Skills & tools

Financial services domain knowledge, API testing, SQL, automation frameworks, CI/CD pipelines, AI-assisted testing tools, and performance testing tools.

Practical notes

This role is based in Boston, MA, with hybrid work expectations. The team follows an agile delivery cadence within an enterprise SaaS environment.

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

Work centers on validating complex financial systems and protecting client data. The role relies on rigorous test design, cross-team collaboration, and continuous learning. Common tools include AI assistants, API clients, database query tools, and monitoring platforms. Performance and stability are critical in a market-based compensation structure.

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.