Cookies & analytics consent
We serve candidates globally, so we only activate Google Tag Manager and other analytics after you opt in. This keeps us aligned with GDPR/UK DPA, ePrivacy, LGPD, and similar rules. Essential features still run without analytics cookies.
Read how we use data in our Privacy Policy and Terms of Service.
π€ 15+ AI Agents working for you. Find jobs, score and update resumes, cover letter, interview questions, missing keywords, and lots more.

JetBrains β’ Berlin, Germany
Role & seniority
Stack/tools
Outreach: LinkedIn (baseline), multi-channel experimentation
QA/stack context: Playwright, Cypress, Selenium; CI/ flaky tests domain
Qualification: forms, scoring, data-driven process
Communication: strong written messaging; build repeatable playbooks
Top 3 responsibilities
Build ICP-based targeted lists and run outbound sequences; A/B test channels weekly
Design and implement qualification gates (forms/scoring) to filter leads before founder calls
Drive early user growth to 20+ weekly active users and capture feedback to inform engineering
Must-have skills
Proven 0-to-1 outbound experience for an early-stage devtool/QA tool or similar
Demonstrated cold outbound results; comfortable with saying no to ill-fit leads
Credible discussion of flaky tests, CI pain, and differences between Playwright vs. Cypress
Strong written communication; craft concise messages that elicit replies
Nice-to-haves
QA/SDET background or direct QA tooling experience
Experience handling security/compliance objections
Content/creator skills (engaging LinkedIn posts, not just DMs)
Prior early-stage startup experience (one of first 10 employees)
Location & work type
Location not specified; remote-friendly option likely
Full-time role; phase-one focus on individual QAs, later B2B expan
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.
We process the data provided in your job application in accordance with the Recruitment Privacy Policy.