Cloud360 Ongoing Development Phase 2
Budget: $10 – $30 CAD
Cloud360 is moving into Phase 2, a cycle dedicated solely to squashing the bugs that surfaced after launch. I’ll hand you a clearly documented backlog—steps to reproduce, log excerpts, and a link to the Git repository—and expect clean, well-commented patches submitted via pull request. Each fix must be accompanied by unit tests and must pass the existing CI pipeline before we promote it to our staging environment.
The stack is a typical cloud-native mix of Node.js, React, PostgreSQL, Docker, and AWS services, with automated testing through Jest/Mocha and a CI/CD workflow. If you are comfortable diagnosing issues in this ecosystem and can work iteratively while keeping an eye on regression risk, you’ll fit right in.
Deliverables
• Patched source code for each ticket with accompanying tests
• Concise change log entry per fix
• Confirmation that all CI checks and existing test suites pass on the staging branch
Acceptance criteria
• Each assigned issue verifies as “fixed” on staging
• No new lint, security, or performance regressions are introduced
Share a brief example of similar repair work and your typical turnaround time per issue when you respond, and we can get started right away.
The stack is a typical cloud-native mix of Node.js, React, PostgreSQL, Docker, and AWS services, with automated testing through Jest/Mocha and a CI/CD workflow. If you are comfortable diagnosing issues in this ecosystem and can work iteratively while keeping an eye on regression risk, you’ll fit right in.
Deliverables
• Patched source code for each ticket with accompanying tests
• Concise change log entry per fix
• Confirmation that all CI checks and existing test suites pass on the staging branch
Acceptance criteria
• Each assigned issue verifies as “fixed” on staging
• No new lint, security, or performance regressions are introduced
Share a brief example of similar repair work and your typical turnaround time per issue when you respond, and we can get started right away.