~/mentorship
Learn Cloud with Amina. Fund the next engineer.
A 4-month mentorship in Cloud, DevOps and Platform Engineering. You won't follow tutorials. You'll think like an engineer, break things on purpose, and build infrastructure that actually runs. Proceeds go to G3Women.
- 8 modules × 2 weeks
- 4 months
- sessions & code reviews
- Live
- hands-on, real cloud
- 100%
- receives the proceeds
- G3Women
$ cat why.md
A mentorship, not a course.
Most people learning cloud get stuck in tutorial loops: copy a command, watch it work, understand nothing. Then the first real outage arrives and none of it helps.
I'm in the sessions, in the code reviews and in the postmortems. You learn the why before the syntax, at a pace that leaves room to struggle properly, and you leave with a portfolio that proves you can operate real systems.
Where your fee goes: proceeds fund G3Women's programmes for women in digital tech across northern Nigeria.
$ cat principles.yaml
Why before how
Before running any command, you understand the problem it solves and the trade-off it makes. Context first, syntax second.
Break things on purpose
You will break containers, misconfigure IAM and corrupt state, so you learn how systems actually recover.
Document everything
Every module ships a postmortem, a diagram or a runbook alongside the code. Engineers who can explain their work can improve it.
Real infrastructure only
No simulations, no toy sandboxes. You deploy to real cloud accounts and operate real workloads from day one.
$ ./pipeline --stages
Four months, eight modules, two weeks each.
By the end you'll have a running Kubernetes workload, an IaC repo, a CI/CD pipeline, and dashboards proving it all works. Pick a module to see what's in it.
Month 1 · Foundations
Month 2 · Cloud infrastructure
Month 3 · Platforms
Month 4 · Production
$ cat module-01.md
Module 01 · Weeks 1–2 · Month 1
Linux, Networking & Git
The mental models underneath every abstraction: processes, systemd, CIDR, DNS, SSH and Git internals.
$ cat module-02.md
Module 02 · Weeks 3–4 · Month 1
Cloud Fundamentals & IAM
Regions and zones, IAM policy evaluation, least privilege, Workload Identity Federation and audit logs.
$ cat module-03.md
Module 03 · Weeks 5–6 · Month 2
Compute, Storage & Networking
VPC design, Compute Engine, Cloud Storage, L4 vs L7 load balancing, Cloud DNS and Shared VPC.
$ cat module-04.md
Module 04 · Weeks 7–8 · Month 2
Docker & Container Security
Namespaces and cgroups, image layers, multi-stage builds, runtime hardening and image scanning.
$ cat module-05.md
Module 05 · Weeks 9–10 · Month 3
Kubernetes
Run a real workload on Kubernetes and understand what the control plane is doing for you.
$ cat module-06.md
Module 06 · Weeks 11–12 · Month 3
Infrastructure as Code
Describe your infrastructure in code, review it like code, and recover when state goes wrong.
$ cat module-07.md
Module 07 · Weeks 13–14 · Month 4
CI/CD Pipelines
Build a pipeline that tests, builds and ships your workload on every push.
$ cat module-08.md
Module 08 · Weeks 15–16 · Month 4
Observability
Dashboards and alerts that prove it all works, and tell you quickly when it does not.
$ crontab -l
What a module looks like
- 1
Week one: learn & build
A live, recorded session on the concepts and trade-offs, then you start the hands-on lab on your own Google Cloud account.
- 2
Week two: break & fix
A second session for questions, debugging and reviews. You break the thing on purpose, recover it, and finish the lab.
- 3
Deliverable
Each module ends with a postmortem, diagram or runbook, reviewed before you move on.
Why 4 months? +
Cohort 1 ran the curriculum in 8 weeks, and one week per topic was too fast for people working or studying alongside it. Each module now gets two weeks, so there is time to finish the lab, get stuck, get unstuck and actually understand it.
Do I need prior experience? +
No. The programme is designed for beginners. What matters most is commitment: you will need time each week for the lab and the deliverable.
Where does the money go? +
Proceeds from the mentorship go to G3Women Network for Growth, the NGO I founded to close the gap for women in digital tech across northern Nigeria. Your learning funds someone else's.
What do I need to start? +
A laptop, a reliable internet connection, a Gmail account to set up Google Cloud, and Git installed. New GCP accounts come with free credits that comfortably cover the labs.
What timezone are sessions in? +
West Africa Time (UTC+1). Exact times are agreed once the cohort is formed. Every session is recorded.
Do I get a certificate? +
No, and that is deliberate. You leave with a GitHub portfolio of real infrastructure, written postmortems and runbooks, and skills you can defend in an interview.
How big is a cohort? +
Small, so that every lab gets reviewed. Applications are read individually.
Cohort 2 is forming.
Join the waitlist and you'll be the first to know when applications open.