At a Glance
- Tasks: Lead the creation of an innovative QA platform and build reusable tools for engineering teams.
- Company: Join Swap, a cutting-edge AI-native platform revolutionising global commerce.
- Benefits: Enjoy competitive salary, stock options, private health, and wellness benefits.
- Other info: Be part of a diverse team committed to equality and innovation.
- Why this job: Make a real impact by shaping quality processes and empowering engineers with your tools.
- Qualifications: 8+ years in software or test engineering, with strong experience in developer tools.
The predicted salary is between 80000 - 100000 £ per year.
About Swap
Swap is the infrastructure behind modern agentic commerce. The only AI-native platform connecting backend operations with a forward-thinking storefront experience. Built for brands that want to sell anything - anywhere, Swap centralises global operations, powers intelligent workflows, and unlocks margin-protecting decisions with real-time data and capability. Our products span cross-border, tax, returns, demand planning, and our next-generation agentic storefront, giving merchants full transparency and the ability to act with confidence. At Swap, we’re building a culture that values clarity, creativity, and shared ownership as we redefine how global commerce works.
About the role
We're looking for a Staff Software Engineer in Test to lead the creation and development of Swap's internal QA Platform — a new function whose mission is to build reusable tools and infrastructure that enable our engineering teams to innovate faster and with confidence. You'll be building the internal platform — tools, frameworks, automation pipelines, and AI-powered workflows — that engineers across Swap use every day to ship safely and fast. Your success is measured by adoption, developer experience, and the speed at which teams can deliver quality software.
You will partner with our existing SDET who built the current e2e testing framework, extending its capabilities and building on top of it as part of a broader platform vision. You'll define the strategy, own the roadmap, and make the highest-impact decisions about where to invest the platform's effort.
Responsibilities
- Own QA Platform Strategy & Roadmap: Define the vision, strategy, and roadmap for the QA Platform — what to build, in what order, and why. Prioritise ruthlessly for maximum impact.
- Make high-impact architectural and tooling decisions that shape how quality works across the entire engineering organisation.
- Track adoption, usage, and developer satisfaction. The platform only succeeds if engineers actually use it — driving adoption and engagement is as important as building the tools.
- Build Reusable Quality Tools & Infrastructure: Design and build reusable tools, frameworks, and self-serve quality infrastructure that engineering teams use to ship with confidence — reducing friction to near zero.
- Partner with the existing SDET to extend and scale the current e2e testing framework into a broader platform with wider capabilities.
- Create internal developer-facing tools with excellent DX — documentation, clear APIs, easy onboarding. If it's hard to use, it won't be used.
- Lead AI-Native Quality Tooling: Build agentic e2e testing capabilities — LLM-driven test generation from user stories and acceptance criteria, running in sandboxed environments.
- Develop AI-powered workflows for test generation, edge-case fuzzing, visual regression, contract validation, and exploratory testing.
- Create and maintain a knowledge base of QA best practices, agent skills, MCP servers, and prompt templates that any team can leverage.
- Continuously evaluate and integrate new AI capabilities as models and tooling improve.
- Scale Across the Organisation: Work with every product team to embed quality tooling into their development workflow — making it part of how code is written and shipped, not an afterthought.
- Onboard teams that currently have no QA coverage into the shared quality ecosystem through self-serve tooling.
- Build tools that scale independently of QA headcount — the platform should multiply every engineer's ability to ship quality software, not create dependency on the QA team.
Requirements
- 8+ years of experience in software engineering, test engineering, SDET, or platform engineering roles, with significant time spent building developer-facing tools and infrastructure at scale.
- Experience building internal platforms, developer tools, or shared infrastructure — you understand what makes engineers actually adopt tooling. You've driven adoption and engagement across multiple teams, not just built features nobody used. This is core to the role.
- Strong software engineering fundamentals — you write production-quality code. This role is more engineering than testing.
- Deep expertise in test automation frameworks, CI/CD pipeline design, and quality tooling — you've built these systems, not just used them.
- Experience with modern cloud infrastructure — Kubernetes, containerised test environments, infrastructure-as-code. You're comfortable with the full stack.
- Product thinking for internal tools — you think about your users (engineers), their workflows, and their pain points. You measure success by adoption and impact, not features shipped.
- Technical leadership experience — you've led engineering initiatives, defined roadmaps, made architectural decisions, and influenced practices across multiple teams.
- Strong communication skills — you can articulate technical vision to engineers and business value to leadership.
Strong Preference
- Experience with AI/LLM-powered testing or developer tools — agentic testing, AI-assisted test generation, or building tooling that integrates LLMs into development workflows.
- Experience in e-commerce, fintech, or high-transaction-volume environments where quality has direct business impact.
- Experience working across a full engineering organisation — not just one team, but shaping practices and tooling that affect 10+ teams simultaneously.
Mindset
- You think like a platform engineer — your users are developers, and your product is the tooling they rely on every day.
- You're obsessed with developer experience — quality tools should reduce friction, not add it. If it's not easy, it won't be adopted.
- You believe quality is a system, not a phase — and you want to build that system.
- You're excited about AI as a force multiplier for quality, not threatened by it.
- You default to automation over manual process — if a human has to do it twice, it should be automated.
- You're comfortable with ambiguity and greenfield work — you're building something new, not maintaining something old.
- You prioritise ruthlessly — you'd rather ship one high-impact tool that every team uses than five tools nobody adopts.
Benefits
- Competitive base salary.
- Stock options in a high-growth startup.
- Competitive PTO with public holidays additional.
- Private Health.
- Pension.
- Wellness benefits.
- Breakfast Mondays.
Diversity & Equal Opportunities
We embrace diversity and equality in a serious way. We are committed to building a team with a variety of backgrounds, skills, and views. The more inclusive we are, the better our work will be. Creating a culture of equality isn't just the right thing to do; it's also the smart thing.
Staff SDET in London employer: Swap
Contact Detail:
Swap Recruiting Team
StudySmarter Expert Advice 🤫
We think this is how you could land Staff SDET in London
✨Tip Number 1
Network like a pro! Reach out to folks in your industry on LinkedIn or at meetups. A friendly chat can lead to opportunities that aren’t even advertised yet.
✨Tip Number 2
Show off your skills! Create a portfolio or GitHub repo showcasing your projects and contributions. This gives potential employers a taste of what you can do, especially for a tech role like Staff SDET.
✨Tip Number 3
Prepare for interviews by practising common questions and scenarios related to QA platforms and automation. We recommend doing mock interviews with friends or using online platforms to get comfortable.
✨Tip Number 4
Don’t forget to apply through our website! It’s the best way to ensure your application gets seen by the right people. Plus, it shows you’re genuinely interested in joining our team at Swap.
We think you need these skills to ace Staff SDET in London
Some tips for your application 🫡
Tailor Your Application: Make sure to customise your CV and cover letter to highlight your experience with developer-facing tools and internal platforms. We want to see how your skills align with our mission at Swap!
Showcase Your Impact: When detailing your past roles, focus on the impact you've made in previous positions. Talk about how you drove adoption of tools and improved developer experience — we love seeing results!
Be Clear and Concise: Keep your application straightforward and to the point. Use clear language to describe your achievements and avoid jargon that might confuse us. We appreciate clarity just as much as creativity!
Apply Through Our Website: We encourage you to submit your application directly through our website. It’s the best way for us to receive your details and ensures you’re considered for the role. Don’t miss out!
How to prepare for a job interview at Swap
✨Know Your Stuff
Make sure you’re well-versed in the technical skills required for the Staff SDET role. Brush up on your knowledge of test automation frameworks, CI/CD pipelines, and cloud infrastructure like Kubernetes. Being able to discuss your past experiences with these tools will show that you’re not just familiar with them, but that you’ve actively used them to drive adoption and engagement.
✨Showcase Your Leadership Skills
This role requires strong technical leadership, so be prepared to share examples of how you've defined roadmaps and made architectural decisions in previous positions. Highlight any initiatives you've led that improved developer experience or quality tooling across multiple teams. This will demonstrate your ability to influence practices and drive change within an organisation.
✨Understand the User Perspective
Remember, your users are developers. Be ready to discuss how you think about their workflows and pain points when building internal tools. Share specific examples of how you’ve designed tools with excellent developer experience in mind, ensuring they reduce friction and encourage adoption. This mindset is crucial for success in this role.
✨Embrace AI and Innovation
Since the role involves building AI-native quality tooling, be prepared to talk about your experience with AI-powered testing or developer tools. Discuss any innovative projects you've worked on that utilised AI to enhance quality processes. Showing enthusiasm for AI as a force multiplier for quality will resonate well with the interviewers at Swap.