We are looking for a Product Engineer who sits between how something is built and why it's being built. This person will spend real time with the people closest to our customers, help decide what we build, and then go and build it.
Quality at Snapplify sits with the experts in each area of the product rather than with a separate function. This role is central to that: you'll know your part of the product better than anyone, and you'll be accountable for it being good.
A large part of that is test design and automation. Quality is owned by the experts in each area, but they need help getting their test cases to a point where they can actually be automated - and that's you. You'll work across the whole company raising the standard of how test cases are written, and then you'll be the one who automates them, writing the Cucumber scripts and Playwright implementation behind them. You own that chain end to end, from the test case to the suite running green.
If you are a person who:
- Has a functional home office environment (reliable internet access and backup power) for remote working
- Can take an idea from a customer conversation all the way through to shipped
- Is comfortable writing production code, and comfortable sitting in a customer call
- Has a strong understanding of testing methodologies and where quality actually comes from
- Can write a test case precise enough to automate, and then go and automate it
- Can teach that skill to people outside engineering without being condescending about it
- Is familiar with the software development lifecycle (SDLC) and software testing lifecycle (STLC)
- Uses AI tooling seriously and critically - you get real leverage from it, and you know exactly where it can't be trusted
- Can analyse complex issues and drive data-driven decision-making
- Has strong verbal and written communication skills, with the ability to explain complex technical issues to non-technical stakeholders
- Has excellent interpersonal skills, with the ability to build strong relationships across the organisation
- Has attention to detail and a commitment to quality and accuracy
- Has a strong bias towards action
- Chooses to learn and strives for mastery
- Gets things done and takes accountability
- We can work with and shares the same vision and mission as we do
So, if the above describes you - read on to find out what will be required of you and what will impress us. Some of the tools we use (but not limited to):
- Kotlin, Java and Spring Boot
- Thymeleaf
- MySQL and Hibernate JPA
- Jira and Xray
- Bitbucket
- JUnit, Cucumber and Playwright
- Postman
- Claude Code and other AI development tooling
- Google Suite (Gmail, Drive, Docs, Sheets)
- Freshdesk
- Slack
What will you be required to do?
Customer and Product Understanding
- Work directly with Customer Success, Sales and Adoption to understand what customers hit, what they ask for, and where they stall
- Sit in on support conversations, demos and onboardings to see the product as customers experience it
- Look at usage data to understand what's actually being used and what isn't
Product Definition and Planning
- Turn what you learn into clear, well-scoped work the team can build
- Take part in prioritisation and roadmap conversations, and be willing to disagree in them
- Break work down into tasks and estimations
- Define what "done" looks like before the work starts
Development and Delivery
- Contribute directly to the codebase alongside the development team
- Follow features through to release, and then check whether they actually solved the problem
- Work in a peer code-reviewed environment. You review my code, I review yours
Test Design and Quality Ownership
- Set the standard for how test cases are written in Jira and Xray - unambiguous, atomic, and complete enough to automate
- Work with teams right across the company to bring their test cases up to that standard, coaching rather than doing it for them
- Review test cases before they're accepted as automation-ready
- Automate those test cases once they're ready - writing the Cucumber scripts and the Playwright step definitions behind them
- Keep the automated suite healthy, meaningful and trusted as the product changes
- Own the quality of your area of the product, including the tests that prove it works
- Make sure quality input happens early in the development cycle, not at the end
Cross-Departmental Collaboration
- Act as the bridge between the commercial teams and engineering, in both directions
- Communicate risks, trade-offs and status to stakeholders clearly and early
Continuous Improvement
- Identify gaps and inefficiencies in how we work, and do something about them
- Maintain updated knowledge of industry trends and advancements
What skills/knowledge and experience will impress us?
- Bachelor's degree in Computer Science, Information Technology, Engineering, or a related field is advantageous
- Experience across both product and engineering - you've shaped what gets built, not only built it
- Hands-on development experience in Kotlin or Java, with Spring Boot
- Good SQL and relational database experience
- Strong testing background - test design and management in Jira and Xray, unit testing with JUnit, and hands-on test automation with Cucumber and Playwright
- Experience building and maintaining an automation suite over time, not just writing the first hundred tests
- Experience writing test cases in Gherkin, or in a style that translates cleanly into it
- Experience with various delivery methodologies (e.g. Agile, Scrum) and tools (e.g. Jira, Bitbucket)
- Genuinely effective use of AI tooling such as Claude Code
- Experience in E-Reading or E-Readers
What can you expect working at Snapplify?
- Competitive salary
- A flat organisational structure with a focus on teamwork and continuous learning
- A fast-paced and challenging environment that will keep you on your toes
- An environment where your input and ideas matter
- Really smart and fun colleagues
