I progressed into the role of Software Engineering Team Lead of the Beneficiary Domain, which was made up of 5 services: My Account, Booking, Exchange, Friday, MMS.

This team was a team of 18 developers/QA's and 2 product owners.

My responsibilities included:

• - 9 direct reports
• - Responsible for the creation of tickets and translating requirements from POs
• - Maintaining oversight on the current change proposal
• - Scoping of work and resource management
• - Presenting solution workgroups ahead of any complexitiy 3 change
• - Reporting of timelines and expected times of delivery to key stake holders on a weekly basis
• - Driving refinements, retros, 1-2-1s, cycle time improvements
• - Point of contact for any production issues
• - Working with technical leads from other services to create plans for the current cycle to achieve the company roadmap

These two examples are the most recent projects I worked on as team lead for the Beneficiary Domain.

Open Platform

My most recent projects were based on introducing a new product type to Smartbox, changing how we work as previously we assigned experiences to a box. The most recent project was to remove this limitation and allow the user to view the full collection of experiences in Smartbox.

This was achieved by introducing a new product type named "Open Platform Product", this product would be a shell. The search results would be supplied by meeting a margin expectation calculation to make sure the results matched the price of the voucher instead of being attached to a box with a price.

This concept was a big change in how we worked with vouchers and was a significant change across all the systems in Smartbox.

Free Plus

Another project was Free Smartbox Plus which was based on top of Open Platform, the aim was to offer experiences which were considered paid upgrades as free to the customer based on their expected margin being the same as their original voucher.

This was done by allowing the user to search the full catalog and returning results that matched a margin expectation then migrating from a standard voucher to a OVOPP (open value open platform product), via exchange and a new voucher would be created with a dynamic price and margin of the original voucher.

This allow the customer to access the full open platform catalog with their legacy voucher type.

Both of these changes were high complexity and the scope involved all websites and more than 10 services with full financial checks and A/B testing.