@fed/senior-qa-engineer
Senior QA Engineer Cover image unavailable
Prompt v1.0 · updated 2026-07-04

Prompt

Senior QA Engineer

Senior QA Engineer is a Prompt for Engineering & Automation on Sigrix.

Answers delegated testing and release-safety questions with a risk-ranked plan: what to test first, what's most likely to break, and the evidence that proves the change is safe.

Token usage 0.2k tokens
Compatible
ChatGPT
Updated 2026-07-04
Rating —
Engineering & Automation engineer senior what

Tested compatibility

Platforms and models the creator verified this listing on.

  • ChatGPT Verified

Production readiness

Starter

1 of 5 production pillars met

  • Compatibility tested
  • Evaluated
  • Security screened
  • Tools & integrations
  • Memory & state
  • Per-run observability coming soon

What you get

  • Digital strategy engine (prompt-based), reusable across scenarios for ChatGPT
This prompt is used in 1 agent

What this does

Answers delegated testing and release-safety questions with a risk-ranked plan: what to test first, what's most likely to break, and the evidence that proves the change is safe.

Prompt preview

What's inside this prompt

A summary of the blocks this prompt includes. Full template content unlocks on access.

🔒 Source locked
  • 01
    Context✓ Included

    Background and operating environment.

  • 02
    Rules✓ Included

    Hard constraints the prompt must follow.

  • 03
    When responding✓ Included

    Style and approach for each reply.

  • 04
    Output format✓ Included

    Structure and shape of every response.

Template

Prompt template

Preview the structure. Unlock the full, copy-ready template on access.

🔒 Locked 
Twelve years of QA on payment and onboarding flows. Most incidents ship inside "small" changes nobody thought to test. You think in failure modes, edge cases, and regression blast radius.
🔒 Full template unlocks on access
Full template locked
4 blocks · run-ready — unlock to copy, fill and open in your tool of choice.
Sample run

What this prompt returns on a real case

Sample interactions provided by the creator — your results may vary by model.

ChatGPT
User

A payments team shipped a "small" refactor to the retry logic on failed card charges. What should we test first?

Output

Risk-Ranked Plan for Testing Retry Logic Refactor

1. Top Risks in Priority Order:

1.1. Incomplete or incorrect retry attempts

  • Failure Mode: If the logic does not appropriately trigger retries (for example, retries may not occur for certain error codes), users may experience charges that fail without any resolution.
  • Blast Radius: Affected users may be unable to complete payments, leading to loss of revenue, increased customer frustration, and potential chargebacks.

1.2. Looping behavior due to misconfigured retries

  • Failure Mode: If the retry logic inadvertently creates infinite loops (e.g., retrying without a proper backoff or threshold), the system may become unresponsive or degrade service.
  • Blast Radius: Service degradation can impact all users trying to make card payments, leading to widespread payment failures.

1.3. Data integrity issues due to processing of duplicate transactions

  • Failure Mode: The refactor could inadvertently create situations where the same transaction might be processed multiple times if retries are not handled correctly, causing double charges.
  • Blast Radius: Directly impacts affected users through incorrect billing, potential financial losses, and may trigger disputes or refunds.

2. What to Test First:

  • Test 1: Error Code Handling & Retry Triggers Focus on testing various error codes (e.g., temporary failures like network errors vs. permanent failures like card declined) to ensure retries trigger correctly and in expected scenarios.
  • Test 2: Backoff Strategy and Safety Limits Test the backoff logic in retries with extreme scenarios (e.g., high frequency of errors) to verify that it does not lead to infinite loops, ensuring service remains stable with defined limits.
  • Test 3: Duplicate Transactions Verify that the retry logic includes mechanisms to prevent processing the same transaction multiple times. Conduct tests with various transaction states (e.g., already processed, pending) to ensure consistency.

3. Evidence That Proves the Change Is Safe:

  • Error Handling Metrics: Collect metrics that demonstrate that the retry logic correctly processes a range of error codes and that the number of successful retries is within expected limits without any infinite loops.
  • Load Testing Results: Execute stress tests to simulate high volumes of failed charges in different scenarios, ensuring that the backoff mechanisms correctly limit retries and that service remains performant.
  • Transaction Logs Audits: Review transaction logs post-implementation to confirm that no duplicate transactions were logged and that charge statuses are consistent with intended business logic, ensuring data integrity is maintained.

By strategically addressing these areas, we can significantly reduce the risk of introducing failures while validating the functionality of the newly refactored retry logic effectively.

Tested on: ChatGPT

How this product works

  1. Get access
  2. Copy the prompt
  3. Paste into ChatGPT
  4. Get tailored results
FAQ

Common questions

  • What is included with this prompt listing?

    You get the prompt, example output, and usage instructions needed to run and adapt this listing.

  • Which model should I run this prompt with?

    Use the validation badges and scenario notes in this listing to pick a tested platform and version.

  • Can I customize this prompt for my context?

    Yes. Replace placeholders and tune constraints in the Prompt tab while keeping the prompt structure intact.

  • Where are execution and template details?

    The Prompt tab includes practical run steps plus optional expandable blocks for full prompt and template content.

View all FAQs →
More from @fed

Other prompts you might like

Browse all prompts
Prompt
Software Architect
Answers delegated system-design and performance questions with a specific direction: the smallest design that solves it, the main trade-off it accepts, and the first step to take Monday.
Free by @fed
Prompt
Product Designer
Answers delegated UX, flow, and adoption questions with a concrete design diagnosis and fix: where users struggle, why, and the specific change to ship first.
Free by @fed
Prompt
ScrollStop AI
A short-form hook architect that engineers scroll-stopping opening lines and spoken hooks for Reels, TikToks, Shorts, and social posts — built for creators losing viewers in the first two seconds.
Free by @fed
Prompt
ClickLift AI
A YouTube packaging strategist that engineers title-and-thumbnail combos to lift click-through rate without burning audience trust — built for creators whose good videos keep getting buried.
Free by @fed

About this listing

Frequently asked questions

What does Senior QA Engineer do?

Answers delegated testing and release-safety questions with a risk-ranked plan: what to test first, what's most likely to break, and the evidence that proves the change is safe.

Who is Senior QA Engineer best for?

Senior QA Engineer is built for engineering & automation use cases. and is particularly useful for engineer, senior, and what.

Can I edit Senior QA Engineer after I get it?

Yes — Senior QA Engineer is delivered as editable prompt text you own on Sigrix. Adapt the wording, variables, and structure to fit your workflow; it is not a locked black box.