Name: Ronnie Kilsbo
Job title: Senior Consultant / Tech Lead
Length of service: 1.5 years at Amido.
At 7.45am. Once I wake up and get myself slowly together I then catch up with all my communication at around 8.15am, looking at how I should prioritise my day. Basically, this is my no noise ramp-up moment.
At around 8.45am I leave for Clapham Junction Railway station, and depending on where I’m going, I either jump on a train to Waterloo/Victoria to get to my client, or I take the Overground to Shoreditch High Street to get to the Amido offices. My commute is pretty simple, even though we all know some days can be a pain, when commuting in London.
As a Tech Lead at my current client, my role is quite varied. I focus on the bigger picture of business requirements and architecture of the solutions to fulfil the requirements. Most of the time, I’m working on investigations and proposals for future development. It can be an identity management solution, integration platform, release management process and so on.
When I left my last employer, I was looking for a role where I got to work with cloud native solutions rather than on premise ones. I also like variation, which a consultancy most likely will give you. Amido focuses on project scope and cloud first solutions, so when a recruiter emailed me about this, everything went quickly. I signed three days after reading that email. I’ve worked at smaller, growing companies like Amido before, and immediately recognised the vibrant environment these companies bring.
Frankly, I don’t have a typical day, and that’s one of the perks with my current role. Some days might be pure meetings, discussing or presenting future solutions, but also project steering, architectural meetings and topics like that. Other days I might be directly involved in sprint task work with my team. I’m often in talks with my team to get their input on current work but also around future solutions. I need to know their experience and thoughts about current and future topics, to be able to make more precise assessments and choosing the “right” next steps. It’s very important to me that it is a team effort rather than tech authority.
I think the most rewarding part of my role is mentoring more junior team members. Having someone asking me questions and giving me answers on mine, is just amazing and keeps great conversations going.
The most challenging thing is without a doubt getting everyone on the same page. Sometimes when planning and implementing moves fast, this can become more difficult. Normally, in our daily scrum meetings there is not enough time for this, and team members have tasks to work on, so it is important not to use up too much of their time and find a simple solution.
The directors are working hard on creating a safe, enjoyable and rewarding work environment at Amido, and they are doing a very good job at this. You get opportunities to engage in various competency areas, social activities, and knowledge transfers using internal talks, but also engaging publicly with Amido hosted meetups. Amido also promotes employer initiatives, so if you have an idea, that might just get picked up, and maybe even earn funding for execution.
We are in a business of constant evolution, and right now the pace of this evolution is just mind blowing. For me personally, it’s all about the cloud and how the cloud can change the game in many ways. It changes how you write software, how you deploy software and the fact that something I might have created just 5 years ago would cost maybe 50-100 times more than creating the same solution in the cloud today. I also like the idea that the cloud doesn’t only lower operational costs, but also leads to a much smaller environmental footprint than before.
It’s difficult to rank one over all the others, but I would say the upskilling strategy that Amido has, like the £2000 per person yearly budget for training, but also upskilling through participating in Amido’s various competency group activities, really shows that Amido is a people first company, and is very beneficial for your personal development.
I think that if you’re coming from a Senior Engineer role to work as a Tech Lead, just face it, you’re not going to be the main implementer anymore, the engineers of your team will be. It’s a transition, be prepared. But also, you will be working more on proof of concepts and investigations, which is really fun to do!