Senior Quality Engineer

About apexdynamics.io LLC

avexpdynamics.io LLC is a software company headquartered in Saint Petersburg, Florida, with operations in Gersau, Switzerland and New York. We build long-horizon technology infrastructure for business owners in regulated, high-trust industries. Our work is referral-based, our clients are senior, and the bar for what we ship is set by the people who put their names on the outcome.

We work in measured tones: we build for permanence, not for speed of headline. The technology we build is meant to outlast the contract that paid for it.

About Velocity

Velocity is our multi-ISV platform for assessment, training, and coaching businesses. Today it serves leading European Independent Software Vendors and is being built to compliance-by-design standards from day one — DSGVO/GDPR, the EU AI Act, and DIN psychometric standards are non-negotiable from the first commit.

The platform is multi-tenant by design, with strict tenant isolation, immutable audit evidence, and an underlying ontology of five universal primitives — Subject, Concept, Instrument, Observation, Agreement — that allows new ISVs and assessment domains to be onboarded by configuration rather than by schema migration.

The role

This is the senior quality role on the team. You will own the quality discipline of the Velocity platform end-to-end — the automation that keeps the bar high, the mentoring that lifts the engineers around you, and the structured feedback loop into architecture that keeps engineering, architecture, and business in alignment.

The role is deliberately positioned as a peer to the technical lead, not a downstream verifier. You are not the last gate before release; you are one of the senior voices that shapes how we work, what we measure, and where we invest engineering attention.

You report directly to the founder. This is a deliberate structural choice to protect the neutrality and objectivity of quality findings — your observations reach the business without being filtered through the engineering chain. Operationally, you collaborate as a peer with Carlos, our technical lead based in Colombia, on architecture and quality decisions.

What you will own

• Designing and operating the platform's quality automation — GitHub Actions pipelines, Playwright (or other) end-to-end suites, contract and integration testing across .NET 8 backend services and Angular frontends, and the AI-assisted review tooling that augments human code review.
• Defining the quality bar that PRs must clear before merge, and the discipline that keeps that bar from drifting.
• Building the regression and quality-gate scaffolding that lets the team ship faster — not slower — as the platform grows.
• Mentoring the backend and frontend engineers on the team. From the patterns you observe in real PRs, real bugs, and real production incidents, you give actionable, specific, kind feedback that helps each engineer improve their craft.
• Closing the loop with the technical lead. Quality findings that point to architectural drift, contract erosion, or process inefficiency are surfaced — with evidence — to keep architecture, engineering, and business goals aligned. You challenge where challenge is warranted.
• Reporting directly to the founder on quality posture, recurring patterns, and the platform's overall risk profile, with a cadence and format we will agree together.

What you bring

Required

• Senior-level experience as a Software Development Engineer in Test (SDET) or Quality Engineer, with a real full-stack development background — you have shipped production code, not only tested it. This is non-negotiable: the mentoring side of the role only works if your feedback is grounded in the lived experience of having built, broken, and fixed real systems.
• Demonstrated experience across multiple working environments, languages, and configurations — the kind of breadth that lets you recognize patterns and anti-patterns quickly across stacks you may not have written in yourself.
• Practical command of the modern .NET stack (C# / .NET 6 or newer, ASP.NET Core, EF Core or Dapper) and the modern Angular stack (Angular 17+, TypeScript, RxJS) at a level where you can read, review, and meaningfully improve code in both.
• Strong test automation engineering: Playwright (or equivalent) for end-to-end, xUnit / NUnit / Jest / Jasmine for unit and integration, contract testing, performance testing where relevant.
• Deep CI/CD experience on GitHub Actions — not just consuming pipelines, but designing them: quality gates, branch protection, parallelization, artifact and reporting strategy.
• Comfort with multi-tenant SaaS testing concerns: tenant isolation verification, row-level security validation, idempotency and replay testing, regulated-data handling.
• Solid command of test data strategy, observability, and the realities of debugging distributed systems.
• Clear written English, used daily in code review, structured feedback, and asynchronous decision-making. The mentoring component requires written communication that is direct, specific, and respectful.

Strongly preferred

• Practical experience with AI-assisted engineering tools — Claude Code, Copilot, Cursor, or similar — used in real production work, with an opinion on where they help and where they don’t.
• Experience designing AI-assisted code review and quality automation (rule sets, evaluation pipelines, review-augmentation tooling).
• Exposure to regulated workloads (GDPR, EU AI Act, HIPAA, financial regulation) and the testing discipline that comes with them.
• Experience with chaos / fault-injection testing, performance and load testing, or formal contract testing tooling.

How we work — AI-first engineering

We are an AI-first engineering team. Our developers use Claude Code as a primary tool inside a structured SDLC: estimate, spec, build, review, ship. Quality automation is a first-class part of that loop, not a bolt-on afterwards.

Practically, this means we automate everything where automation makes sense — boilerplate, scaffolding, test generation, repetitive refactors, documentation, and code review assist — so that the engineers on the team spend their attention on the parts that actually matter. Your role sits at the heart of this discipline: the quality automation you build is what gives us the confidence to move fast without breaking the things our customers depend on.

If you are open to working this way, you will be given real ownership in shaping how we evolve the AI-first quality method itself. This is not a passenger seat.

How we work — culture

Five behaviours are the core of how we operate together:

• Accountability — we say what we will do, and we do it.
• Responsibility — when something is ours, it stays ours until it is done.
• Transparency — we surface problems early, in writing, with evidence.
• Respectful communication — we disagree with ideas, never with people.
• Customer-first thinking — every decision is filtered through what the customer will experience.

We learn from our mistakes continuously, and we support each other in getting better. There is no lone-wolf culture here. Senior people on this team make the people around them better, by default. For a QA mentoring role, that last sentence is the entire job description compressed.

How engagement and payment work

We work in agreed work packages. For each package, we estimate the effort together with you and validate the estimate jointly before you start. The validated estimate is what you are paid for — no scope inflation, no after-the-fact renegotiation.

You can choose between three contract models. Pick the one that fits your situation; all three are real options.

Option A — Fixed monthly retainer plus quality bonus

A fixed monthly rate, agreed up front and paid on a regular schedule. On top of the base rate, you earn a quality bonus tied to objective indicators of platform quality posture (defect escape rate, regression incidence, mean time to detection, customer-warranty performance of features that passed your gates).

This model fits engineers who want predictable income and treat quality as a craft worth being rewarded for.

Option B — Per work-package 60 / 40 split

For each agreed work package, the validated estimate is your fee. It is paid in two parts:

• 60% when the work package reaches the QA Tech Passed gate (the work is delivered, reviewed, and accepted by the technical quality gate).
• 40% after the delivered work has been in production for 30 consecutive days with zero customer support tickets attributable to it.

There is no quality bonus on this model — the warranty mechanism itself is the quality incentive.

Option C — Hourly rate

A straight hourly contractor rate, agreed up front, invoiced against tracked hours on agreed work packages. No retainer floor, no warranty deferral, no quality bonus. This model fits engineers who prefer the simplest possible commercial structure and full elasticity on weekly hours.

All three options apply per engagement; we will agree which model applies before we start working together, and the model can be revisited at the start of any new engagement window.

Workload and time commitment

The initial workload will be higher — there is real setup work to get the quality automation, pipelines, and feedback loops running properly. After that initial period, we expect the steady-state commitment to be approximately 10–15 hours per week, adjusted as the platform grows.

This is a part-time, long-horizon engagement. It is not a substitute for a full-time role and we are not looking for someone whose attention is fully consumed by it. The right candidate will be working on other interesting things and will treat this engagement as one of them.

Working conditions

• Fully remote. We do not run an office for engineering.
• Fully flexible hours. We care about delivery, not the clock.
• Working language: English. You will collaborate in writing every day, so written English needs to be clear and professional.
• We are looking for engineers based in Latin America (Central and South America).
• Daily standup attendance is part of the role — the mentoring component depends on you being present in the team’s rhythm.
• Reporting line: directly to the founder, for neutrality and objectivity of quality findings.