Home for Attachments: From Platform Foundations to Product Delivery
How customer needs, roadmap trade-offs, and storage modernization came together to enable a better way for service providers to manage job-related files.
- 2026
- Staff Technical Product Manager - Backend Foundations
- Platform foundations, storage modernization, cross-team delivery
- Showcased at Jobber Now, October 2026
- Ruby on Rails, ActiveStorage, Amazon S3, GraphQL
The problem
Photos, documents and other attachments associated with jobs were spread across the product experience. Creating a unified place for service providers to find and manage those files required the underlying storage foundations to evolve as well.
The role
Kavindu connected the customer-facing opportunity with the platform work needed to make it possible: investigating backend dependencies, reviewing the remaining storage migration, and working with senior leadership and engineering management to establish a viable delivery path within an already committed roadmap.
The approach
Discovery showed that storage modernization was a critical dependency. Kavindu aligned the work to the customer outcome, prioritised the models needed by the feature first, and separated the launch-critical path from the longer work of migrating historical data and retiring legacy code.
What Kavindu led
- Established a phased plan connecting the storage migration to the product milestone.
- Created clear ownership and progress tracking across attachment-owning models.
- Aligned engineering capacity and dependencies with feature-team timelines.
- Coordinated adoption work across backend, frontend and mobile stakeholders.
- Communicated delivery risks and the remaining retirement work transparently.
The outcome
The platform work unblocked the feature team to deliver Home for Attachments, giving service providers a unified experience for job-related files. The experience was showcased at Jobber Now in October 2026.
- The launch-critical platform dependencies were addressed.
- New attachment writes were consolidated onto the modern storage platform, according to internal program reporting.
- Remaining legacy-client retirement was tracked separately rather than described as fully complete.

Kavindu Narathota