What is your background experience as a Development Director and what did you do before joining SteadyGo?
I started my career with Jo and Jason who founded SteadyGo all those years ago as a junior developer at another agency. Shortly after they left that agency, I joined them as lead developer for SteadyGo.
As for experience, I didn’t have any in this role having risen through the ranks! I think that has given me great perspective of what’s involved in the roles of our dev team as I’ve done them all myself. Jo and Jason also taught me a lot about business and how to manage people which I hope has made me into a good Director!
What does the role of Development Director entail?
I’m essentially in charge of all things dev and tech related at SteadyGo. I look at new technologies and see if they might be useful to us, manage our developers and help them if they are stuck, I refine our processes and try to automate things and most of all I write code! (Among the many other things everyone in a small business needs to do).
What is your process of working when taking on a project, and are there any methods you find particularly useful?
Obviously, things differ based on the type of project, but I try to be methodical when taking anything new. I think the first and most important thing to understand is what the purpose of the project is and why the client has sent us the brief. There’s no point going barking up the wrong tree as it wastes time and budget which are critical to both us and the client!
Once we really understand what the goal is, we can plan a strategy to get the most out of the client budget and timelines to give them the best value.
What do you find to be the most challenging aspect of your role at SteadyGo?
I’d say trying to balance completing client work while improving process and trying to advance staff knowledge at the same time!
What do you find to be the most rewarding aspect of your role at SteadyGo?
When someone says they really enjoy working for SteadyGo! We spend a lot of our time at work, it’s nice to see that it’s not a chore!
What advice would you give to anyone wanting to follow your particular career path?
Code, code and more code. Write code, read code, learn about infrastructure, different languages, different tools. Working for an agency no two jobs are the same, having a wide range of experience with different technologies means you can solve lots of different problems.
Keep an eye on the wider tech landscape as things move quickly but don’t jump on a bandwagon for the sake of it. Finally, not everything is about code, being a team player and getting on with your co-workers is as important as your technical knowledge.