What we’re looking for

The Quality Platform team is looking for a Software Engineer passionate about software quality and test automation. We are a small team dedicated to supporting the tooling and infrastructure that help our engineering teams write, execute, and report on tests. You’ll have the opportunity to debug test automation issues with fellow engineers and build metric dashboards to help report on product quality. 

What you’ll be working on

• Creating and maintaining automation frameworks.
• Developing tools to aid in testing.
• Building and developing dashboards for reporting metrics.
• Helping engineers debug issues with test automation.
• Advising teams on test strategy.
• Collaborating with a talented team of engineers to build high-quality products.

We’d love to hear from people with

• 2-4 years of role-related experience.
• Proficient in both JavaScript and Python.
• Experience with building tools to aid in testing or development.
• Experience with SDET tools such as Selenium, Webdriver.IO, PyTest.
• Experience with logging tools and dashboarding, such as Splunk and Grafana.
• Experience with CI/CD methodologies.
• A data-driven, growth mindset in the approach to self-development and problem-solving.
• Experience with React, GitHub Actions, or AWS Timestream preferred.

SurveyMonkey believes in-person collaboration is valuable for building relationships, fostering community, and enhancing our speed and execution in problem-solving and decision-making. As such, you will be required to work from our Amsterdam office up to 1 day per week.

#LI-Hybrid

We're building an AI copilot for web testing automation. It enables manual and automation QA engineers to turn their manual testing flows into production-ready automated E2E testing scripts, saving hours of manual work and coding. We are a small team with zero bureaucracy, focusing on real users. We optimize for shipping value - not hype.

About the role:

You'll own the top of the funnel: outbound, qualification, and getting leads to sit down for a conversation. Demos, onboarding, and retention are staying with the founder for now.

Phase one: Get individual Automation QAs to try the product, aiming for fast adoption and no procurement. Once we hit 20+ weekly users, we’ll move on to phase two, where we’ll shift the focus to B2B – qualified meetings with QA Leads and Engineering Managers.

Your focus in the first three months:

• Build targeted lists: Automation QAs at companies with web products and Playwright, Cypress, or Selenium in their stack.
• Run outbound sequences (LinkedIn is the baseline, but you decide the channels). A/B test weekly.
• Design qualification gates (forms and scoring) to filter leads before the founder calls.
• Reach 20+ weekly active users after month one – ICP-qualified and giving direct feedback to engineering.
• Document what works into a repeatable playbook.

Growth path:

This role expands as your strategies deliver results. Once the user pipeline works, you can take over demos and run B2B sales end to end. From there, the natural next step is Growth Lead (funnel optimization and scaling the playbook) or Account Executive (owning deal execution).

Why to join:

• You'll be building a strategy that scales the product, not filling a quota. What you create from scratch becomes the foundation.
• Your outreach turns into users who talk directly to engineering, and their feedback ships as features within days.
• AI for developer tools is a market with real pull, and QA automation is one of its sharpest pain points.
• We’re backed by JetBrains – financially secure with no reliance on external VC funding.

Who we're looking for:

You should have a high level of agency and be quant-minded – you live in funnel metrics, run experiments, and are comfortable saying "no" to leads that are a bad fit. 

The ideal candidate will:

• Have done 0-to-1 outbound for an early-stage devtool, QA tool, infrastructure product, or similar.
• Have proven cold outbound results, instead of being dependent on warm inbound.
• Be able to talk credibly about flaky tests, CI pain, and Playwright vs. Cypress. You don't need to be an engineer, but you do need domain empathy.
• Possess strong written communication skills, with the ability to craft short, sharp messages that get replies.

Nice to have:

• A QA or SDET background – you've felt the pain yourself before moving to sales or BD.
• Exposure to security/compliance objections – enough to pre-empt and route.
• Content skills – your LinkedIn posts get engagement, not just your DMs.
• Experience as one of the first 10 employees at a startup.

#LI-REMOTE 
#LI-KT1