I am a Software Engineer within Starling Payment Schemes, where my role is a dynamic mix of technical and operational support. I focus on payment flows to ensure seamless, secure transactions. As a significant part of my day-to-day involves technical debt reduction and system optimisation, I directly empower our Engineering, Payment Operations and Customer Service teams to work more efficiently, ultimately improving the end-user experience.
It was a natural intersection of my affinity for problem-solving and creative expression. Growing up, I was drawn to anything that required logic, such as puzzles, board games, and, generally, random shower thoughts! What really sold me on the tech industry, however, was
its open-source ethos. The wealth of accessible information and the culture of online peer discussion made education feel democratic and self-attainable. I love that the industry embraces a growth mindset; it’s a space where saying “I don’t know… yet” is welcomed, and where people are encouraged to learn at their own pace across various specialisms.
Actually, no. My academic background is in Mechanical Engineering, and my A-Levels were in Maths, Physics, and Economics. While those subjects are highly analytical, my exposure to “code” was limited to MATLAB and specialised engineering software for CAD and FEA
(Finite Element Analysis). Even during my uni days, I felt like I’d missed the ‘early web’ era, largely because I hadn’t experimented with coding during the formative 2000s, especially when meeting people who did (see, hard on myself again for no reason!). Transitioning into pure software engineering required me to translate those foundational problem-solving skills into a completely new digital language.
I didn’t have traditional IT work experience. Instead, I took a different route by completing a coding bootcamp and participating in a career-switcher programme at a telecoms company.
These experiences were pivotal in bridging the gap between my engineering background and the specific demands of a software development environment. There is absolutely no shame in reskilling and starting again!
Statistically, yes. While it is encouraging to see the number of female juniors growing, there is a noticeable scarcity of women in mid-level and senior leadership positions. We are making progress at the entry level, but the real challenge now is ensuring that women have the support and retention pathways to reach higher tiers of influence.
Definitely. There is a persistent stereotype that tech is a “male-only” domain, which often manifests as unconscious bias. Interestingly, this bias isn’t just external; women can sometimes internalise these stereotypes themselves. It is crucial for us to stay vigilant and “check” ourselves and our peers whenever these biases creep into our decision-making or workplace culture.
We need to shift the culture toward psychological safety. Making it “okay to fail” or not understand a concept immediately is vital. If we frame technology as a journey of trial and error rather than an innate talent you either have or don’t, it becomes much less intimidating and far more inviting for women to explore. People in tech don’t need to have been tinkering at home since they were 9!
Yes, there are both systemic and internal barriers. Systemically, exclusionary job descriptions or rigid hiring practices can act as a deterrent. Internally, there is the hurdle of self-rejection, where women might talk themselves out of applying for a role because they don’t meet 100% of the criteria. I personally experienced this while studying for my male-dominated engineering degree. I assumed everyone (regardless of gender) was just as meticulous about meeting every single requirement. However, I realised there is a deeper sociological layer at play: due to early childhood signalling, women are often conditioned to believe they will be placed under a microscope. Because we feel our mistakes are more
heavily scrutinised, we develop a self-imposed pressure to be “perfect” before even stepping through the door. Breaking into tech requires us to unlearn that need for perfection and realise that the “requirements” list is often just a wish list.
