Senior Maintenance CTO for Bug-Fixing
Budget: $15 – $25 USD
I need an experienced technical leader who can step in as my fractional CTO and immediately take ownership of ongoing maintenance, with bug fixing as the number-one priority. We run a portfolio of customer-facing web apps, companion mobile apps, and several interconnected backend services. Issues crop up across this full stack, so I’m looking for someone who can dive into production incidents, trace root causes quickly, and ship solid patches without disrupting live traffic.
Beyond the day-to-day bug squashing, you’ll keep an eye on DevOps and monitoring automation. Our CI/CD pipelines (GitHub Actions + Docker + Kubernetes), logs (ELK), and alerts (Prometheus/Grafana) are in place but need continuous tuning so that defects are caught before users feel them.
Key deliverables
• A triaged bug backlog with severity, root-cause notes, and ETA for each fix
• Verified fixes deployed to production for web, mobile, and backend components
• Hardening of our monitoring rules and dashboards to surface regressions earlier
• A concise weekly report summarizing resolved issues, open risks, and next actions
Acceptance criteria
1. All critical bugs reproduced, fixed, peer-reviewed, and merged following our GitFlow process.
2. Automated tests expanded or added to cover every resolved defect.
3. Alert coverage proves effective by triggering in staging during fault-injection tests.
4. Zero-downtime deploys maintained throughout.
You’ll collaborate directly with two in-house developers and me, communicating over Slack and Jira. If you have a proven track record of hands-on leadership in high-traffic environments—balancing quick fixes with long-term stability—let’s talk.
Beyond the day-to-day bug squashing, you’ll keep an eye on DevOps and monitoring automation. Our CI/CD pipelines (GitHub Actions + Docker + Kubernetes), logs (ELK), and alerts (Prometheus/Grafana) are in place but need continuous tuning so that defects are caught before users feel them.
Key deliverables
• A triaged bug backlog with severity, root-cause notes, and ETA for each fix
• Verified fixes deployed to production for web, mobile, and backend components
• Hardening of our monitoring rules and dashboards to surface regressions earlier
• A concise weekly report summarizing resolved issues, open risks, and next actions
Acceptance criteria
1. All critical bugs reproduced, fixed, peer-reviewed, and merged following our GitFlow process.
2. Automated tests expanded or added to cover every resolved defect.
3. Alert coverage proves effective by triggering in staging during fault-injection tests.
4. Zero-downtime deploys maintained throughout.
You’ll collaborate directly with two in-house developers and me, communicating over Slack and Jira. If you have a proven track record of hands-on leadership in high-traffic environments—balancing quick fixes with long-term stability—let’s talk.