LOADING ENGINEERING LOADING ENGINEERING LOADING ENGINEERING LOADING ENGINEERING LOADING ENGINEERING
LOADING ENGINEERING LOADING ENGINEERING LOADING ENGINEERING LOADING ENGINEERING LOADING ENGINEERING
LOADING CHECK LOADING CHECK LOADING CHECK LOADING CHECK LOADING CHECK
LOADING CHECK LOADING CHECK LOADING CHECK LOADING CHECK LOADING CHECK
LOADING STRATEGY LOADING STRATEGY LOADING STRATEGY LOADING STRATEGY LOADING STRATEGY
LOADING STRATEGY LOADING STRATEGY LOADING STRATEGY LOADING STRATEGY LOADING STRATEGY
LOADING MOTION LOADING MOTION LOADING MOTION LOADING MOTION LOADING
LOADING MOTION LOADING MOTION LOADING MOTION LOADING MOTION LOADING
LOADING BRANDS LOADING BRANDS LOADING BRANDS LOADING BRANDS LOADING BRANDS
LOADING BRANDS LOADING BRANDS LOADING BRANDS LOADING BRANDS LOADING BRANDS
LOADING DIGITAL LOADING DIGITAL LOADING DIGITAL LOADING DIGITAL LOADING DIGITAL
LOADING DIGITAL LOADING DIGITAL LOADING DIGITAL LOADING DIGITAL LOADING DIGITAL
LOADING LOADING LOADING LOADING LOADING LOADING LOADING LOADING LOADING LOADING
LOADING LOADING LOADING LOADING LOADING LOADING LOADING LOADING LOADING LOADING
Reimagine
LOADING LOADING LOADING LOADING LOADING LOADING LOADING LOADING LOADING LOADING
LOADING LOADING LOADING LOADING LOADING LOADING LOADING LOADING LOADING LOADING
0%
LOADING ENGINEERING LOADING ENGINEERING LOADING ENGINEERING LOADING ENGINEERING LOADING ENGINEERING
LOADING ENGINEERING LOADING ENGINEERING LOADING ENGINEERING LOADING ENGINEERING LOADING ENGINEERING
LOADING CHECK LOADING CHECK LOADING CHECK LOADING CHECK LOADING CHECK
LOADING CHECK LOADING CHECK LOADING CHECK LOADING CHECK LOADING CHECK
LOADING STRATEGY LOADING STRATEGY LOADING STRATEGY LOADING STRATEGY LOADING STRATEGY
LOADING STRATEGY LOADING STRATEGY LOADING STRATEGY LOADING STRATEGY LOADING STRATEGY
LOADING MOTION LOADING MOTION LOADING MOTION LOADING MOTION LOADING
LOADING MOTION LOADING MOTION LOADING MOTION LOADING MOTION LOADING
LOADING BRANDS LOADING BRANDS LOADING BRANDS LOADING BRANDS LOADING BRANDS
LOADING BRANDS LOADING BRANDS LOADING BRANDS LOADING BRANDS LOADING BRANDS
LOADING DIGITAL LOADING DIGITAL LOADING DIGITAL LOADING DIGITAL LOADING DIGITAL
LOADING DIGITAL LOADING DIGITAL LOADING DIGITAL LOADING DIGITAL LOADING DIGITAL

From Blueprints to Bugs: How This Architect Became A Software Engineer

Kamsi Etiobi
|
Software Engineer
May 19, 2024

SHARE

On a random, uneventful day in March last year, my friend, JT, unknowingly steered me into Check, by sharing an application link with me — the Checklearn link. 

Hesitant due to my perceived lack of skill and ‘fancy’ portfolio, I thanked her but pushed it aside. Later on that week, she reached out again, practically lifting me by the neck while my legs dangled, and insisted that I MUST apply. So, I took the plunge and did. That was one of the best decisions I made in 2023.

But first, how did we get here? 

It, ironically, all started with me trying to create my architecture portfolio with Wix. After graduation, I didn’t luck into a 9–5 job at an architectural design firm, so I opted for freelance work instead. If you’re familiar with freelance work, you know having a solid portfolio is necessary for survival, and decided to make one by myself.  I didn't know exactly what I was doing but the site came out pretty okay (in my opinion oh!).

So began my curiosity. 

The journey

I started to consume a lot of tech-related content on Instagram and YouTube to understand roles in the tech space. As someone from a design background, my initial interest was in UI/UX, product design, and web design.

I’ve always been fascinated by design and innovation and the ability to solve problems using creative methods. Architecture is still a strong and necessary part of who I am and the kind of work I do. Design, particularly in architecture, demands an unwavering focus on intricacies. It compels you to scrutinize each detail meticulously. It’s not just about seeing individual pieces but perceiving the entire picture all at one glance.

I explored UI/UX through free courses on platforms like Udemy and Simplilearn and tinkered with Figma. However, I personally found the design aspect less fulfilling due to its repetitive nature, and I struggled to grasp the underlying purpose (‘why’) behind the design.

During my exploration, I observed a recurring theme on YouTube channels emphasizing entry into tech industry without coding skills, and that sparked my interest. I wanted to know what exactly it was that people were running away from.

Seeking roles with potentially less competition, I discovered ‘Web Development’ and was captivated by its blend of design and coding- the best of both worlds. Now, transitioning to a new industry isn’t an easy feat, especially after years of studying and investing in a different one. Imagine learning the ropes of a field you are completely unfamiliar with while competing with others with way more experience. 

So I created a roadmap:

  • Learn JavaScript for 6–7 months (January — July)
  • Build websites and a portfolio for 3 months (August — October), 
  • Start internship applications by October. 

However, life had a different plot in store. Remember the Checklearn application? 

In the first week of April, I received my acceptance into the program. To be honest, I was not particularly excited, as I was somewhat unaware of what I had gotten myself into. Nevertheless, there was a sense of pride and joy, having received positive feedback from my first application.

On the first day at the Check office, meeting everyone in person significantly heightened my desire to be a part of the team. That’s when my initial lack of excitement transformed into genuine enthusiasm for being there.

Again, from a background in architecture, I had encountered many ‘uptight’ companies lacking youthful energy. However, at Check, I immediately noticed the team members had a different kind of energy. Even the company’s COO, Charles, also the coordinator of Checklearn, seemed cool-headed and calm. My team lead, on the other hand, proved to be exceptionally funny — perhaps a bit too funny…*suspicious stare

 

How would I describe the programme? 

Rocky. Fun. Fulfilling. Exciting.

I particularly remember the first task given as a ‘warm-up’, I read the brief and went into panic mode, because I assumed this was a ‘Zero to Hero’ program, but this task did not feel like a task for a zero. I even reread the program guide because I was a bit delirious. I was very much unfamiliar with this game. 

However, my tutor highly appreciated the effort I put into the task, and as time progressed, it felt like any contribution I made received sincere acknowledgment from him. Often, he would call other tutors and brag about my work to them. This constant encouragement played a significant role in motivating me to put in 10x more effort.

I found immense joy in the programme, I was always quite jovial with my colleagues and the overall positive environment. I would spend my weekends looking forward to coming to the office the following week. I was just happy to be there.

The pace quickened, transitioning swiftly from basic JavaScript to Vue and Nuxt frameworks. Although I still grappled with tasks, my consistent efforts were quite evident. I learned the importance of seeking help, and regularly reaching out to my colleagues and team lead when faced with challenges.

By July, the Checklearn programme concluded, and I felt a deep sense of pride in my progress within this short span. The conclusion of the program’s first phase marked a significant accomplishment for me. I was now a ‘certified’ software engineer.

After the Checklearn programme, I was one of the people selected to be a part of the Check Spotlight/internship programme due to my performance. I remember sharing the news with my friend, and we both savored the excitement.

The reward for good work, they say, is more work. 

For me, embracing tech wasn’t about chasing high salaries or prestigious roles, it was more of an attempt to stay relevant in this rapidly evolving environment. I wasn’t fixated on the pay, I simply craved fulfillment in my work.

The spotlight/internship stage proved to be even more mentally strenuous than the first. Now, we were dealing with actual company work, and there were lighthearted jokes about the consequences of breaking the company’s code. Jokes of how the police would come to find you if you break the codebase of one of our fintechs. 

My CTO the moment I spoil company code:

__wf_reserved_inherit

I’ll be honest, even though I did really well in the Checklearn programme, the internship wasn’t a bed of roses. Despite the challenges, the rewards of this transition have been worthwhile. Each of us has a unique story navigating uncharted waters in a new field.

For instance, I almost didn’t secure a permanent position at Check, but was given a one-month extension to prove myself due to my positive integration with the Check team. The one-month extension became an opportunity for redemption and you reading this article is a testament that I did indeed prove myself. 

Wrapping Up - TL;DR Lessons

On the 22nd of November, I underwent my final probation review, and I received the coveted handshake of approval from my team lead. 

It felt like a weight lifted off my chest. Knowing that I gave my all and it worked out for me brings a sense of accomplishment. I was highly commended for the significant changes and improvements I made over a short period.

I really lucked out on my journey into tech. Not only did I secure a job at Check, but I also landed in an organization that values design, engineering, learning, and personal growth, all while being surrounded by a group of fun, talented, and supportive individuals. Discovering a workplace with such a harmonious blend of these qualities is truly a stroke of luck and grace.

To end, to anyone navigating new paths, I’ll leave you with a few notes:

  • Enjoy the process and be present
  • Become comfortable with the unknown and strive to know
  • Make mistakes and make them early
  • Committing to daily efforts, even in small increments, is more effective than occasional bursts of intense work.
  • Be true to yourself, and most importantly, 
  • Allow life to just happen. 

Amidst the plans I made for myself at the start of 2023, only a few unfolded exactly as intended. Allowing life means that, despite having plans and goals, it is crucial to leave room for life to happen. It’s a reminder that adaptability is integral to life, and anything can truly happen.