The iOS Team at Gousto use autolayout for all of its UI so that we are able to accommodate variable content, dynamic type and different size classes of devices. When we wanted to switch our recipe list to a grid on medium size class devices, we struggled to find any documentation on how we could achieve this using UICollectionView and XIBs for the UICollectionViewCells. This blog post talks about the issues we had and how we achieved it using a custom UICollectionViewLayout.
This post is the second in our series interviewing members of our GoustoTech team. In this post we meet Catherine Burrows who has recently moved from our Analytics team to become a Data Scientist in our Data Science (Artichokes) team.
Hi, I’m Catherine and I am a Data Scientist at Gousto. We currently have a team of 5 data scientists and it’s our job to develop and maintain key products that make Gousto unique as a company, from the recipe recommendation engine, to the warehouse routing algorithm.
This post is the first in a new series interviewing members of our GoustoTech team. We start right at the top by interviewing our CTO, Shaun Pearce and over the coming weeks will interview a number of other members of our team.
Hi, my name is Shaun and I’m Gousto’s CTO. I’m responsible for all aspects of technology across our business. This of course includes our customer facing website and mobile apps but that’s really just the tip of the iceberg! Technology plays a crucial role all over Gousto. My team is also responsible for our bespoke order management system, internal tools supporting our customer care, marketing and recipe development teams as well as systems used to manage our supply chain, our warehouse and our automated pick lines.
Gousto, like many tech startups, used to build a product roadmap on a quarterly basis. Towards the end of each quarter our product managers would kick off the work by writing up a long list of initiatives for our business to focus on for three months, and would work closely with their engineering squad and stakeholders to whittle this down to a few key items with the strong business justification and estimated complexity.
However over the second half of 2017 we started to become frustrated with this process and found that it was not working for us. To start with, building a quarterly roadmap required a prolonged effort from staff around the business, and many hours of coordination by the Product Manager. The overhead of creating a plan and aligning with the wider business was very high. We also found that we were providing little visibility to our leadership team and other stakeholders, as this plan would only be reviewed every three months. Worst of all, the plan was misleading. Given we would begin this process before the start of a new quarter, we found ourselves projecting out 4 or 5 months into the future. In a fast paced business like Gousto the result was that we rarely stuck to the original plan. The quarterly roadmap felt distinctly un agile, but we quickly found a simple alternative.
In the iOS team, we are always trying to improve our app. Our mobile apps provide our customers with a platform to create new Gousto orders, edit orders, view recipe instructions and manage their account. These features are also available on our website, so we have to give our customers a reason to download and use the mobile app, which is why we must improve upon these core features and create a better more engaging user experience.
On a day to day basis, we all work hard on company initiatives that directly relate to our business goals, but as a tech team we all take one day every two weeks to work on self-driven projects for Gousto, we call this Tech 10%. These projects enable our team to further their skills in different technologies, improve the user experience of our products and add features to the platform.
I have used this time over the course of the last couple of months to implement some app-specific features, that will take the user experience above and beyond the web. Some of these unique features I have worked on recently are using biometric sensors for authentication, Force Touch for navigation and Health Kit for nutritional information tracking.
After joining Gousto as Head of Engineering in September 2017 I’ve spent a lot of time interviewing candidates as we look to scale out our engineering team. One of the most common questions I’m asked is how we structure the team here at Gousto. This is the first in a series of posts looking at ‘how’ (and most importantly ‘why’) we structure our engineering team this way.
At Gousto we actually split our Data Science team from our Software Engineering team, but work amazing closely. I’ve included both in this article so you can see how they fit together. At the current time our combined team is around 30 people but this is likely to grow up to around 50 by the end of 2018. This is the first part of our growth as we continue to scale the company and expect this only to continue into 2019.
The Olympic swimming pool; the double-decker bus; the football stadium. Whilst researching stats to include in this post, it saddened me to discover that these are all units commonly used to quantify the UK’s food waste. As for where it’s all coming from, studies (for example, this study by WRAP) suggest that retail and household food waste accounts for around three quarters of the UK’s overall post-farm-gate total. Given Gousto’s rapid growth, it is now more important than ever for us to consider our impact in terms of food waste. So what exactly are we doing to help? In this post, I will attempt to answer that question, focusing particularly on our strong investment in data science and analytics.
The UK has a young, but fast-growing data science community, as evidenced by the growing number of regular data science meet-ups and companies offering training programmes like ASI or S2DS. As a data science team we are keen to learn from fellow data scientists, as well as to showcase our work and the impact it has had on the business. Giving talks at universities is one way in which connect with the community, while improving our chances to grow our team with the UK’s most promising new data scientists. Recently, we combined a team off-site in Cambridge with a workshop in partnership with the Cambridge University Data Science Society. You can find the slides we used for the event in this post, along with some learnings we took away as a team.
A look back at my 12 weeks interning in Gousto’s Mobile Apps team
Hi, I’m Nik! I’m a 19-something Computer Science student at Imperial College
London and just finished my summer internship at Gousto, working in the
iOS/Mobile team called ‘Mushrooms’ (now the title makes sense) 😄.
This is my first internship and it was a super exciting opportunity to work
in a tech team at a company on a real product. That’s right, some of what
I’ve worked on is now out for the world to see and is hopefully benefitting
the business as well. It was also my first time participating in code
reviews, both having my code be reviewed and being the one who reviews.
I’ll try to catalogue what I’ve done and what it’s been like working here for
12 weeks in this post.
About a year ago, I met Shaun and Gareth at the careers' fair of Imperial College's Department of Computing Society (DoCSoc), which I helped to organise. They had bought with them a big food bike, along with boxes of fresh veg.
Hmmmm, a pretty… quirky company, certainly nothing at all like the other 12 tech companies there.