Change can be hard. What's the biggest change you've faced in your career, and what lessons did you learn?
It's less of a change and more of a pivot. In 2018, I decided to join a consultancy, staying in software engineering (before this, I'd worked as part of an in-house tech team). It was a big learning curve in terms of learning to appreciate the work done before I joined by keeping the agile Prime Directive in mind: “Regardless of what we discover, we understand and truly believe that everyone did the best job they could, given what they knew at the time, their skills and abilities, the resources available, and the situation at hand”.
I also faced interesting tech problems I'd never seen before, meaning I had to learn how to research things quickly and find a solution. All of which helped me grow, plus I learnt how to effectively interact with clients.
What would you tell your younger self as you start your career?
Stick with it! I worked hard in those early years, and sometimes, I'd have moments where I'd think I wasn't progressing fast enough, but it worked out in the end.
I would also tell myself to know and negotiate my worth. Be braver in getting what you want in your career. Do your research to help you achieve this.
We're a team of doers. We help turn our client's strategy into a reality. What excites you about this? Is there a particular project that has challenged you/the team, and how did you approach it? Anything you'd do differently now?
One project that stands out is a major re-platforming project for a pre-paid payments company, which we delivered in nine months. When we joined the project, the tech was working, but it was held together with sticky tape. It wasn't fit for the client's needs, and it was hard to scale and change. Our mission was to make things better using modern technologies and make them more scalable and maintainable.
One way we did this was by following an MVP approach, focusing on one product and one payment method. This meant we could show how we could deliver value quickly and build up trust.
In terms of doing things differently, I would be braver in changing tactics when something isn't quite working. Don't be afraid to say: we tried to make it work, but let's do something else. Go back to the drawing board and try a different approach if it means you're going to deliver the outcome even faster. I now follow this approach on all my projects.
What is your advice for tech teams facing the "it's not how we do things" thinking? What personally helps you overcome this when you hit this blocker?
When I hit this, I find someone who believes in me and will champion my working methods. I always make sure it's someone within the client team I'm working with. Make sure you spread your message, and you will find people who understand and want to help you make it happen. You don't have to do this on your own.
What do engineering quality, speed to delivery and upskilling teams mean to you and your work?
For me, it's about delivering value as soon as possible, moving safely at speed, implementing solid engineering principles that the whole team has agreed upon, and pairing with the engineers in the client teams as much as possible.
We want to leave the organisation in a better place and ensure that what we build is supported when we roll off the project.
What does 'Transformation through Delivery' mean to you? How does it transform our client's business? What one thing stands out for you on TTD?
It's about being part of the exemplar team, showing the client what good looks like and enabling teams to learn from us and adopt some of our behaviours.
I've been working on a project where my team has taken a different approach. We've planned our work in advance, with a roadmap and sprints 1, 2, and 3 locked in. But we're still flexible and can rejig things whenever priorities change. The whole team is always aware of what's coming up next. It's a team effort, and by having this road map, we can show to other teams how we can estimate when work will be done and effectively engage with them.
What's an example of engineering quality, speed to delivery and upskilling teams where you've pushed yourself/your team to get to the right outcome for our clients? Any lessons learnt that you want to share?
I was part of a team working with a new authentication platform for a financial services client. The client had an apprentice engineer paired with the Crosstide team. It was a steep learning curve for all of us. I really enjoyed moulding someone at the start of their career, especially because I started my career as an apprentice. Plus we delivered something really good for the client - quickly - and I got to work with a great team of people.
We're all about amplifying connections. With one another, our clients, and partners. How have your connections shaped and influenced your career?
Every person I've worked with has taught me something. I always try to connect with the people I work with, and the best way to do this is by learning from them. One of the beliefs I stand by is always to be learning.
What excites you about technology right now and why?
I'm interested in how AI will change how we work. It won't replace my job but will help me become a faster engineer.
For example, when you have an error and a messy stack trace, rather than going through it line by line and trying to figure out exactly where the failure is, you can use AI to scan it and tell you the exact spot. This has been saving me hours.
While AI can write some code code, half of the stuff it generates is wrong. But it's very good at telling you where you've made a mistake. It's then firmly on you to fix it. I don't fear AI in any way!
What does 'the energy of change' mean for you?
I like change! I'm always excited about the next project, challenge, and the thought of changing hearts and minds. I'm not afraid of changing things if I need to.
One thing that can happen when I go on a new project is imposter syndrome. I think I'm bad at my job and will quit and move to the woods. Nick (Morgan, Crosstide Technology Director) has helped me with this. He says: "Everyone gets imposter syndrome, and good engineers get it bad because they appreciate what they don't know". A little bit of imposter syndrome pushes you to be better.
What's the project you're most proud of and why?
I'm part of a team working on a project with a vegetation intelligence company that's helping free up some engineers to work in other areas, including preventing forest fires. The work Crosstide is doing will help prevent power outages for their customers. I'm proud of working on projects where technology is having a positive impact on people and the environment.
Who is the one person you admire for creating change?
It's another shoutout for Nick (Morgan), who is doing a great job shaping our engineering practice by facilitating knowledge sharing sessions, mentoring and ensuring all the Crosstide engineers are upskilled. I'm enjoying all the positive changes he is making.
In 2024, 20% of the software engineering workforce comprised women. What one thing would you change to encourage more women and non-binary people into the profession?
Start young by allowing girls to do more problem-solving and Lego building. I had cars and Barbie dolls from a young age and was never told, "These toys are for boys and these are for girls". Toys were just toys, and that allowed me to explore the world with little gender bias.
I've been in tech since I was 18, and a book that helped me is 'Women in Tech' by Tarah Wheeler. It encourages you to forget that you're a woman and instead just be yourself. It's a nice guide for anyone starting in the industry.