Our client does not use off-the-shelf software for their operations. They have built a proprietary, complex workflow engine that manages thousands of tasks, users, and automations daily.
The mission of this engagement is to serve as the Final Gatekeeper. You are the wall between code deployment and operational chaos. Your objective is to ensure that automation logic strictly obeys the rules, the platform remains stable for users, and zero critical bugs reach the live environment.
Who This Is For
This role is for a Breaker. If you prefer the Happy Path where everything works as intended, do not apply. We need the professional who naturally looks for the edge case that crashes the system. You must possess Competitive Greatnessyou don't just find bugs; you take pride in finding the bugs that no one else could.
The Scorecard: Key Results & Deliverables
We are not hiring you for hours; we are engaging you for outcomes. Success in this role is measured by the following results:
1. Pre-Release Validation (The Gatekeeper)
- Result: New backend and frontend features function exactly as engineered before they touch the live environment.
- Deliverable: Validated engineering tickets confirming features meet strict specifications.
- Deliverable: Negative Testing reports where you have actively attempted to input invalid data, bypass fields, and stress-test error handling to ensure robustness.
2. Logic & Automation Integrity
- Result: Automated assignment bots and workflows obey all availability rules and distribution logic without failure.
- Deliverable: Audited workflow logs confirming that Timer SLAs (trigger, pause, reset) and Status changes function correctly.
- Deliverable: Verification that metadata and tags persist accurately across workflows without flip-flopping.
3. Live Environment Sanity
- Result: Immediate detection of critical failures post-deployment.
- Deliverable: Post-Deployment Sanity Checks completed immediately after code pushes (Login, Save, Submit, Sync functions).
- Deliverable: Proactive identification of Zombie States (tasks stuck in processing loops) flagged to Engineering before they impact Operations.
4. Incident Resolution Speed
- Result: Developers receive actionable, technical data rather than vague user complaints.
- Deliverable: Reproducible Bug Reports that isolate specific variables (Browser, OS, User ID).
- Deliverable: Complete technical evidence packages (Console Logs, Network/HAR files, IDs) attached to every issue log.
Competencies & DNA (The How)
- Sincere Candor: You speak Dev. You do not sugarcoat issues. You provide clean, harsh, accurate technical logs (Network HAR files, Console logs) that Engineers respect.
- Logic Fluency: You can look at a complex workflow diagram and trace IF/THEN/ELSE rules to verify bot behavior without needing hand-holding.
- Unimpeachable Character: You will have access to sensitive permissions to simulate Admin vs. User roles. You treat security boundaries as absolute.
- Autonomy (Level 4 Accountability): You act, then inform. We do not micro-manage. We expect you to own the QA queue and inform us of the status.
Requirements
- Proven experience in Manual QA and Logic Testing for complex web applications.
- Ability to read and interpret browser Console Logs and Network tabs.
- Experience engaging with Engineering teams via tickets/bug tracking tools.
- Tech Stack Alignment: Must be proficient with [Insert Client's Specific Project Management/Bug Tracking Tools, e.g., Jira, Linear, etc.].
The Agreement
- Type: Independent Contractor Agreement.
- Service Fee: Monthly retainer or hourly rate (to be negotiated based on experience and scope).
- Availability: Must be available to coordinate synchronously with the Engineering team business hours.
Next Steps
If you are ready to own the quality standard of a high-stakes platform and you align with the results above, apply here.
Warning: We test for skill, not just history. Be prepared to demonstrate your ability to catch a bug during the interview process.
