I’m writing this piece because I tweeted this last year
Clearly, I never got round to writing it, but then someone asked for a link in the replies nearly 2 years later and at this point, it’ll be criminal to not write the piece.
I’m going to try to make this as practical as possible, but the truth is transitioning requires a lot of intention on your part, and so if anything comes off as common sense then I guess it’s really up to you to execute on what you already know. I’m not going to give you actual steps, instead, I’ll approach it from a mindset perspective (things to know or consider as you begin your journey) because I think having the right mindset trumps following a series of steps.
For context, I moved from Commercial Banking into a Business Analyst role in an Agile team focused on Innovation and Digital Enablement a couple of years ago.
That said, here goes.
- Figure out what interests you 🤔: It goes beyond code or no-code roles. The first step I think is to identify the sort of work that interests you, and what competencies you possess relative to that work. In my case, I felt like I was an idea machine with strong analytical and communication skills. In addition to this, I had zero interest in writing code, so the day I saw a Business Analyst job description, it jumped at me and I explored that opportunity. It may be useful to transition into roles where you have some transferable knowledge, but this isn’t cast in stone as I believe we can all learn anything. In my case, my time in Commercial Banking gave me the financial context I needed to work in the role and it was within the same organization, so all I had to do was build my understanding of concepts in tech.
- No such thing as “sunk cost” 💪🏿: The amount of time you’ve spent in your existing role should not be regarded as a con when you’re trying to move. In my case, I moved a couple of months after getting promoted. I was highly rated within the team and took what I thought was a gamble in moving (in retrospect, it was inevitable. I don't like sales/finance like that). If you’ve not had much success in your current role, then I can imagine that it’ll be an even easier decision, but don’t let the fear of the unknown or “starting over” hinder you from taking that next step. It doesn’t work that way. Your past experience isn’t going anywhere and will always be a plus.
- Brace for hardship 😅: You need to know and accept that you likely won’t be hot stuff immediately you move (unless you’re an exception and really shouldn’t be reading this), and mistakes will be made in your early days. Those mistakes will speed up your learning process and ensure you never make them again. You may also find that you’re having to google everything, and nothing makes any sense, but embracing that ambiguity and not relenting is crucial; you won’t be the office olodo forever. If you’re looking to move from sales/finance into roles that involve writing code, prepare to work twice as hard to keep up your motivation. It’ll be a steep but very rewarding learning curve.
- Don’t be greedy you detty pig 😒: If all you’re doing is applying for senior roles because you’re hoping to 23x your income, you may be searching for a while, and if by some miracle (miracle because there’s almost no chance you won’t get found out during the interviews) you get into such a role, it’s very likely you will be found out very quickly. If you’re able to make a horizontal move and maintain or increase your income, then that’s great, but a pay cut isn’t necessarily a bad thing especially if you’re going to play the long game.
- Talk to people 👋🏿: Join communities and talk to experienced people in the role you’re targeting. Communities are a good way to find job opportunities, especially if you’re just starting out, plus communities will help you identify openings/companies you should be avoiding (yes, there are horrid companies on both sides of the tech/non-tech divide).
- Certifications don’t really pop here like that 🤓 : Finance people in Nigeria have an unholy obsession with certifications and degrees; MBA, CFA, ACCA, ICAN, MSc., CIBN, etc. This isn’t really a thing in tech, so abandon that mindset and only take certifications that contribute directly towards improving your skillset and not because you think it’ll look good on a CV (I’m looking at all of you with PRINCE2 and HSE working as Account Managers). You’re better off taking free and paid courses on the specifics you’re interested in, especially those Google courses. A recruiter that is swayed by certifications and degrees alone will likely have an organization full of charlatans (in my opinion) and that’s not the sort of organization you should be working in.
- Apply! x3 📝 : Target great companies and apply. Check with your community members and search for what people say about the companies you apply to. Practice for your interview and be honest with your assessment of your abilities. Highlight your transferable skills and your motivations if asked. Fintechs in particular often lack people with banking/finance context in many positions so that’s an advantage for you, and one that will be difficult to ignore by any (competent) recruiter.
That’s pretty much it and I hope this is useful for you. You can connect with me on Twitter @Mr_Oyedele and send me a DM if you need a bit more clarity. Good luck!
