Sharesies Open
Overview
At Sharesies, I developed a self-service portal for companies managing employee share schemes (ESS) during my summer internship.
This was the first step in a major expanding Sharesies Open’s feature set. The portal will replace a manual, spreadsheet-based workflow with a fully integrated company-facing interface.
I was the sole developer on the project with guidance from senior developers. I also worked closely with product designers and business analysts.
Sharesies Open was an existing product with a BFF model. I introduced a secure, maintainable internal API to bridge Sharesies Open Backend with the Retail Backend, avoiding duplication and preserving future flexibility.
Designed and delivered a read-only MVP in just 6 weeks
Integrated new functionality into existing services with zero downtime
Set the technical foundations for future CRUD capabilities
Categories
Saas
Full-stack
Client
Sharesies
Project Detail
Bridging Two Codebases Without Duplication
Employee share scheme data lived in the Retail backend, while Sharesies Open was designed to face companies directly. To avoid duplicating data or creating syncing issues, I established a secure internal API that connected the two systems.
Identifying a shared id for the NZSX/ASX listing, I created a reliable relationship between a company in Open and its corresponding entities in Retail —even when they weren’t mapped 1:1. This allowed us to expose ESS data, safely and accurately within the new portal.
Cross Functional Collaboration
I had genuine fun working in cross-functional process; balancing stakeholder needs with my own technical judgment. This included:
Collaborating closely with product to translate intent and designs into responsive UI
Co-working sessions with BAs to clarify edge cases
Architecture workshops with senior devs to sketch and refine data flows
Although I was fairly new to an environment like Sharesies; my decade of experience running my own service business (Patina Photo) served me well;. I knew when to ask questions, when to propose solutions, and when to slow down and listen. Resulting in a better product —and better working relationships.
Security and Permissions with Growth In Mind
I expanded the Sharesies Open permissions system to support the ESS (and future) company-facing features.
The back-end permissions system was expanded to allow fine-grained authorisation per staff member within a company. I also used flags so that features could be gated by company plans and subscription levels. Combined, these let us roll out new capabilities gradually, test with specific cohorts, and prepare for monetisation pathways.
The changes were released with no downtime, using an expand-and-contract migration strategy that allowed safe schema evolution while keeping existing users unaffected.
Sharesies Open
Overview
At Sharesies, I developed a self-service portal for companies managing employee share schemes (ESS) during my summer internship.
This was the first step in a major expanding Sharesies Open’s feature set. The portal will replace a manual, spreadsheet-based workflow with a fully integrated company-facing interface.
I was the sole developer on the project with guidance from senior developers. I also worked closely with product designers and business analysts.
Sharesies Open was an existing product with a BFF model. I introduced a secure, maintainable internal API to bridge Sharesies Open Backend with the Retail Backend, avoiding duplication and preserving future flexibility.
Designed and delivered a read-only MVP in just 6 weeks
Integrated new functionality into existing services with zero downtime
Set the technical foundations for future CRUD capabilities
Categories
Saas
Full-stack
Client
Sharesies
Project Detail
Bridging Two Codebases Without Duplication
Employee share scheme data lived in the Retail backend, while Sharesies Open was designed to face companies directly. To avoid duplicating data or creating syncing issues, I established a secure internal API that connected the two systems.
Identifying a shared id for the NZSX/ASX listing, I created a reliable relationship between a company in Open and its corresponding entities in Retail —even when they weren’t mapped 1:1. This allowed us to expose ESS data, safely and accurately within the new portal.
Cross Functional Collaboration
I had genuine fun working in cross-functional process; balancing stakeholder needs with my own technical judgment. This included:
Collaborating closely with product to translate intent and designs into responsive UI
Co-working sessions with BAs to clarify edge cases
Architecture workshops with senior devs to sketch and refine data flows
Although I was fairly new to an environment like Sharesies; my decade of experience running my own service business (Patina Photo) served me well;. I knew when to ask questions, when to propose solutions, and when to slow down and listen. Resulting in a better product —and better working relationships.
Security and Permissions with Growth In Mind
I expanded the Sharesies Open permissions system to support the ESS (and future) company-facing features.
The back-end permissions system was expanded to allow fine-grained authorisation per staff member within a company. I also used flags so that features could be gated by company plans and subscription levels. Combined, these let us roll out new capabilities gradually, test with specific cohorts, and prepare for monetisation pathways.
The changes were released with no downtime, using an expand-and-contract migration strategy that allowed safe schema evolution while keeping existing users unaffected.
Sharesies Open
Overview
At Sharesies, I developed a self-service portal for companies managing employee share schemes (ESS) during my summer internship.
This was the first step in a major expanding Sharesies Open’s feature set. The portal will replace a manual, spreadsheet-based workflow with a fully integrated company-facing interface.
I was the sole developer on the project with guidance from senior developers. I also worked closely with product designers and business analysts.
Sharesies Open was an existing product with a BFF model. I introduced a secure, maintainable internal API to bridge Sharesies Open Backend with the Retail Backend, avoiding duplication and preserving future flexibility.
Designed and delivered a read-only MVP in just 6 weeks
Integrated new functionality into existing services with zero downtime
Set the technical foundations for future CRUD capabilities
Categories
Saas
Full-stack
Client
Sharesies
Project Detail
Bridging Two Codebases Without Duplication
Employee share scheme data lived in the Retail backend, while Sharesies Open was designed to face companies directly. To avoid duplicating data or creating syncing issues, I established a secure internal API that connected the two systems.
Identifying a shared id for the NZSX/ASX listing, I created a reliable relationship between a company in Open and its corresponding entities in Retail —even when they weren’t mapped 1:1. This allowed us to expose ESS data, safely and accurately within the new portal.
Cross Functional Collaboration
I had genuine fun working in cross-functional process; balancing stakeholder needs with my own technical judgment. This included:
Collaborating closely with product to translate intent and designs into responsive UI
Co-working sessions with BAs to clarify edge cases
Architecture workshops with senior devs to sketch and refine data flows
Although I was fairly new to an environment like Sharesies; my decade of experience running my own service business (Patina Photo) served me well;. I knew when to ask questions, when to propose solutions, and when to slow down and listen. Resulting in a better product —and better working relationships.
Security and Permissions with Growth In Mind
I expanded the Sharesies Open permissions system to support the ESS (and future) company-facing features.
The back-end permissions system was expanded to allow fine-grained authorisation per staff member within a company. I also used flags so that features could be gated by company plans and subscription levels. Combined, these let us roll out new capabilities gradually, test with specific cohorts, and prepare for monetisation pathways.
The changes were released with no downtime, using an expand-and-contract migration strategy that allowed safe schema evolution while keeping existing users unaffected.
