Building cloud infrastructure, automating deployments, and shipping real projects. Trained at NextGen Playground. Founder of She Builds Tech.
My name is Loweh Goodness. I am a DevOps engineer building hands-on experience in cloud infrastructure, CI/CD automation, and containerised deployments.
I come from a background in logistics and supply chain management. That experience taught me what it costs when systems fail and why automation is not optional. It is what pushed me into engineering.
I trained at Primus Learning and am currently building production-grade projects at NextGen Playground, where I have gone from theory to real deployed infrastructure on AWS.
Tools and technologies I have built real hands-on experience with.
Real projects built and deployed. Every one of these is in production or has been run end-to-end.
A Jenkins CI/CD pipeline that automatically builds, tests, and deploys a portfolio website as a Docker/Nginx image with Slack notifications at every stage. Multi-stage Jenkinsfile: Checkout, Build, Test, Push, Deploy.
How Jenkins orchestrates multi-stage pipelines from a Jenkinsfile. Debugging container networking on the jenkins_default network, fixing curl output parsing in test scripts, and wiring Slack webhooks for real-time pipeline notifications.
A containerised web application with a complete GitHub Actions CI/CD workflow. Every push to main triggers a build, pushes a Docker image to Docker Hub, and deploys automatically with zero manual steps.
Wiring Git to deployment end-to-end. Managing secrets in GitHub Actions, Gitflow branching with PR-based merges, and how one broken pipeline step reveals gaps in your whole mental model of the system.
Provisioned AWS EC2 instances and S3 buckets using Terraform modules for reusable, clean infrastructure. Configured a remote backend for state management — infrastructure as code done properly.
Why remote state matters the moment you work with a team. Modules make Terraform readable and reusable. State locking prevented a race condition that would have corrupted the infrastructure state file.
Built and deployed this portfolio site with a custom domain at lowehtech.com. Configured DNS records on Cloudflare, enforced HTTPS, and set up automatic deployment on every push to main via GitHub Pages.
DNS propagation is not instant and TTL matters. Cloudflare proxying vs DNS-only mode behave very differently. Deploying your own site publicly forces you to understand the full stack from commit to browser.
Responded to a real AWS credential exposure incident. Terraform secrets were accidentally committed to a public GitHub repository, triggering unauthorised EC2 launches within minutes. Submitted an AWS Trust and Safety case, rotated all credentials, and remediated the breach.
One push to a public repo with secrets exposed can spin up infrastructure in seconds. Add to .gitignore before you commit, never after. IAM least-privilege is not optional. AWS Trust and Safety responds fast if you are transparent and act immediately.
The practical engineering work I can contribute to a team from day one.
I build automated pipelines using Jenkins and GitHub Actions. A push to main triggers build, test, and deployment automatically. No manual steps, no forgetting to deploy.
I package applications into Docker containers, write Dockerfiles, manage images on Docker Hub, and make sure what runs locally runs exactly the same in production.
I provision and manage AWS infrastructure — EC2, S3, IAM, VPC. I know how to configure it securely, keep costs in check, and document what I build.
I use Terraform to define infrastructure so it is consistent, version-controlled, and reproducible. No more manual clicks in a console that no one can remember or repeat.
I set up Prometheus, Grafana, and UptimeRobot so the team knows about problems before users do. Dashboards, alerting, and uptime checks from day one.
Every project I touch gets a proper README, architecture notes, and clear steps to reproduce. Good documentation is engineering work, not an afterthought.
The values that guide how I work, not just what I build.
If a human is doing it more than twice, a machine should be doing it. Manual processes are technical debt in disguise.
Infrastructure that cannot be version-controlled, reviewed, and reproduced will eventually fail you silently.
Secrets hygiene, IAM least-privilege, and HTTPS are not nice-to-haves. I learned this the hard way in production.
A system you cannot observe is a system you cannot trust. Metrics, logs, and alerts are how you sleep at night.
If another engineer cannot understand what you built without asking you, it is not finished. A README is part of the deliverable.
Writing about what I am building forces me to understand it more deeply. Strong engineering cultures share knowledge, not just code.
She Builds Tech is a community for women in tech and women transitioning into the industry. I started it because I wanted more women to know there is space for them in this field — and that they do not have to figure it out alone.
We share stories, build skills, and support each other. Because when one woman makes it, she opens the door for others.
DevOps Engineer · Cameroon · Building infrastructure by day, building community always. She Builds Tech was founded so no woman has to figure out tech alone.
Equipping women with the knowledge and confidence they need to break into tech, no matter where they are starting from.
Sharing real stories of women in tech so others can see themselves in those journeys and know it is possible.
A space where women support each other, share resources, and grow together in their tech careers.
Removing the barriers that keep talented women out — mentorship, resources, visibility, and honest conversation about the real path in.
Making sure more women are visible in DevOps and cloud — because seeing yourself in a space is the first step to believing you belong there.
I am looking for opportunities where I can do real engineering work, contribute to a team, and keep growing. I show up prepared, ask good questions, and put in the hours to figure things out.