// quality engineering · test automation · AI-assisted QA

Pedro Botter
Bondezan

Quality treated as engineering: risk-based test strategy, end-to-end automation and generative AI applied to the QA process.

I define QA standards, architect automation frameworks and integrate test suites into CI/CD pipelines in enterprise environments across different industries — with traceability from requirement to defect.

  • Playwright · Cypress · Selenium
  • Python · JavaScript · C# · Java
  • GitHub Actions · Azure Pipelines · Docker
  • k6 · Grafana
  • LLM agents · MCP
Get in touch View experience

01 — about

Work philosophy

I work in risk-based quality engineering. I cover the test process end to end — from test basis analysis and test case design to automation, execution, defect management and reporting — with E2E and API automation integrated into CI/CD pipelines at large companies across different industries.

My current focus is scaling quality responsibly with generative AI: I architected a QA control plane built on LLM-powered agents, with multi-agent orchestration and human oversight over test analysis and design, PR reviews and documentation. I treat AI output as an artifact to be verified — with complete context, traceability to the source and evidence-based verification before any result enters the quality workflow.

Before QA, I built an 11+ year career in the financial market, growing into an investment specialist and high-net-worth relationship manager — portfolio management, risk profiling and financial planning for highly demanding clients. That shapes how I approach quality: it's not about "finding bugs", it's about reducing business risk before it reaches the end customer.

// principles.spec — how I work
const principles = [
  'tests come from acceptance criteria,',
  '  not from code, CSS or layout',
  'every step has an expected result',
  'every automated test is traceable',
  '  to a test case and a requirement',
  'validate observable behavior —',
  '  a false positive is a test defect',
  'production incidents become coverage',
  'AI output is a hypothesis until verified'
]

expect(pedro.mindset).toBe('quality-first') // ✓

02 — skills

Skills

Test strategy & process

  • Risk-based test strategy
  • Test basis analysis and test case design
  • Black-box techniques and BDD (Gherkin / Cucumber)
  • Regression and confirmation testing
  • Defect management: severity, priority and lifecycle
  • Traceability requirement → test case → defect

QA standardization

  • Team-wide test case authoring standards
  • Bug reporting templates and checklists
  • Evidence-based PR review
  • Feature documentation with dependency mapping
  • QA Tasks linked to every User Story

UI automation (E2E)

  • Playwright + pytest
  • Cypress
  • Selenium WebDriver (MSTest, Cucumber)
  • Page Object Model and framework architecture
  • Tests linked to test cases with automatic results

API & data testing

  • REST and SOAP
  • Cypress (cy.request), Postman, Insomnia
  • Data validation with SQL Server
  • Test data management

CI/CD & test infrastructure

  • Git, GitHub and code review
  • GitHub Actions
  • Azure Pipelines
  • Docker for environments and suite execution

Performance & observability

  • Performance testing with k6
  • Defect investigation with Grafana (logs and metrics)
  • Playwright HTML Reporter

Generative AI in QA

  • LLM agents and multi-agent orchestration
  • Human oversight on critical tasks
  • Prompt engineering for test tasks
  • Claude Code + MCP (Azure DevOps, GitHub, Figma)
  • Mitigating hallucinations and non-determinism

Languages & management

  • Python · JavaScript · C# (.NET) · Java
  • Azure DevOps (Boards, Test Plans, Repos)
  • Jira
  • Scrum / Agile

Soft skills & languages

  • Business and risk mindset
  • End-user focus
  • Communication with technical and business audiences
  • Analytical thinking and attention to detail
  • Negotiation, ownership and adaptability
  • Portuguese — native · English — full professional

03 — experience

Professional experience

  1. Sep 2024 — present

    QA Engineer @ Halliburton

    Beyond executing tests, I define the team's QA standards.

    • Architected Cerberus, an AI-assisted QA control plane that coordinates and standardizes quality across a multi-repository ecosystem, with specialized agents and human oversight
    • Defined the test case authoring methodology in Azure DevOps: cases derived exclusively from acceptance criteria, a mandatory expected result on every step, parameterization with Shared Parameters and automatic suite organization
    • Structured the bug reporting standard: structured template, pre-creation checklist, P1–P4 prioritization and a rejection/reopen workflow
    • Built traceability for QA Tasks (test plan creation, review and execution, bug fix) linked to every User Story
    • Defined an evidence-based PR review: full-diff reading, progressive findings log, confidence filtering and multi-perspective analysis (architecture × QA/operational safety)
    • Standardized feature documentation with traceability to requirements, design and code, including DEV × QA perspectives and cross-feature dependency mapping
    • E2E automation with Python 3.12, Playwright and pytest: every test linked to a Test Case, with automatic result propagation and execution on GitHub Actions and Azure Pipelines with Docker
    • Performance testing with k6, defect investigation with Grafana and production incidents used as a source of test coverage
    • Anti-false-positive rule: tests validate the product's observable behavior, never implementation details

    Python · Playwright · pytest · k6 · Docker · GitHub Actions · Azure Pipelines · Azure DevOps · Grafana · Claude Code · MCP

  2. May — Jul 2024

    QA Engineer @ Multisoftware by nstech

    • Designed test strategies and wrote test cases in an agile team
    • UI automation with C#, Selenium WebDriver and MSTest, maintaining the automation framework
    • Test data management via SQL and traceability of stories, test cases and defects in Azure DevOps

    C# · Selenium · MSTest · SQL Server · Azure Pipelines · Azure DevOps

  3. Jan — May 2024

    QA Engineer @ REPAY

    Communications and Batch squads.

    • Implemented UI and API automation with Cypress, running in CI on GitHub Actions
    • Data validation directly in the database with SQL Server
    • Improved the squads' quality assurance processes, bringing in best practices from previous roles
    • Contributed to more efficient workflows between QA and development

    JavaScript · Cypress · SQL Server · GitHub Actions · Jira

  4. Sep 2022 — Nov 2023

    Software QA Engineer II @ Wex Inc

    Scrum team.

    • Designed comprehensive test strategies and wrote detailed test cases
    • Identified automation opportunities and worked across the end-to-end test lifecycle, manual and automated
    • Continuous maintenance and refinement of the C#, Selenium and MSTest automation framework, running on Azure Pipelines
    • Troubleshooting of test failures and peer reviews of test plans and test cases
    • Test data management via SQL Server and test cases in Azure Test Plans

    C# · Selenium · MSTest · SQL Server · Azure Pipelines · Azure Test Plans · Azure Boards

  5. Feb — Sep 2022

    QA Analyst Jr @ Compass.UOL

    • Manual and automated testing throughout the project lifecycle, focused on automating and optimizing processes
    • Web and API automation with Cypress; exploratory API testing with Postman and Insomnia
    • Test planning and coverage with Gherkin scenarios via Cucumber
    • Bug management in Jira, from opening to closure

    JavaScript · Cypress · Postman · Insomnia · Cucumber · Jira

  6. Oct 2020 — Jan 2022

    Test Analyst / QA @ E2E Coders

    Start in QA, working across the entire test process.

    • Test planning and test effort estimation with the squad
    • Requirements analysis and test case design using black-box techniques
    • Step-by-step test cases and BDD scenarios in Gherkin (Given/When/Then)
    • Defect management and confirmation testing, from logging to closure
    • Built a UI automation framework from scratch with Selenium, Cucumber and Java (Page Object Model), from BDD scenario to executable test
    • SOAP API testing with Postman

    Java · Selenium · Cucumber · Postman · Jira

+ 11 years in the financial market before moving into QA.

04 — education

Education & certifications

Academic background

  • Bachelor's in Computer Engineering — Impacta Tecnologia Jun 2019 – Jun 2023 Technical foundation for the move into technology: programming, software engineering, databases and networking — completed alongside my first years in QA.
  • MBA in Finance and Banking — Universidade Anhembi Morumbi 2020 – 2021 Deep financial business knowledge — products, risk and regulation — a differentiator when testing systems for banks, fintechs and payments.
  • Foreign Trade (Import/Export) — Universidade Paulista (UNIP) 2013 – 2014
  • Bachelor's in International Relations — FMU | FIAM-FAAM 2010 – 2013

Certifications & courses

  • Software Testing Mentorship — Julio de Lima 112h Software testing fundamentals and practice: strategy, test case design, automation and QA career.
  • Postman: The Complete Guide — REST API Testing — Udemy 50h REST API testing: requests, assertions, environment variables, collections and automated runs.
  • Scrum Foundation Professional Certificate (SFPC) — CertiProf 40h Scrum roles, events and artifacts — the foundation for QA work in agile teams.

Continuous learning

  • Software testing fundamentals Test process, test design techniques and defect management based on the leading international syllabi.
  • Testing AI systems and testing with generative AI ML model quality, prompt engineering for test tasks, LLM agents and hallucination mitigation.

05 — contact

Let's talk

Open to Senior QA / QA Lead opportunities — QA strategy and standardization, automation architecture and AI applied to testing.