Why did you join Tickd?
I joined Tickd because I was excited by the opportunity to work in a small, agile team where I could make an impact from day one.
The energy-switching industry was new to me, but joining a small SaaS company felt like a great chance to grow quickly both as a developer and in my understanding of this space.
What’s good about Tickd?
Culture: “The team is genuinely helpful and supportive. People are always happy to help with the tricky problems we face.”
Pace: “Things move quickly here – we ship features frequently, and there’s a real sense of momentum behind what we’re building.”
Trust: “One of the best things is the level of trust I have been given the backend. Particularly with our small team, I can suggest improvements to our systems and see them implemented quickly, without layers of bureaucracy.”
What’s bad about Tickd?
Wearing multiple hats: “I often end up touching more than pure backend work – a bit of DevOps work, occasional frontend tasks, or even data engineering – which is great for learning but can stretch focus at times too.”
Resource Constraints: “As a small team, sometimes we have to make pragmatic trade-offs. Not everything can be perfectly refactored or given extensive test coverage right away, so we have to actively manage tech debt.”
Scaling challenges: “As we grow as a platform with more partners and higher volume, we’ve hit some scaling pain point that require careful consideration. We don’t always have deep prior experience or specialists in every area, so we solve them as a team.”
What’s different about Tickd?
Full-stack visibility: As a backend developer, I get to see as well as influence how the frontend, partner integrations, and business logic all fit together.
Resourcefulness: Every person within this team is hands-on. As a small team we make the most of our collective knowledge-bases, without any ‘that is not my job’ mentality.
What have you learnt since joining Tickd?
Within the last 6 months I have learnt a great deal both technically and professionally:
Technically: I’ve gained deeper experience in backend development, particularly in building resilient API’s and systems capable of handling significant traffic and complex data.
One highlight was building a live analytics system that provides breakdowns and insights across our hundreds of stacks/brokers with all of our suppliers, with careful data structure design to make data retrieval near-instant and powerful.
Working in a ‘startup’: I’ve learnt how to balance speed with quality, and how to prioritise effectively when almost everything feels important and impactful, and the critical value of clear communication in a small team.
Domain knowledge: A solid understanding of the UK business energy market, switching processes, compliance requirements, and how white-labelled SaaS works in a B2B2C setup.
