Quality Engineer - Automation

InfoTrust is a global, privately-owned products and solutions company dedicated to unlocking the power of data to drive marketing performance and business growth. We specialize in digital analytics, media enablement, and privacy-centric solutions that help Fortune 100–500 companies and the world’s largest brands optimize their marketing strategies. Our culture is built on passion, ownership, diversity, trust, respect, and continuous growth—values that have earned us multiple “Best Places to Work” awards, including a Great Place to Work certification 7 years in a row.

About the role

InfoTrust is growing a portfolio of enterprise SaaS products, and we want quality built into how we develop them, not checked at the end. As a Quality Engineer – Automation, you’ll join our quality engineering team inside R&D. You’ll own test planning and automated testing for your assigned features, and you’ll help build the shared frameworks, standards and CI/CD integration the whole team uses to test our products across the UI, APIs, services and data.

This is a hands-on individual contributor role reporting to Engineering leadership. Leadership sets your main product focus when you’re hired. You’ll work closely with other quality engineers, engineering managers, developers, DevOps and product teams. The goal is simple: catch defects before they reach production, not after.

In your first 90 days you’ll learn our products, architecture and shared frameworks. Then you’ll start building automated tests for your features. By day 90, your releases will ship against a complete test plan, with your tests running in the pipeline.

What you'll do

• Write the test plan for every feature you own before it ships. You’ll document and plan test cases with engineering managers and developers so each release is fully covered.
• Design, build and maintain automated functional, regression, performance and API tests for your features, using the team’s shared frameworks.
• Validate and query data in SQL and NoSQL databases to set up test data, check results and troubleshoot.
• Monitor test results, analyze failures and report issues with diagnostics clear enough for the team to act on quickly.
• Help extend the team’s test automation frameworks so they stay scalable and maintainable as our products grow.
• Integrate automated tests into CI/CD pipelines so every change is validated on its way to production.
• Work with other quality engineers, developers, DevOps and product teams to cover microservices and cloud-based architectures without gaps or duplicated work.
• Follow the team’s testing standards, propose improvements to them, and advocate for testability and engineering best practices across the development lifecycle.

Qualifications

• 2-5 years of test automation experience on web, API or cloud-based systems
• Bachelor’s degree in Computer Science, Engineering or a related field
• Solid grounding in software testing principles, QA methodologies and the SDLC
• Strong programming skills in JavaScript and Node.js
• Experience with AWS or GCP
• Strong knowledge of relational and NoSQL databases, including writing SQL
• Hands-on experience with CI/CD and version control, including Git
• Experience with test automation frameworks such as Selenium, Mocha, Jest, Cypress or Playwright; API testing tools such as Postman or REST Assured; and CI/CD platforms such as Jenkins, GitHub Actions or Azure DevOps (equivalent tools are welcome)
• Strong analytical and problem-solving skills, attention to detail, and a drive to keep improving
• Excellent communication and teamwork skills
• Bonus: experience with Docker or Kubernetes, infrastructure as code and cloud test environments, performance testing tools (JMeter, Locust), or observability tools (Datadog, Prometheus)

You’ll love this role if you’d rather catch a bug before release than explain it after, you like turning repeatable checks into automation that scales, and you see quality as part of engineering, not a gate at the end.

It may not be the right fit if you expect testing to start only after development is done, you want to stay in one layer of the stack, or you’d rather build everything your own way than work within shared team frameworks.