Let me be upfront: a certification has never made anyone a good engineer. I collect them anyway, and here's my reasoning.

Left to myself, I learn in an unstructured zigzag, whatever the current project needs. Certifications force breadth. Studying for Oracle Cloud Infrastructure Foundations made me learn the parts of OCI I would never have touched voluntarily, and some of it turned out to be immediately useful.

Where I am right now:

• Done: Oracle Cloud Infrastructure 2025 Foundations Associate (1Z0-1085-25).
• In progress: AWS Cloud Practitioner Essentials and AWS Technical Essentials, formalizing what I already use daily (S3, CloudFront, WAF, Lambda) so the knowledge has fewer holes.
• Alongside: Oracle APEX Foundations, Google Cloud Arcade, and DevOps tracks through Infosys Springboard.

My one rule: every cert has to connect to something I've actually built. The OCI material maps to cloud fundamentals I use on AWS. The AWS tracks map directly to how this site is hosted. If I can't point at a project where the knowledge landed, the cert was decoration.

The fellowship side, Keploy API Fellowship (selected from 18,500+ applicants) and Headstarter AI, works the same way: structured pressure to learn things I'd otherwise postpone forever.

I'll update this post as the roadmap moves. It's a living note, mostly for accountability.