Credera UK Meet & Greet
A biomedical engineer who had never heard of the cloud now leads engineers
Fresh out of a biomedical engineering degree, with a thesis on bone cement for hip and knee replacements, she had never heard of the cloud or DevOps. Years later, after doubting her ability as a consultant, Credera UK Managing Consultant Stephanie Quinn is tech lead on a data mesh program overseeing 15 to 20 engineers. What did it take to move from project coordination to hands-on engineering inside the same company?
Get the practical steps she used to pivot into cloud engineering without leaving her employer
In short
Stephanie Quinn, Managing Consultant at Credera UK, introduces the consultancy's services, values and employee networks, then traces her own path from biomedical engineering graduate to technical lead on a data mesh program. She shows how certification, internal practice projects, career coaching and asking colleagues for help let her pivot from project coordination into cloud engineering without changing employer.
“So when I left university, I had never even heard of the cloud.”
“And over time I kind of became a little bit conscious that I hadn't really found that one area of tech that I wanted to specialise in and rightly or wrongly then began to doubt my ability as a consultant.”
What you will learn
- Map how a non-computing degree can lead into technology consulting and then engineering
- Plan a pivot by focusing on one cloud provider and earning a foundational certification first
- Use internal projects as a safe place to gain hands-on experience before client work
- Ask colleagues, coaches and staffing teams to take your aspirations into account when placing you
- Recognise the transferable skills, such as stakeholder and migration planning, that coordination roles build
Key takeaways from the speaker
- Credera's Values
- Credera's Culture
- Experience from one of Credera's great Managing Consultants
Details
- Level
- Beginner
- Format
- Demo
- Technical depth
- Introductory technical
- For
- Early career, Career changer, Mid-career
- Length
- 18:08
- Published
- June 2022
Questions this talk answers
Can you move into engineering without a computer science background?
Stephanie studied biomedical engineering and had never heard of the cloud when she graduated, yet she became technical lead on a large data mesh program.
How did she switch from project coordination to engineering?
She focused on AWS, earned the Solutions Architect Associate certification, attended re:Invent and built an internal AWS landing zone with colleagues before taking a first engineering lead role.
What skills do project and migration coordination roles build?
She gained grounding in project management, planning large migrations of live systems and working with technical and business stakeholders.
What employer support helped her change direction?
She used her training budget and dedicated training time, internal initiatives for hands-on practice, paid career coaching, and a scheduling team that considered her aspirational capabilities.
What areas does Credera work in?
Credera helps clients across strategy, transformation, cloud, engineering and data, and the best projects often combine several of these areas.
About this talk
This meet and greet is an opportunity to hear from one of Credera UK’s managing consultants about what Credera does, how we do it, and her own experience in the company.
Topics
Highlights
- Never heard of the cloud: a biomedical engineer's first tech job (55 s)
- Doubting yourself, then asking for help to pivot (83 s)
- Four practical steps to change direction at work (81 s)
So good afternoon, everyone, and welcome to Credera's Meet and Greet. My name is Stephanie. I'm a managing consultant with Credera. I've been with the company for just over four years, and I'm really thrilled to be hosting this session today. I also have Zane joining me. Zane is an engineer with Credera, and she'll be helping facilitate the session, I think, by keeping an eye on the chat. So please post any questions that you may have for us in there. As the name of the session suggests, today I'm going to introduce you to Credera, a really great company to work for, so I hope I do justice. As well as that, I'm going to talk to you about my career journey with Credera and the lead up to that. And what I really want to demonstrate today is just how varied a career
in technology and technology consulting can be, and even within the same company. So who are we? Credera is a global boutique consulting firm with offices in the UK, the US, India, Mauritius, and Australia. We have four offices in the UK. We have one in London, Leeds, Manchester, and our newest office opened recently in Newcastle. And we've eight offices in the US, and we've recently opened an office just this year in Sydney. And so what does a global boutique consultancy actually mean?
Well, it means that our clients have access to a global wealth of expertise with the personalized approach expected from a local partner. We help our clients across five main areas: strategy, transformation, cloud, engineering, and data. And the best projects often actually encompass multiple, if not all of these areas. And so, for example, at the moment, I am working on a project helping one of our public sector clients to build a data mesh. And my day-to-day will span cloud data and engineering.
However, we also have people on the team whose role it is to actually transform the organization to ensure the successful adoption of what we're actually building. So, I've already mentioned that I'm working in the public sector. But our people have experience working across many different sectors, including energy and financial services. And here's just a selection of the clients that we're currently working with or who we've worked with in the past. And I hope that these kind of first few slides have started to build a picture of the variety which comes with a career in consulting.
So, as well as making an extraordinary impact on our clients, it is part of our mission to make that same impact on our people and our community. And at the heart of this lie our five core values. Our five core values are humility. And so, we consider our clients and our colleagues' interests as more important than our own. And when we are wrong, we learn from our mistakes and work to rebuild trust and confidence. Excellence, we don't try sell the perfect solution. Instead, we take time to really understand the issues and apply our experience to achieve remarkable results.
Integrity, we do the right thing even when no one is watching and no matter the cost. Tenacity, we are focused on driving a project from strategy to successful completion. And last but not least, people first. We treat each person with value and care. We know that individual differences bring strength. I know that every company has something like this, but I guess one of kind of the things that sticks with me and how we kind of embody these values is that we are, I guess, a more practical example is that we are completely vendor agnostic and we don't try and push specific products onto our clients. We make sure that we find the right solution for their requirements and their needs.
So our people really are at the center of what we do and we're immensely proud of the awards that we have received, which reflect this. Something that's very important but actually isn't highlighted on this slide is that this year we were also acknowledged by the Women in IT Awards as Outstanding Diversity Network of the Year 2022. Another way in which we place a strong emphasis on our people is through the networks of support which we have.
And these are really opportunities for people to bring their interests to work. So just to call out a few of these, CRED Climate aims to raise environmental awareness and reduce the company's environmental footprint. And we recently organized a company-wide green week and had a lunch and learn about ongoing rewilding efforts. Our diversity, equity and inclusion team includes groups that focus on gender, LGBTQ+, minority ethnicities and visible and invisible disabilities. We also have numerous self-managed clubs where we can get together and share our interests such as running, gaming and film.
So what is it really like working for Credera? So my aim here is not to give you a sales pitch on why Credera is the best, but actually instead show you a few of the different paths that are available to you when you choose a career in technology and technology consulting. And also just share some practical steps that I took to change the direction of my career whilst working with Credera.
So I've been working in technology consulting for the last eight years and I've been with Credera for four of those years. And while my title is Managing Consultant, my role is kind of much more aligned to our engineering practice. I think all of the boundaries of our roles are quite blurred, but I think, yeah, my experience helps me bring quite a good balance of that technical knowledge and people skills to the role. So currently I'm tech lead for a program building a data mesh, as I mentioned, and at the moment I'm responsible for kind of the quality of the engineering delivery across the program and oversee a team with kind of 15, 20 engineers.
While I am predominantly AWS focused, I have been fortunate enough to work on a variety of different cloud projects where I've also gained practical experience in Azure and GCP. I'm also very interested in DevOps and CICD, and I've used a variety of different tooling for automation, including GitHub and GitLab. And then finally, the mandatory fun fact that must be included, having done very little during the various lockdowns, I recently took up rowing and raced in my first regatta just a few weeks ago.
So there have been a few key moments or turning points in my career and joining Credera was definitely one of those. But for those of you in the session who are maybe at an earlier stage in your career, perhaps you don't have much consulting or technology experience yet. I'll go back a little bit further. So I studied biomedical engineering at university in Dublin. And to give you a sense of just how green I was when I entered the world of tech and my thesis and the last couple of years at university, I focused on looking at bone cement and the ways in which can be delivered into bone to improve fixation of artificial joints when you get kind of a hip or knee replacement, for example.
So when I left university, I had never even heard of the cloud. I had no idea what DevOps was or Python or no idea. And so equipped with my degree in biomedical engineering, then I made the less obvious choice of applying for a role as a graduate financial software engineer with a small startup in London. So during this role, I actually spent most of my time working with just two other graduate engineers and I was studying and learning all about something called KDB Plus, which is a time series database and it has its own language, Q. And this was actually a really tough environment to work in. And kind of within six months, I realised that it really was not the path for me and I sort of cut my losses. But I had heard about this
company called Accenture and a few of my engineering classmates had joined after graduating. So I decided, yeah, maybe this is quite a good middle ground for me. So after attending one of their networking events, I applied to their technology consulting graduate programme and started a short while later. And it's safe to say at this stage that I definitely fell into my career in technology consulting, as I think many consultants probably do. Quite a lot of my projects then over the next four years were networks based with a particular focus on something called DNS and IP address management. And once again, I was completely new to the tech I was working with. And during this time, though, I learned huge amounts about these technologies and also networking and connectivity fundamentals. And I think something
which I didn't quite appreciate, though, at the time, or maybe it just wasn't as obvious to me was some of the other skills that I gained. So I got a really good grounding in project management, how to plan a large migration of life systems, working with a range of technical and business stakeholders and stakeholders and also working with technical teams. And it was actually this last part.
So working with technical teams, which was the most enjoyable part of my role and getting the opportunity to actually understand the detail of what they were implementing. And this was one of the kind of key influencing factors for my move to Credera. So I had heard about Credera through LinkedIn. And when I started doing my research, there were a few things that really resonated with me. First up was just how much they valued their people. And I was acutely kind of aware of, you know, the best places to work awards that they had won even way back then.
Secondly, it was clear that they built really strong relationships with their clients. There was a very strong sense of working in partnership with clients and being trusted advisors. And then finally, kind of based on my previous few roles, I knew that being a consultant with that deep technical expertise was what I really wanted and what was very important to me. And I could really see this in a number of their consultants that I spoke to whilst kind of going through the interview process and also attended a couple of networking events as well.
So my first couple of roles with Credera continued to be quite project management coordinator type roles. And to give you just a better idea of what some of these entailed. And so my first project with Credera was actually as a testing coordinator for an airport group in the UK. And I supported the creation of a test strategy and a test plan for the rollout of a new network at one of their airports.
And then one of my longest running roles was actually as a migration manager on NHS digital's health and social care network migration. And we worked with NHS digital to migrate over 14,000 WAN services and save the NHS millions of pounds a year. And so I actually kind of on a day-to-day basis, then I worked with groups of GPs and hospitals right across London, and two of their new network suppliers to help them through the procurement and the rollout of their new network.
What I realised though, through these roles, as good as they were, was that I really missed working closely with the technology and the technical teams. And over time I kind of became a little bit conscious that I hadn't really found that one area of tech that I wanted to specialise in and rightly or wrongly then began to doubt my ability as a consultant.
So that was the point then that I really leaned on my colleagues and the support that Credera offers to make a positive change, which has since led to some great roles and projects. The dominant factor was that I knew I loved problem solving. So the move towards engineering seemed like quite a natural next step. However, it did take me some time to realise that I could absolutely do this with Credera. I just needed to kind of speak to the right people and ask for help essentially.
So I began by focusing my attention on one cloud provider. At the time AWS was pretty dominant in the market and a lot of our projects were AWS based. So I started by doing an AWS certification and then later that year I actually got to attend the AWS re:Invent conference with three of my colleagues. And this gave me a really great exposure to everything the technology could do.
And it also kind of gave me that language that I needed to communicate with colleagues and clients about it. From there though, I realised that I really needed to get some hands-on project experience before I could work on some of our client projects. So I started working with a team of other Credera consultants and engineers to build out an AWS landing zone for use internally within Credera.
And this is also then when I started learning to use infrastructure as code and Terraformer. Yeah, Terraform is probably what a lot of people know it as. I guess having that safe environment to learn the technology in was an absolute game changer for me as well as having lots of people around me who supported my learning and kind of shared their experience from client projects with me.
So at that point, I then got my first engineering lead role, although there was a very strong sense of Stockholm Syndrome kicking in at that point. It was the perfect first role though for me. It was a quite a short piece of work and it was taking all of the skills that I had learned internally, building out an AWS landing zone such as infrastructure as code, DevOps, CI/CD practices and then being able to apply them to Azure.
And then as I mentioned earlier, I'm now the technical lead for a large data mesh implementation. We have three teams of engineers who are building out different parts of the architecture and this has been a big step up in terms of complexity. However, I have been able to bring that past infrastructure with past experience with infrastructure as code and DevOps and the likes to this project. And I guess, yeah, maybe something to cry is that, you know, there's a huge opportunity to to make things a reality and kind of build teams as a safe environment so that people of all levels can really contribute to the organizations that we help.
So just to kind of summarize the previous slide then into some of the more practical steps that I took. So like I said, I started off with doing a certification and I used some of my Credera training budget and dedicated training time to take my AWS Solution Architect Associate certification. This gave me a really good grounding and it really helped build my confidence with the technology as it was pretty non-existent previously. I took advantage then of Credera's internal initiatives to get hands-on practical experience with the technology I was learning. I also used my training budget to get some career coaching and I was actually, yeah, I was quite apprehensive about this at the start, but it ended up being a really, really practical and just helped me to take the actions
actions that I needed to get moving in the right direction. And then finally, Credera also have a brilliant scheduling team who always kind of took my aspirational capabilities into account when placing me on projects and they found me a series of amazing roles, which again really helped build my confidence in this new role. So that brings me just to say thank you and I guess open things up to Q&A.
Thank you.
Transcribed automatically; names checked against the speaker record. Select a time to jump there.
Frameworks and ideas mentioned
- Data mesh
- Infrastructure as code
- DevOps
- CI/CD
Resources mentioned
- AWS Solutions Architect Associate certification
- AWS re:Invent conference
- Career coaching
- Terraform
Cite this talk
Stephanie Quinn. "Credera UK Meet & Greet." WomenTech Network, 2022. https://www.womentech.net/video/credera-uk-meet-greet-stephanie-quinn
Related talks
Browse the libraryFrom Zero to Cloud Hero: How AWS Solutions Architect Certification Transforms Careers Across Industries
Women earn about 40% of CS degrees, yet hold 19% of cloud roles
Career Hopscotch: Navigating your Journey in Technology
Sideways hops can open doors, even when title and pay stay the same
From web developer to product leader, a ride through startups and unicorns.
She never picked a job for its title, only for what it would teach her
From Physics to Software Engineering – building a non-traditional career path
One code project, zero coding internships, and still hired as an engineer
Designing a Happy Career & Working Happy
Your next career move may not need a promotion or a posted job
From Sweatpants to CEO: How to rethink YOU for the future
A CIO who left the C-suite to bake shows there is still time to pivot