In one 60-minute call a week, you'll turn the Azure you already half-know into a project you can explain in an interview.
Labs, Discord, and me.
A 60-minute call every week · me on Teams in between
I have trained hundreds of people through workshops and one to one, and without fail the thing keeping them out of a cloud job, or stuck in the one they have, is not effort. It is the order they are doing things in.
They usually fall into one of three camps:
All three stall. Twelve months in with a certificate, no interviews or no offer, and no idea why.
All you need to change that is one order to follow and someone to answer to every week. One that ends with something real to talk about. That is what we build here.
It's one 60-minute call a week. Live, one to one, on Pacific Time. Bring what you built and what broke.
It's for people in IT who want a cloud role, or the next one. Helpdesk, support, sysadmin, dev, and engineers already in Azure who want to move up. Beginner is fine. Experienced moves faster.
You get the full CloudLearn catalog. 250+ hands-on Azure, AWS and Kubernetes labs, included. Not a second subscription.
You get me on Teams between calls. Message me directly when you are stuck. Discord is there too, for the group.
You walk out with a project you can explain. Built in your own tenant, broken on purpose, written up. That is the interview.
No job guarantee. Anyone who promises one is lying. I help with the skills, the paper, and the screen. Showing up is on you.
The exact sequence to learn Azure in, starting from where you actually are. Not a catalog of every topic.
Every weekBuilt in your own tenant, broken on purpose, fixed, and written up. Something real to point at.
Your tenantHow you talk through what you built. The paper, the screen, and the questions you will get asked.
The screenThis is the shape. You start where you actually are. You do not sit through "what is a subscription" if you already create resources. You do not skip the floor if you cannot.
Log in. Create a resource group. Create something cheap. Find it. Delete it. Enough networking that a VNet lab is not a foreign language. Then the labs, not another YouTube binge.
One target title. Real postings. One skills list. Rewrite one role so it would survive a screen. LinkedIn and GitHub that a recruiter can actually open. Applications stay paused until the paper is defensible.
Entra as the container. App registration and the two IDs. Same resource in the portal, Azure CLI, and PowerShell. A custom role on paper. Then ARM and Bicep, not a cert dump.
One thing in a tenant you can defend. Break it on purpose. Write what happened. Then you can talk through your own work without freezing. That is the screen. Not a pile of lab badges.
Live, one to one, on Pacific Time. Bring what you built and what broke.
Every week250+ hands-on Azure, AWS and Kubernetes labs, cert paths and quizzes. Yours the day you start.
250+ labsMessage me directly when you are stuck. You are not waiting a week for a forum reply.
Between callsGroup discussion with everyone else I mentor. Ask the room, compare notes, see what others are building.
The groupThe interview screen, rehearsed with me before the real one. Real questions, straight feedback.
Real questionsYour resume rebuilt with me around what you shipped. Line by line, not a template.
Line by lineI knew Azure from work but could not explain it in an interview. We fixed the order, I built the project in my own tenant, and the interview turned out to be the easy part.
I was doing the same three things at work and calling it experience. The weekly call kept me honest, and the labs filled gaps I did not know I had.
I had watched hours of videos and never deployed anything. Six weeks of labs in the right order and I finally had something to talk about.
A 60-minute call every week with Parveen Singh. Labs and Teams in between.
Role, cloud experience, goal. I read every one myself and reply with the fit.
60 minutes · 1:1 · Pacific TimeIf yours is not here, write and ask. I answer those myself too.
Ask me directlyIn practice they are the same engagement. Mentoring is the long arc: the order to learn Azure in, what to skip, and what good looks like at each stage. Coaching is the weekly pressure: what you shipped, what broke, what you send on Monday. You get both.
Yes. You do not need to be able to create a resource yet. Labs are the start. Write me your background and goal.
Yes. Many of the people I work with already do. You know the concepts, so we fill the gaps, build a project past the services you touch every day, and get you ready for the next role. That tends to move fast.
A course is a pile of topics. This is an order, labs you finish, and me live so you do not stall for six months.
No. Anyone who guarantees a job is lying. I will help you with the skills, the paper, and the screen. Applying and showing up is on you.
Yes. Ask in the form. I can send an invoice after we have the fit.
Pick a range on the form. I reply with the fit and the number that matches where you are.
I read it myself and reply with whether we are a fit. If I am not the right person for what you need, I will say so and point you somewhere better.
