QA Engineer (Data Team)

As a QA Engineer on the Data Team at Sweed, your primary responsibilities include developing and executing end-to-end test scenarios for reporting features, ensuring feature implementation aligns with business requirements, performing regression testing during releases, and supporting the release process. Your role is integral in maintaining the quality of our software, particularly in ensuring that data flows accurately across the pipeline, from raw data to insightful analytics.

To join Sweed as a QA Engineer for the Data Team, you should have at least 3 years of experience in Quality Assurance and/or Data Quality, along with proficiency in SQL and experience in UI manual testing. Familiarity with tools like Postman, strong communication skills, and a willingness to work with data are important as well. If you have additional skills such as knowledge of ETL, ELT, or ClickHouse, that would be advantageous too!

The QA Engineer role at Sweed is crucial in upholding our mission to provide quality cannabis retail solutions. By ensuring that our software performs flawlessly and meets customer expectations, you help foster trust and reliability among our users. Your efforts in testing and validating data directly contribute to our ability to launch new features that enhance the customer experience and promote the medicinal benefits of cannabis.

At Sweed, the QA Engineer will be part of a cross-functional team typically consisting of 10-12 members, which includes front-end and back-end engineers, QA specialists, and analysts. Each team has a dedicated product owner who guides the project, ensuring that every aspect functions cohesively and effectively to meet our users' needs and expectations.

As a fully remote company, Sweed offers a dynamic and flexible work environment for our QA Engineers. You can enjoy flexible working hours, with core hours generally set between 09:00 and 15:00 GMT. This encourages a work-life balance that can adapt to your needs while ensuring collaboration among your team members in various time zones.

In your answer, highlight specific examples of how you've used SQL in previous projects for querying databases, validating data integrity, or running regression tests on reporting functionalities. Discuss your proficiency level and how it will enable you to ensure the quality of data that flows through Sweed’s systems.

Employ the STAR method to structure your response. Describe a situation where you had competing deadlines, the task you undertook to prioritize your workload—perhaps using tools or frameworks for task management—and the results of your focused efforts in delivering quality outcomes for your projects.

Share your knowledge of testing methodologies such as Black Box, White Box, and Risk-Based Testing. Explain how you would implement these methodologies in a data-centric role at Sweed, ensuring comprehensive test coverage for data pipelines and reporting features.

Detail a specific instance where you discovered a significant bug, the investigative steps you took to diagnose the issue, and the communication process you followed to report it. Highlight the impact of solving the issue on the project and any lessons learned moving forward.

Discuss your approach to reviewing requirements and collaboration with stakeholders to establish clear definitions for metrics. Detail any tools or methodologies you use to verify data accuracy and alignment across different datasets in your testing.

Provide examples of your past projects where manual UI testing was crucial. Be sure to mention the tools used (like Postman) and how you evaluated user experience alongside functionality to ensure a seamless interface.

Articulate the importance of regression testing as a practice for ensuring that new code changes do not adversely affect existing features. Share examples of how regression testing has saved time and resources during your previous projects by catching potential issues early in the development cycle.

Focus on your experience with agile methodologies or similar frameworks that emphasize collaboration. Discuss how regular stand-ups or feedback loops contribute to improved communication, and provide specific examples of how you facilitate discussions around quality assurance processes.

Describe your approach to lifelong learning, such as following industry blogs, participating in webinars, and attending conferences. Share how staying informed enables you to apply the latest best practices in quality assurance to your role at Sweed.

Show that you have done your homework on the cannabis industry. Discuss unique challenges, such as state-level regulations and metrics significant to cannabis retail, and how this knowledge influences your testing strategies and focus areas in maintaining data integrity and compliance.