Blog
Working as a Mobile QA at Engine: In conversation with Rachel Haszeldine
By Team Engine
Firstly, tell us a little bit about you and how you became a Mobile QA (or QA in general)
After leaving university, I completed a graduate scheme at a mobile app and website consultancy; this was a fantastic opportunity to rotate around different areas of the business, discover more about the software development lifecycle and to have my first experience of the role of a QA. It felt like a natural fit for me; I enjoyed the opportunity to contribute to requirement building, help shape different products and see them come to life, all while advocating for high quality - I’ve been enjoying working as a QA ever since
What does a typical day look like as a Mobile Product QA at Engine?
Every day is different at Engine, which makes working here exciting. A typical day would be kicked off with a morning stand-up, where we discuss what we’re working on and any blockers. After that, I could be doing anything from testing new features to triaging potential defects, writing automated tests or discussing upcoming feature requirements with the team.
Tell us the most exciting thing about being a Mobile Product QA at Engine
We’re lucky to work with some awesome clients at Engine, so it’s great when we receive positive feedback from them and particularly exciting to see what we’ve built in the hands of our end users! From a QA perspective, it’s always satisfying to identify the cause of obscure defects or to expand my knowledge around a new test tool
What would you like to tell anyone looking to join Engine as a Mobile Product QA or a Tech role in general at Engine?
Engine is the perfect place to develop your skill set, work on cool projects and learn from a talented group of people. It’s a place where we learn and grow together, so you’ll have the opportunity to influence how we do things.
What is the one piece of advice / guidance you’d have given yourself on your first day as a QA?
Be inquisitive and don’t be afraid to ask questions.