QA & Operations Automation Engineer

ABOUT PSYNTH

Psynth builds the software psychologists use to write assessment reports. A neuropsychological or forensic evaluation can cost a clinician 8–12 hours of writing after the testing is complete. We give most of that time back—without ever allowing the model to originate a diagnostic conclusion or invent a number.

More than 380 clinicians across the US, Canada, and the UK pay us for this software. Real revenue, real users, no VC theater. We’re a small team: three engineers, a QA specialist, an SRE, and the CEO.

We intend to operate at the avant-garde of startup technology. That means using AI and automation as real production leverage, building quickly without becoming careless, and treating internal excellence as part of the product—not as administrative work to clean up later.

WHY THIS ROLE EXISTS NOW

Our vision is large, and there are not enough hours in the day to pursue it at the standard we expect.

We’re building quickly. That creates two compounding needs: more capacity to protect product quality and a dedicated engineer focused on making the company itself more efficient. If we allow testing, operational handoffs, or disconnected systems to remain manual, they will become constraints on everything else we want to build.

This role exists to prevent that.

It is a deliberate 50/50 combination of QA automation and operations engineering. You’ll help us ship reliable software, then apply the same engineering discipline to the workflows behind the company: APIs, data flows, CRM and marketing systems, engineering tools, and internal operations.

If you want a narrow testing role, this isn’t it. If you like understanding whole systems, finding where time and reliability are being lost, and building the automation that fixes both, it may be a very good fit.

WHAT YOU’LL OWN

~50% — QA automation

- Design, implement, maintain, and debug E2E and API tests using Playwright and TypeScript.

- Turn product requirements and code changes into risk-based coverage and regression plans.

- Own test-suite health: architecture, fixtures, helpers, test data, coding standards, and maintainability.

- Investigate flaky and failed tests, distinguishing product defects from automation, data, environment, and infrastructure problems.

- Modify GitHub and CI/CD workflows, analyze test runs, and shorten the path from failure to root cause.

- Validate APIs, requests, responses, integrations, and underlying data; use SQL to prepare and investigate test data.

- Communicate quality risks clearly and help Engineering and Product decide what matters most.

~50% — Operations engineering

- Build and maintain API-first workflows across engineering, product operations, CRM, marketing, sales, and reporting systems.

- Connect tools such as GitHub, Linear, CRM platforms, advertising platforms, and internal systems.

- Automate audience syncing, conversion-data plumbing, pipeline operations, reporting, and cross-functional handoffs.

- Choose the right implementation for the job: Make, custom TypeScript scripts, agents, or direct API integrations.

- Design for production, not demos: logging, observability, retries, failure handling, data integrity, and recovery.

- Eliminate manual data entry and create a clearer connection between business metrics and technical execution.

- Identify operational debt before it becomes organizational drag.

HOW WE WORK WITH AI

We are an AI-heavy shop—not aspirationally. Our engineers use agents in their daily work, and this role is expected to do the same.

- You’ll use AI to accelerate test design, code generation, maintenance, debugging, root-cause analysis, and workflow development.

- You’ll build systems that verify output rather than trusting generated code because it looks plausible. In QA especially, an unverified generated test can create more confidence than truth.

- You do not need to have mastered every AI-native workflow today. You do need the appetite and judgment to become independently productive with them quickly.

If AI tooling is something you merely tolerate, you’ll probably be unhappy here. If you see it as a way to increase both speed and rigor, we should talk.

WHAT YOU NEED

- Strong hands-on experience with TypeScript, APIs, webhooks, and system integrations.

- Production experience building and maintaining test automation with Playwright, or deep experience with a closely related modern framework and the ability to ramp quickly.

- A practical understanding of E2E and API testing: what deserves coverage, what does not, and how to keep a suite trustworthy.

- Confidence with Git, GitHub, CI/CD pipelines, databases, and SQL.

- The ability to troubleshoot across application code, tests, third-party APIs, data, environments, and infrastructure.

- Experience building real workflows with Make, custom scripts, agents, or comparable automation tools.

- Evidence that you have personally owned automation after launch—not only built a happy-path prototype and handed it off.

- Clear written and spoken English. You’ll work across Engineering, Product, and go-to-market functions.

- Independent prioritization based on risk, impact, and criticality.

NICE TO HAVE

- CRM integrations, ad-platform audience syncing, conversion APIs, or revenue-operations automation.

- Accessibility, performance/load, integration, or security-testing experience.

- Observability and self-healing patterns for automated workflows.

- Experience stabilizing a flaky or slow test suite.

- Work in a small, fast-moving product company where the boundaries between systems and functions were not tidy.

WHAT SUCCESS LOOKS LIKE

Within your first six months, you will have:

- Taken meaningful ownership of suite health and made automated results more trustworthy.

- Improved coverage around our highest-risk product journeys and APIs.

- Reduced recurring failures and shortened the path from failed run to root cause.

- Shipped multiple cross-functional automations that remove meaningful manual work.

- Made important operational workflows more observable, resilient, and maintainable.

- Given the rest of the team more time to build by removing work that software should be doing.

TERMS

- $2,500 USD per month for the first 60 days, increasing to $3,000 USD per month thereafter. Independent contractor, paid in USD through Deel. No equity.

- Remote, South America. Argentina preferred but not required.

- Be reachable and responsive on Slack from 9:00 a.m. to 5:00 p.m. Eastern Time. This is a responsiveness window, not a seat-time requirement. Get the work done, communicate clearly, and be available to the team when needed.

- You’ll report to the Lead Engineer and work closely with Engineering, Product, and the CEO on quality and company-wide automation priorities.

- Psynth is HIPAA-compliant and SOC 2 oriented. You’ll learn the practical data and security boundaries in week one.

HIRING PROCESS

1. Introductory call

2. Untimed take-home assessment

3. Team call

4. Offer

The assessment is unpaid, self-contained, and is not work product for Psynth. Candidates may take the time they need to complete it. We’ll share the scope and expectations in advance.

HOW TO APPLY

Apply through LinkedIn with your résumé or profile and one concise example of an automation you personally owned. It can be a test framework, API integration, operational workflow, repository, or technical case study.

Tell us:

1. What problem you were solving.

2. What you personally designed or built.

3. How you handled failures, edge cases, or maintenance.

4. What improved as a result.

• No polished portfolio is required. We care about evidence of ownership and engineering judgment.