QA Engineer - Trading Systems

QA Engineer – Trading Systems

Overview

🏢 Company | Trading Technology, Market Infrastructure, FinTech

👤 Position | QA Engineer

🎯 Impact | Live trading systems, release quality, automation progression

📏 Size | ~100 people globally (tight engineering + QA team)

🌟 Skills | Linux, SQL, Python, Automation (growing), Backend Testing

📍 Location | London

💻 Hybrid | 3 days in office

💰 Offer | £60,000 + bonus + benefits

The Role

You’ve probably done a bit of everything in QA.

Some manual testing. Some automation. Maybe a bit of scripting. You know there’s a better way to do it, but you haven’t quite had the environment to go all-in on it yet.

This is that environment.

You’ll be working on systems that are live, time-sensitive, and used in real trading environments. When something breaks here, it matters. Which means your work matters.

You’ll get:

• The chance to move properly into automation, not just maintain test cases
• Exposure to backend systems, APIs, and data-heavy platforms
• A team that actually works with QA, not around it
• The space to own what you test, not just execute someone else’s plan

And importantly, you won’t be expected to walk in as a finished automation expert. You’ll be expected to grow into one.

What you’ll be doing

• You’ll test releases across backend systems, APIs, and data flows
• You’ll design and run both manual and automated tests
• You’ll build out automation using Python and modern frameworks over time
• You’ll work closely with developers to understand changes before they hit production
• You’ll take ownership of defects and see them through to resolution

You’ll also get exposure to real-world trading workflows, where edge cases aren’t theoretical — they happen.

What you’ll need

Keep it focused, three things matter here:

• You’re comfortable in a Linux environment and can work with SQL
• You’ve tested real systems (not just simple web apps)
• You’ve started using automation (Python / Selenium / Playwright / similar)

That’s it.

You don’t need to have built full frameworks. You don’t need to be an expert in every tool. But you do need to want to get better.

The environment

You’ll be joining a team where:

• QA is part of engineering, not an afterthought
• People take ownership of what they ship
• You’ll be working closely with developers and operations, not in a silo
• The systems are complex enough to keep you learning

Interview Process

📅 CV Review → Intro Call → Technical Interview → Final Discussion → Offer

What next

If you’re at that point where you want to move from “doing QA” to actually owning quality, this is worth a conversation.

Apply or drop me a message, I’ll give you the full picture and you can decide from there.