Senior Quality Engineer
Circle · Wilmington, DE · 1 mo ago
RemoteRemoteQuality Assurance$120k–$130k/yrFull-time
We need to output HTML fragment with sections: About the role, Responsibilities (maybe "What You'll Be Doing"), Requirements (maybe "What You'll Need To Be Successful"), Benefits, Pay (Compensation & Benefits includes compensation range). Also maybe "About Us" but we should not repeat job title. The instruction: Use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). Use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). Use - for any list of duties/requirements/benefits, and
for prose. Do NOT repeat the job title as a heading (the page already shows it) and do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short
or drop it. Preserve ALL substantive information; do NOT invent or summarize away detail. Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. IMPORTANT: include a section ONLY when the posting has real, specific content for it — never emit a heading followed by filler/placeholder text (e.g. "commensurate with experience", "not specified", "N/A", "varies", "TBD") and never create Pay/Schedule/Benefits sections unless the posting actually states them. Prefer a few substantive sections over many thin ones. Output ONLY the HTML fragment — no /, no markdown code fences.
We need to decide which sections to include. The posting includes:
- About Us (company description) – could be considered "About the role"? Actually "About Us" is company description, not role. The instruction says use headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We can include "About the role" maybe summarizing the role description. But we have "About The Role" section in the posting. So we can use that as heading "About the role". Then we have "What You'll Be Doing" which is responsibilities. Then "What You'll Need To Be Successful" which is requirements/qualifications/skills. Then "Compensation & Benefits" includes compensation range and benefits description. Also there is "Bonus points" which could be considered "Skills" or "Qualifications". We could incorporate bonus points into Requirements or Skills.
We should not include sections like Schedule (not mentioned). Pay we can include as part of Compensation & Benefits, but we could separate Pay and Benefits if we want. The instruction says we can use Pay and Benefits headings if posting actually states them. The posting states compensation range and benefits description. So we could have a
Pay
with the compensation range, and Benefits
with benefits description. Or combine into one Benefits section that includes both. The instruction says prefer a few substantive sections over many thin ones. So maybe combine compensation and benefits into one Benefits section. But they gave Pay as possible heading. However they said never create Pay/Schedule/Benefits sections unless posting actually states them. It does state compensation and benefits, so we could have either Pay or Benefits. To be safe, we could have a single Compensation & Benefits
but that's not in the list of allowed headings? The list includes Benefits, Pay. It didn't list "Compensation & Benefits". But we could use Benefits heading and include compensation details inside. Or we could have two sections: Pay and Benefits. That would be more sections but still substantive. The instruction says prefer a few substantive sections over many thin ones. Two sections is fine.
We need to use - for any list of duties/requirements/benefits. So for responsibilities we should list bullet points. For requirements we should list bullet points. For benefits we could list bullet points.
We need to preserve all substantive information, not invent or summarize away detail. So we need to include all details from the posting, but we can format them as prose or lists.
Let's extract content:
About Us Circle is building the world’s leading AI-powered, all-in-one platform for digital businesses. We make it possible for creators, coaches, educators, and businesses to bring together their audience with engaging discussions, live streams, events, chat, courses, and payments — all in one place, all under their own brand. We’re proud to be a fully remote company of around 270 (and growing!) team members from 30+ countries around the world. We seek exceptional individuals around the world, set them up to do the best work of their lives, and in turn, create a meaningful impact in their own lives. We don't track hours, but we do manage for high expectations very closely. We collaborate across time zones, are highly async, and like to document a lot. Twice a year, we bring the whole company together in beautiful places around the world for our company offsites. So far, we’ve hosted offsites in Turkey, Portugal, Mexico, Thailand, Colombia, Italy, Ireland, and more, with still more to come! Check out our Careers page for more about working at Circle.
About The Role We’re looking for a Senior Quality Engineer to help shape how quality is built into our product. Our SQEs work across multiple product teams, partnering with Engineering, Product Leads and Design across different areas of Circle. You’ll get involved throughout the development lifecycle. Exploring ideas, identifying risks, challenging assumptions and helping teams make better decisions about quality. This is a collaborative, hands-on role for someone who enjoys being close to the product, moving between different problem spaces and making Quality Engineering visible across the organisation. You’ll combine strong product thinking, exploratory testing, automation and technical investigation to help teams ship with confidence.
What You'll Be Doing Product Quality Partner with multiple product teams across different areas of Circle. Get involved early in product, design and engineering discussions. Identify meaningful product, technical and customer risks. Bring a quality perspective to user journeys, UI/UX, requirements and technical approaches. Shape pragmatic, risk-based testing approaches based on the change and its potential impact. Automation & Technical Quality Build and maintain reliable automated coverage across web, APIs and integrations. Make thoughtful decisions about what to automate, where to test it and what provides the strongest signal. Investigate complex failures across the application, APIs, CI pipelines and supporting systems. Work with engineers to improve testability, reliability and developer feedback loops. Use modern engineering and AI-assisted tooling where it improves planning, automation, debugging or investigation. Quality Strategy & Enablement Identify recurring or systemic quality issues and drive improvements across teams. Use bugs, production issues and quality signals to improve prevention, not just detection. Help teams make informed decisions about risk, coverage and release confidence. Share knowledge and approaches that strengthen quality ownership across Engineering.
What You'll Need To Be Successful Exceptional written and verbal communication skills in English (CEFR C2 or equivalent), as most collaboration at Circle happens asynchronously. Strong experience working as a Quality Engineer within modern product engineering teams. Strong web test automation experience with Playwright, TypeScript, or comparable technologies. Good knowledge of API and integration testing. Strong exploratory and risk-based testing skills. Confidence reading application code and debugging complex technical issues. Experience with CI/CD pipelines and automated test execution. Strong product judgement. You care about the experience being built, not just whether it technically works. Comfortable working across multiple teams and product areas, switching context and getting up to speed quickly. Able to operate with a high degree of autonomy and identify where your input will create the most value. Confident asking questions, challenging assumptions and influencing decisions constructively. A collaborative and pragmatic approach to balancing quality, risk and delivery.
Bonus points Experience, interest or strong potential in building quality platforms, test infrastructure, automation frameworks, developer tooling or other reusable quality-enabling systems. We’re particularly interested in SQEs who enjoy solving quality problems in scalable ways. Mobile testing, particularly React Native, iOS or Android. Payments or integration-heavy products. Observability and production monitoring. Performance and load testing. CI/CD and build infrastructure. Developer experience or engineering productivity.
Compensation & Benefits Circle offers U.S.-benchmarked compensation globally, equity in the company with ongoing refresh grants, and 35 days of paid time off each year. We’re a remote-only team that comes together twice a year for company retreats in incredible destinations around the world. Alongside incredible flexibility and autonomy, we offer a benefits package that supports health, wellbeing, and professional growth. Learn more in our Candidate Hub. Learn more Candidate Safety & Interview Process NoticeDiversity, Equity & InclusionHow We Use Candidate DataEqual Employment OpportunityVisit our Candidate Hub to learn more about working at Circle, our benefits, and our hiring process. Compensation Range: $120K - $130K
We need to remove boilerplate: "Learn more Candidate Safety & Interview Process NoticeDiversity, Equity & InclusionHow We Use Candidate DataEqual Employment OpportunityVisit our Candidate Hub to learn more about working at Circle, our benefits, and our hiring process." That's boilerplate/legal. Remove.
Also remove duplicated lines: "Learn more" appears twice? Actually there is "Learn more in our Candidate Hub." and later "Learn more Candidate Safety & Interview Process..." We'll keep the first "Learn more in our Candidate Hub." as part of benefits? It's a reference; maybe we can keep it as prose but it's not substantive? It's a pointer to learn more; could be considered boilerplate? Might be okay to keep but it's not essential. The instruction: Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. "Learn more in our Candidate Hub." is not exactly boilerplate but it's a call to action; could be considered application instruction? It's not exactly applying. Might be safe to keep but we could drop it as it's not substantive detail about the role. However we need to preserve ALL substantive information; "Learn more in our Candidate Hub." is not substantive about the role, it's a reference. I'd drop it.
Also "Compensation Range: $120K - $130K" is substantive.
Now we need to format.
We'll have sections:
About the role
- combine About Us and About The Role? Actually About Us is company description, not role. But we could include it under About the role? The instruction says use headings like About the role, Responsibilities, etc. It didn't list About Us. But we could include About the role heading and include both company description and role description? Might be okay. However the About Us is not about the role but about the company. Could we omit it? The instruction says preserve ALL substantive information. The About Us is substantive about the company; we should keep it somewhere. Could we put it under About the role? Might be okay but it's not strictly about the role. However we could create a heading "About the company" but not in allowed list. The instruction says use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It gives examples but not exclusive list? It says "Use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." This suggests we should use those headings when appropriate. It doesn't forbid other headings, but we should follow the pattern. Probably we should stick to those headings. So we need to map content to those headings.
We have:
- About the role: could include the description of the role (the "About The Role" paragraph). The company description could be considered part of "About the role"? Not ideal but maybe we can include it as a brief preamble under About the role.
- Responsibilities: "What You'll Be Doing" with sub-sections Product Quality, Automation & Technical Quality, Quality Strategy & Enablement. We'll list bullet points.
- Requirements: "What You'll Need To Be Successful" plus Bonus points (maybe as Skills). Could split into Requirements and Skills. But we have headings Requirements, Qualifications, Skills. We could use Requirements for the main needed qualifications, and Skills for bonus points? Or combine.
- Benefits: compensation and benefits description.
-
for prose. Do NOT repeat the job title as a heading (the page already shows it) and do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short
or drop it. Preserve ALL substantive information; do NOT invent or summarize away detail. Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. IMPORTANT: include a section ONLY when the posting has real, specific content for it — never emit a heading followed by filler/placeholder text (e.g. "commensurate with experience", "not specified", "N/A", "varies", "TBD") and never create Pay/Schedule/Benefits sections unless the posting actually states them. Prefer a few substantive sections over many thin ones. Output ONLY the HTML fragment — no /, no markdown code fences. We need to decide which sections to include. The posting includes: - About Us (company description) – could be considered "About the role"? Actually "About Us" is company description, not role. The instruction says use headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We can include "About the role" maybe summarizing the role description. But we have "About The Role" section in the posting. So we can use that as heading "About the role". Then we have "What You'll Be Doing" which is responsibilities. Then "What You'll Need To Be Successful" which is requirements/qualifications/skills. Then "Compensation & Benefits" includes compensation range and benefits description. Also there is "Bonus points" which could be considered "Skills" or "Qualifications". We could incorporate bonus points into Requirements or Skills. We should not include sections like Schedule (not mentioned). Pay we can include as part of Compensation & Benefits, but we could separate Pay and Benefits if we want. The instruction says we can use Pay and Benefits headings if posting actually states them. The posting states compensation range and benefits description. So we could have a
Pay
with the compensation range, andBenefits
with benefits description. Or combine into one Benefits section that includes both. The instruction says prefer a few substantive sections over many thin ones. So maybe combine compensation and benefits into one Benefits section. But they gave Pay as possible heading. However they said never create Pay/Schedule/Benefits sections unless posting actually states them. It does state compensation and benefits, so we could have either Pay or Benefits. To be safe, we could have a singleCompensation & Benefits
but that's not in the list of allowed headings? The list includes Benefits, Pay. It didn't list "Compensation & Benefits". But we could use Benefits heading and include compensation details inside. Or we could have two sections: Pay and Benefits. That would be more sections but still substantive. The instruction says prefer a few substantive sections over many thin ones. Two sections is fine. We need to use- for any list of duties/requirements/benefits. So for responsibilities we should list bullet points. For requirements we should list bullet points. For benefits we could list bullet points.
We need to preserve all substantive information, not invent or summarize away detail. So we need to include all details from the posting, but we can format them as prose or lists.
Let's extract content:
About Us Circle is building the world’s leading AI-powered, all-in-one platform for digital businesses. We make it possible for creators, coaches, educators, and businesses to bring together their audience with engaging discussions, live streams, events, chat, courses, and payments — all in one place, all under their own brand. We’re proud to be a fully remote company of around 270 (and growing!) team members from 30+ countries around the world. We seek exceptional individuals around the world, set them up to do the best work of their lives, and in turn, create a meaningful impact in their own lives. We don't track hours, but we do manage for high expectations very closely. We collaborate across time zones, are highly async, and like to document a lot. Twice a year, we bring the whole company together in beautiful places around the world for our company offsites. So far, we’ve hosted offsites in Turkey, Portugal, Mexico, Thailand, Colombia, Italy, Ireland, and more, with still more to come! Check out our Careers page for more about working at Circle.
About The Role We’re looking for a Senior Quality Engineer to help shape how quality is built into our product. Our SQEs work across multiple product teams, partnering with Engineering, Product Leads and Design across different areas of Circle. You’ll get involved throughout the development lifecycle. Exploring ideas, identifying risks, challenging assumptions and helping teams make better decisions about quality. This is a collaborative, hands-on role for someone who enjoys being close to the product, moving between different problem spaces and making Quality Engineering visible across the organisation. You’ll combine strong product thinking, exploratory testing, automation and technical investigation to help teams ship with confidence.
What You'll Be Doing Product Quality Partner with multiple product teams across different areas of Circle. Get involved early in product, design and engineering discussions. Identify meaningful product, technical and customer risks. Bring a quality perspective to user journeys, UI/UX, requirements and technical approaches. Shape pragmatic, risk-based testing approaches based on the change and its potential impact. Automation & Technical Quality Build and maintain reliable automated coverage across web, APIs and integrations. Make thoughtful decisions about what to automate, where to test it and what provides the strongest signal. Investigate complex failures across the application, APIs, CI pipelines and supporting systems. Work with engineers to improve testability, reliability and developer feedback loops. Use modern engineering and AI-assisted tooling where it improves planning, automation, debugging or investigation. Quality Strategy & Enablement Identify recurring or systemic quality issues and drive improvements across teams. Use bugs, production issues and quality signals to improve prevention, not just detection. Help teams make informed decisions about risk, coverage and release confidence. Share knowledge and approaches that strengthen quality ownership across Engineering.
What You'll Need To Be Successful Exceptional written and verbal communication skills in English (CEFR C2 or equivalent), as most collaboration at Circle happens asynchronously. Strong experience working as a Quality Engineer within modern product engineering teams. Strong web test automation experience with Playwright, TypeScript, or comparable technologies. Good knowledge of API and integration testing. Strong exploratory and risk-based testing skills. Confidence reading application code and debugging complex technical issues. Experience with CI/CD pipelines and automated test execution. Strong product judgement. You care about the experience being built, not just whether it technically works. Comfortable working across multiple teams and product areas, switching context and getting up to speed quickly. Able to operate with a high degree of autonomy and identify where your input will create the most value. Confident asking questions, challenging assumptions and influencing decisions constructively. A collaborative and pragmatic approach to balancing quality, risk and delivery.
Bonus points Experience, interest or strong potential in building quality platforms, test infrastructure, automation frameworks, developer tooling or other reusable quality-enabling systems. We’re particularly interested in SQEs who enjoy solving quality problems in scalable ways. Mobile testing, particularly React Native, iOS or Android. Payments or integration-heavy products. Observability and production monitoring. Performance and load testing. CI/CD and build infrastructure. Developer experience or engineering productivity.
Compensation & Benefits Circle offers U.S.-benchmarked compensation globally, equity in the company with ongoing refresh grants, and 35 days of paid time off each year. We’re a remote-only team that comes together twice a year for company retreats in incredible destinations around the world. Alongside incredible flexibility and autonomy, we offer a benefits package that supports health, wellbeing, and professional growth. Learn more in our Candidate Hub. Learn more Candidate Safety & Interview Process NoticeDiversity, Equity & InclusionHow We Use Candidate DataEqual Employment OpportunityVisit our Candidate Hub to learn more about working at Circle, our benefits, and our hiring process. Compensation Range: $120K - $130K
We need to remove boilerplate: "Learn more Candidate Safety & Interview Process NoticeDiversity, Equity & InclusionHow We Use Candidate DataEqual Employment OpportunityVisit our Candidate Hub to learn more about working at Circle, our benefits, and our hiring process." That's boilerplate/legal. Remove.
Also remove duplicated lines: "Learn more" appears twice? Actually there is "Learn more in our Candidate Hub." and later "Learn more Candidate Safety & Interview Process..." We'll keep the first "Learn more in our Candidate Hub." as part of benefits? It's a reference; maybe we can keep it as prose but it's not substantive? It's a pointer to learn more; could be considered boilerplate? Might be okay to keep but it's not essential. The instruction: Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. "Learn more in our Candidate Hub." is not exactly boilerplate but it's a call to action; could be considered application instruction? It's not exactly applying. Might be safe to keep but we could drop it as it's not substantive detail about the role. However we need to preserve ALL substantive information; "Learn more in our Candidate Hub." is not substantive about the role, it's a reference. I'd drop it.
Also "Compensation Range: $120K - $130K" is substantive.
Now we need to format.
We'll have sections:
About the role
- combine About Us and About The Role? Actually About Us is company description, not role. But we could include it under About the role? The instruction says use headings like About the role, Responsibilities, etc. It didn't list About Us. But we could include About the role heading and include both company description and role description? Might be okay. However the About Us is not about the role but about the company. Could we omit it? The instruction says preserve ALL substantive information. The About Us is substantive about the company; we should keep it somewhere. Could we put it under About the role? Might be okay but it's not strictly about the role. However we could create a heading "About the company" but not in allowed list. The instruction says usefor section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It gives examples but not exclusive list? It says "Use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." This suggests we should use those headings when appropriate. It doesn't forbid other headings, but we should follow the pattern. Probably we should stick to those headings. So we need to map content to those headings. We have: - About the role: could include the description of the role (the "About The Role" paragraph). The company description could be considered part of "About the role"? Not ideal but maybe we can include it as a brief preamble under About the role. - Responsibilities: "What You'll Be Doing" with sub-sections Product Quality, Automation & Technical Quality, Quality Strategy & Enablement. We'll list bullet points. - Requirements: "What You'll Need To Be Successful" plus Bonus points (maybe as Skills). Could split into Requirements and Skills. But we have headings Requirements, Qualifications, Skills. We could use Requirements for the main needed qualifications, and Skills for bonus points? Or combine. - Benefits: compensation and benefits description. -