4it techELITE – Exploring Development at Boohoo Part 1

“An insight into the Back End Technology for an e-commerce retailer…”

9th September 2021

4it Recruitment

4it techELITE

“An insight into the Back End Technology for an e-commerce retailer…”

A forum for sharing deepdives into technical issues in the world of IT.

4it techELITE is a non-commercial thought-leadership forum for the exchange of technical knowledge and ideas in the world of IT. 


Steve Nolan – Technology Director

Steve looks after the core platform and back end systems for the Boohoo group brands. Has been at Boohoo for the last two years and previously worked in Technology and e-commerce at Asda, Walmart and Morrisons.

Wes Sangster – PHP Team Lead

Wes looks after the development of core backend applications that enable the business to manage internal processes and enhance the customer experience.

Working with a team that are highly experienced in building scalable and performant Laravel applications by leveraging AWS services like CodePipeline, ECS, ElastiCache, RDS, SNS and SQS that form the building blocks in our drive to standardise architecture, worry less about deployments and focus on quality feature-rich applications that scale horizontally in support of our Boohoo family’s growth.

Ste Lawson – Java Developer Team Lead

Ste is responsible for middleware solutions which have supported our huge growth through brand acquisition. Java development projects include areas such as pricing, products, warehousing, carrier and stock management – there is never a dull moment with quite a few laughs along the way.

I am passionate about boohoo’s technical stack and lead a team that builds reliable solutions to meet the retail market’s demands. I have a focus on building boohoo into a recognised brand for Java developers looking for a rewarding career within the “boohoo Family”.

Questions & Answers

What’s the biggest challenge you find with your respective teams?

At the moment we are developing a lot of new features very quickly. The challenge we face is ensuring those features remain compatible between all microservices. We tend to make most features forward and backward compatible for a few releases to achieve this.

How do you decide which language is used for a specific project?

Honestly, it generally comes down to available resources. PHP will often get picked for full stack internal applications. Also, PHP will often be used where a SDK is available for it. Java is used more for messaging big data and system integration. Also, it can relate to if a team has done a similar project we will cookie cut that approach into the new project. It is not about the “best” language but the language and team that can deliver the quickest and most maintainable results.

Looking for work?

Search our database, or get in touch with us.

Job Search