From Courtrooms to Code: My Software Engineering Adventure - Part 2

Correcting and summarizing CV details

The user seems to want help with two things: fixing typos in a paragraph and completing a final paragraph summarizing their skills based on their CV. First, I'll correct the given text to eliminate any typos. Then, I'll add the summary paragraph, mentioning key skills like AWS expertise (Lambda, CDK, SNS, etc.), Node.js, Python, React, the ability in backend systems, CI/CD, Terraform, and Kubernetes. I'll make sure both parts are clear and succinct before presenting the final output.

Thought for a few seconds

Around the time my NYSC programme was finishing, I decided to enroll in a tech school. I went to a bootcamp where I learned full‑stack software engineering, focusing on the MERN stack. While at the bootcamp, I knew the aim was to get employed, so when I had completed two‑thirds of the programme, I didn’t wait for it to finish—I started applying for jobs online.

Frontend came easily to me, perhaps because of my background in UI/UX and graphics design, so I wasn’t surprised when I got my first job as a frontend engineer using React and TypeScript at a startup building SaaS tools for SMEs in Nigeria. The job was an internship, but I didn’t mind because I was focused on the big picture—the environment was conducive for learning, and I learnt a lot there.

After about three months, I knew I needed more money as the workload was growing but my salary was still ₦50K, so I started applying online again. I focused on frontend roles with React and TypeScript—and that’s what I landed next.

My next role paid better, but the company lacked clear direction. We spent months building a B2B e‑commerce application, only for the CEO at a review meeting to announce she’d assumed it was both B2B and B2C. At that point, I realised the company wasn’t moving forward. I learnt the value of working somewhere with clear vision and momentum.

I knew I’d have to move on eventually. A friend introduced me to cloud computing with AWS and suggested I pivot from frontend to backend and DevOps. After a while at that company, I quit and gave myself three months for personal development. I spent that time building backend projects and getting familiar with AWS services.

I applied again and secured a role as a Backend AWS Engineer at a service‑based company, which was instrumental in my growth as a DevOps engineer. I was involved in building multiple products using AWS services, and it helped me develop expertise in scalable, automated infrastructure.

Not long after, a friend asked me to send my CV to his company, which was hiring backend engineers with AWS DevOps experience. I got the job, and, after a short overlap, I left my previous role to focus entirely on this one. This position—my current company—has been pivotal in accelerating my growth.

I’ve since used AWS services extensively—Lambda, API Gateway, SNS, SQS, DynamoDB, Redis, EKS, ECR and more—alongside infrastructure‑as‑code tools like Terraform and AWS CDK. I’ve built scalable microservices and serverless architectures, managed SSL certificates and custom domains with ExternalDNS, containerized applications using Docker and Kubernetes, and set up CI/CD pipelines with GitHub Actions. My backend expertise in Node.js and Python, combined with solid React experience, allows me to deliver end‑to‑end solutions that are secure, efficient, and production‑ready.

I’m grateful every day for the path I chose—one that challenged me to push beyond my comfort zone and continually learn in the fast‑paced world of cloud and backend engineering. Each twist—from UI/UX roots to mastering AWS services, Terraform, and Kubernetes—has sharpened my problem‑solving skills and deepened my passion for building scalable, impactful solutions. As I look ahead, I’m excited to keep growing, tackle new challenges, and contribute meaningfully to projects that make a real difference. This journey has not only shaped my career but also affirmed that following my curiosity and dedication was the best decision I could have made.