Quality Engineer

Job Description

Job Description

SDET – Software Development Engineer in Test

KNOWiNK — St. Louis, Missouri (An On-site Role)

At KNOWiNK, we build technology that powers elections across the country. That means quality isn't just a nice to have — it's everything. We're looking for an SDET who lives at the intersection of engineering and testing, someone who thinks in code, cares deeply about coverage, and wants to build automation that actually makes a difference. If you're the kind of person who gets excited about finding a bug before it ships, you're going to fit right in here.

What you'll be doing

• Design, build, and maintain automated test frameworks and test suites across web, mobile, and API layers
• Write clean, reusable test code that integrates smoothly into our CI/CD pipelines
• Collaborate with developers and product early in the cycle to identify testability gaps and build quality in from the start
• Perform manual and exploratory testing when automation isn't the right tool for the job
• Own defect documentation and tracking from discovery through resolution
• Contribute to code reviews on test automation with an eye for maintainability and coverage
• Support performance and regression testing efforts across releases and hotfixes
• Help maintain and improve QA documentation, standards, and processes as we grow

What we're looking for

2-4 years of SDET or test engineering experience

Solid programming skills in Python, JavaScript, Java, or similar

Hands-on experience with automation frameworks like Selenium, Cypress, or Playwright

Experience integrating tests into CI/CD pipelines

API testing experience with tools like Postman or REST Assured

Comfortable working in Agile/Scrum environments

Strong analytical thinking and sharp eye for edge cases

Clear communicator who collaborates well across engineering and product

Nice to have

• Experience with performance testing tools like JMeter, K6, or LoadRunner
• Mobile testing experience on iOS and/or Android
• Familiarity with security testing practices
• Exposure to cloud platforms like AWS, Azure, or GCP
• Experience with Docker or containerized test environments
• Background in elections tech, civic tech, or similarly high-stakes software

What success looks like

First 90 days

You understand our product, our stack, and our testing gaps, and you're already writing automation that matters

First 6 months

Your test coverage contributions are measurably reducing regression time and catching bugs earlier in the cycle

First year

You're a core part of how quality gets built into our product, not just validated at the end

Sound like you? We'd love to hear from you.

Write a LinkedIn post for this ↗