For graduates with no experience · cloud & DevOps focus
How to apply when you have no experience
An honest, practical guide, the exact steps, sites, search terms, and messages, written to actually help you make progress, not motivational fluff. The examples lean cloud and DevOps, but the playbook works for any first tech role. We cannot promise you a job, nobody honestly can, but we can make sure your effort goes where it counts.
1
deep project beats five shallow ones
1 page
resume, project-led
5-10 / wk
tailored applications, a sustainable pace
most
applications get no reply, that is normal
Rough rules of thumb to calibrate your effort, not guarantees. Your numbers will vary.
Start here
The honest reality
The entry-level market is genuinely hard right now, and getting your first job takes more applications and more time than anyone tells you. None of that is a reflection of your worth, and you are not the only one. What follows is not a shortcut or a guarantee, it is the concrete, practical steps that actually work, done consistently.
- There is no trick that skips the work. The people who get hired build real skills and apply widely.
- It is a numbers game on top of a skills game: strong applications, sent steadily, over weeks.
- Rejection is the default, not a verdict on you. Almost everyone who got hired collected a pile of nos first.
A win you can get today. Today: pick one role title you would realistically apply for and read three real job posts for it. That is your whole task for now.
Start here
Everything in this guide is in your control today. Read it once, then start acting this week. Aim for steady progress, not perfection.
Your application
Strengthen your resume
As a graduate, your resume is not weak because you lack jobs, it is weak when it hides what you can actually do. Lead with skills and projects, describe them by what you built and decided, and keep it honest. A clear, project-led one-pager beats an empty chronological template every time.
- One page. A recruiter spends seconds on it, so every line must earn its place.
- Lead with a strong Projects and Skills section. Education and any part-time or internship experience come after.
- Describe each project by what you built, the tools, and the outcome or decision, not just a list of technologies.
Things to have
- A links line at the very top: email, phone, and clickable GitHub and LinkedIn URLs.
- 2 to 4 projects, each with one line of context and one or two lines of what you did and the result.
- A focused Skills section listing tools you can actually discuss, grouped (languages, cloud, tools).
- Consistent formatting, plain fonts, exported as a PDF named Firstname_Lastname_Resume.pdf.
Things to avoid
- Photos, age, marital status, and long objective paragraphs. They add nothing and can invite bias.
- Skill bars or percentages (80% Python). They are meaningless and interviewers ignore them.
- Walls of text, two-plus pages, and tiny fonts to cram more in.
- Listing every tool you have ever touched. If you cannot answer one question on it, leave it off.
Weak
Made a task app with React and Node.
Good enough to start
Built a task-tracking app (React, Node) and deployed it free on Vercel; wrote a README with setup steps and a screenshot. github.com/you/project
Strong, aim here over time
Built and deployed a containerized task-tracking app (React, Node, Docker, AWS EC2) with a one-command CI/CD pipeline; wrote the infrastructure and docs. github.com/you/project
Do this
- Structure top to bottom: Name and links, then Skills, then Projects, then Education, then any experience.
- Write each project bullet as: what it does, what you built or decided, the tools, and the outcome or live link.
- Use a clean free template (Google Docs, FlowCV, or Rezi). Avoid heavy graphics that break the ATS scan.
- Mirror the wording of the job post for the skills you genuinely have, so the ATS and the recruiter both see the match.
Free tools to build your resume
A resume with no clickable GitHub link is a resume with no proof. The links line is the single most important row on the page.
Resume and cover-letter teardownsBe findable
Build a LinkedIn profile that does the work for you
Recruiters search LinkedIn constantly, so a complete, specific profile quietly brings opportunities to you. As a student you have more to show than you think: your degree, your coursework projects, and what you are learning right now all belong here, described clearly and honestly.
- Complete every section. Half-finished profiles rank lower in recruiter search and look unfinished.
- Be specific about what you do and want, a vague profile is invisible.
- Your profile should tell the same honest story as your resume, just with more room to explain.
Headline
Not just 'Student'. Say what you are and what you are aiming for, in plain words.
- Good: 'Computer Science graduate | Aspiring Cloud Engineer | AWS, Docker, Python'.
- Weak: 'Student at X University' or 'Looking for opportunities'.
About (your bio)
Three to five short sentences, first person, no buzzwords. Who you are, what you can do (point to a project), and what you are looking for. End with how to reach you.
- Sentence 1: who you are and your focus.
- Sentence 2 to 3: what you have built, naming one real project.
- Sentence 4: the kind of role you want.
- Sentence 5: a simple call to connect or email.
If you are at university: use the Education section fully
Under your degree, you can list relevant coursework, and add your university projects as their own entries with real detail. This is where 'no experience' is answered.
- Add each significant project under Education or in the Projects section: what it did, your role, the tools, and a link to the repo or live demo.
- Treat a serious coursework or capstone project like a job entry: 2 to 3 bullet points of what you did and the outcome.
- Add the Skills section and pin your top projects so they appear first on your profile.
Using AI (like ChatGPT) to improve your wording, responsibly
A free AI chat tool such as ChatGPT, Google Gemini, or Claude can help you phrase things clearly and fix grammar, especially if English is not your first language. Use it to sharpen your own true words, never to invent achievements.
- Do: paste your honest draft and ask it to make it clearer, more concise, and professional.
- Do: ask it to remove emojis, hype words, and anything that sounds exaggerated.
- Do not: ask it to add accomplishments you did not do, or to write in a voice that is not yours.
- Always read the result out loud. If a line is not something you could say and defend in an interview, change it.
Do
- A clear photo, a specific headline, and a complete About section.
- Real projects with links, listed with detail under Education or Projects.
- Plain, professional language in your own voice.
- Turn on 'Open to work' for recruiters and keep your location and target roles set.
Avoid
- Emojis, slogans, and buzzword soup ('passionate ninja rockstar').
- Leaving About, Skills, or Projects blank.
- Copy-pasting an AI bio you would not say out loud.
- Claiming titles or skills you cannot back up in conversation.
No emojis anywhere on your profile or in your messages. They read as unprofessional to most hiring managers and add nothing.
The biggest lever
Build projects and host them where people can see
The reason 'no experience' feels like a wall is that employers want evidence you can do the job. A real project, public and explained, is the closest thing to experience, and it is fully in your control today. One project you understand deeply beats five you copied.
- Build one real project end to end, then be able to walk through every decision in it.
- Make it visible: put the code on GitHub and, if it can run, host it for free so there is a live link.
- The moment a stranger can open what you built and you can explain it, 'no experience' stops being true.
A win you can get today. Today: create a GitHub account and a single empty repo for your first project. Starting beats planning, you can fill it in tomorrow.
Put it on GitHub with a real README
- A stranger should open the repo and understand it in two minutes.
- README: what it does, a screenshot or short demo, a simple diagram, how to run it, and what you would improve next.
- Pin your 1 to 3 best repos to the top of your GitHub profile.
Host it for free so there is a live link
- Static site or portfolio page: GitHub Pages (free, straight from a repo).
- Web app (frontend or full-stack): Vercel or Netlify free tier.
- Backend or container or cloud project: a free-tier service like Render, or a free-tier cloud VM.
- Put the live link at the very top of the README and on your resume.
Reference it everywhere
- Resume: the project bullet ends with the GitHub link (and live link if any).
- LinkedIn: add it under Projects or Education with the same links and a couple of detail lines.
- Write one short post about a hard problem you solved in it. It roughly doubles the value of the project.
What counts
- Something you built and operated: an app deployed to a cloud provider, containerized, with an automated deploy.
- An app real people could use, with login and a database, or a useful tool you actually finished.
What does not (on its own)
- A tutorial you cloned with no changes of your own.
- Twenty tiny half-finished repos. One deep project you can talk about for twenty minutes wins.
Apply smarter
Tailor your application to each job
The same resume sent everywhere is how strong candidates get filtered out. You do not rewrite it each time, you adjust it to match the specific job, so both the automated scan and the human see an obvious fit. Aim for the right roles, then make the match clear.
- Target junior, associate, graduate-scheme, apprenticeship, and internship roles, not senior postings.
- The 60% rule: if you meet about 60% of the requirements and most of the truly required ones, apply. Job posts are wish lists.
- Quality over volume: a smaller number of tailored applications beats blasting the same one everywhere.
A win you can get today. Today: take one job post you like and one resume, and just match the wording on the skills you genuinely have. One tailored application is a real win.
Weak
One generic resume sent to 200 postings with no changes.
Strong, aim here over time
A base resume, lightly adjusted per job: relevant skills first, matching keywords present, summary naming the role.
Do this
- Read the job post and pick out the key skills and exact words it uses. Make sure the ones you genuinely have appear on your resume in the same words (this is what gets past the ATS).
- Reorder your Skills and Projects so the most relevant ones to this job are first.
- Adjust your one-line summary to name the role you are applying for.
- Search the right titles: Junior / Associate / Graduate / Cloud Support / Cloud Engineer I, and adjacent doors like IT Support and Technical Support that lead into cloud teams.
- Apply on the company's own careers page in addition to the job board, it often reaches a human faster.
Tailoring does not mean lying. You are surfacing the true parts of your background that matter most for this role, not inventing new ones.
Aim wide
Where to apply, and what each kind of company is really like
As a graduate, do not narrow yourself to one type of company. Each kind offers a different first experience, and any of them can be a great start. Apply broadly: your first job is a launchpad, not a life sentence, and the experience you gain opens the next door.
- Apply to all the types below that you can reach. Casting a wide net is how you get a first yes.
- Your first role is about getting in, learning fast, and building real experience, not about being perfect.
- After 1 to 2 years of real experience, far more doors open. The hardest one to walk through is the first.
An honest look at each, none is strictly better, they trade off differently.
Large company / MNC
Structured, stable
- Best for: structured training, mentorship, brand on your resume.
- Reality: slower pace, narrower role, more process.
- Growth: steady and clear, but can feel slow.
Startup
Fast, broad, riskier
- Best for: doing a lot, fast, across many areas.
- Reality: less structure and mentorship, higher risk, equity that may be worth little.
- Growth: rapid skill growth if you thrive in chaos.
Product-based
Builds its own product
- Best for: deep work on one product, strong engineering culture.
- Reality: competitive to enter, high standards.
- Growth: excellent technical depth and good pay over time.
Service / consultancy
Builds for clients
- Best for: getting in the door, exposure to many technologies and clients.
- Reality: client-driven work, varied quality, often a common first job.
- Growth: a solid stepping stone; many move to product companies after.
Avoid only the genuinely bad actors: anyone who charges you to work or apply, asks for deposits, or makes guarantees. Otherwise, a real first job almost anywhere beats waiting for a perfect one.
Build a week-by-week planThe hidden path
Ask for referrals the right way
Many roles are filled through referrals before they are ever a cold application, because a referral puts your resume in front of a human instead of a filter. You do not need to already know people, you build those connections respectfully, and you ask in a way that is easy to say yes to.
- A warm referral often beats fifty cold applications, so one real connection is worth real effort.
- Earn it first: a genuine conversation or some visible work before you ask, never a cold demand.
- Make it easy and low-pressure: give them everything they need and an easy way to decline.
Do this
- Build the connection before the ask: comment thoughtfully on engineers' posts, ask one genuine question, share your own work. Be a real person, not a pitch.
- When you ask, attach your resume and the specific job link, and a two-line note on why you fit, so they can act in one click.
- Always give an easy out ('completely fine if not'). It makes people far more willing to help.
- After they refer you, thank them, and tell them the outcome later. That keeps the relationship for next time.
Cold intro to an engineer (asking, not pitching)
Hi [Name], I am a recent graduate teaching myself cloud engineering. I just built and deployed [one-line project and link]. I saw you work on [their team or product] at [company]. Could I ask one quick question: what helped you most when you were starting out? No worries if you are busy.
Referral ask (only after you have actually talked)
Hi [Name], would you be comfortable referring me for the [role] opening on your team? I have attached my resume and the project I mentioned, and the job link is here: [link]. Completely fine if not, and thank you either way.
Stay on their radar
Follow up professionally during the process
A short, polite follow-up shows genuine interest and keeps you front of mind, without being pushy. The rule is simple: one clear message, then patience. Email is usually best; a call only if they invited it.
- Follow up about a week after applying, and within a day after each interview.
- Keep it short, specific, and warm, never demanding or repeated daily.
- Send one message and then wait. Chasing too often hurts you more than silence does.
Do this
- After applying: if you can find the recruiter or hiring manager, one short note of genuine interest, with your project link.
- After an interview: a same-day thank-you that references something specific from the conversation.
- If you have heard nothing in the timeframe they gave: one polite status check, then leave it.
- Prefer email for a written record. Only call if they explicitly offered a call or asked you to.
Follow-up about a week after applying
Hi [Name], I applied for the [role] last week and wanted to express my genuine interest. I built [project link], which lines up closely with what the role needs. I would welcome the chance to discuss it. Thank you for your time.
Thank-you within a day of the interview
Hi [Name], thank you for taking the time to speak with me about the [role] today. I especially enjoyed discussing [specific topic]. It reinforced my interest in the team, and I am happy to share anything further that would help. Thank you again.
Polite status check (only after their stated timeline)
Hi [Name], I hope you are well. I wanted to check in on the [role] process, as I remain very interested. Please let me know if there is anything else I can provide. Thank you for the update whenever you have one.
When you get a yes
Handling your first job offer
An offer is something to be proud of, and it is normal to feel unsure about the money part. For a first job, the most valuable thing is usually getting in and gaining real experience, the foot in the door compounds for years. It is fine to ask one respectful question about flexibility, but do not risk a genuine opportunity over a small gap.
- Understand the offer first: base salary, total compensation, and any equity. Equity at a startup is usually worth little until the company succeeds, so weigh the base.
- It is acceptable to ask, once and politely, whether there is any flexibility, especially if you have a concrete reason.
- For a first role, experience and growth often matter more than squeezing the last bit of salary. Do not lose a real opportunity over a small amount.
Do this
- Thank them sincerely and ask for the offer in writing, and for a little time to consider it (a day or two is normal).
- If you want to ask about pay, do it once, respectfully: 'I am very excited about this. Is there any flexibility on the base?' Then accept their answer gracefully.
- Never invent competing offers or lie about other numbers. It can be checked and it destroys trust.
- Look at the whole package: learning, mentorship, the team, and growth, not only the number. For a first job these often matter more.
Asking about flexibility (respectful, once)
Thank you so much for the offer, I am genuinely excited to join. Before I confirm, may I ask if there is any flexibility on the base salary? I am very happy to discuss. Either way, I am keen to move forward.
This is general guidance, not financial or legal advice, and norms vary by country and company. Be honest, be gracious, and remember that a strong first job is a launchpad. Accepting a fair first offer is rarely a mistake.
Stay in the game
Handle rejection without burning out
This is the part that quietly ends most job searches, not lack of skill, but giving up after a run of rejections. Rejection at this stage is normal and mostly not personal. The goal is to stay in the game long enough, while improving, for the odds to turn.
- Expect a lot of nos and silence. It is the process working normally, not a signal to stop.
- Take one lesson from each round where you can, then let it go.
- Protect your energy: a sustainable steady pace beats frantic bursts followed by quitting.
A win you can get today. Today: start a wins note and add one thing, a callback, a finished project, a kind reply. On hard days, that list is proof you are moving.
Do this
- After a rejection, it is fine to reply once, politely, asking if they have any feedback. Some will share something genuinely useful.
- Keep a wins note: every callback, every interview, every kind reply. Read it on the hard days, progress is real even before the offer.
Do not do this
The things that backfire
Some shortcuts feel tempting when you are desperate, and they actively hurt you. Avoiding these matters as much as doing the right things.
Lying about experience or faking job history
It unravels in interviews or on the job and destroys trust. Real projects are enough.
Claiming you know a tool you have never used
One follow-up question exposes it. Honesty plus a plan to learn beats a bluff.
Letting an AI write things you cannot explain
Use AI to sharpen your own words, never to invent a person you are not. If you cannot explain a line, remove it.
Mass-sending the identical application everywhere
Generic applications get filtered out. Tailored beats high-volume-but-faceless.
Only applying to a few dream companies
You need a wide net of realistic targets where juniors actually get hired, not just the famous names.
Waiting until you 'feel ready' to apply
You will never feel fully ready. Build proof, then apply in parallel with learning.
Paying a site that 'guarantees' a job
Legitimate employers never charge you to apply. Treat it as a scam and walk away.
What the hiring process actually looks like
1. Recruiter screen
A short call, mostly logistics and motivation (why this role, your background). Not deeply technical.
2. Technical screen or take-home
A coding or technical task, sometimes live, sometimes a small project to do at home.
3. Behavioral / team interview
The questions juniors actually get: walk me through your project, a time you got stuck, why this role.
4. Offer
If it is a fit on both sides. Compensation is discussed here, not in the first conversations.
Words you will see, in plain English
- Proof of work
- Something you built that a stranger can look at as evidence you can do the job: a public GitHub repo or a live website.
- GitHub
- A free website where you store your code publicly so anyone (including an interviewer) can see it. Your repos are your portfolio.
- README
- The front-page document of a GitHub project that explains what it does and how to run it. It is what hiring managers actually read.
- GitHub Pages
- Free hosting from GitHub for a simple website straight out of a repo. Good for a portfolio page or a static project.
- ATS
- Applicant Tracking System: software that scans and filters resumes before a human reads them. It is why you mirror the exact words from the job post.
- Referral
- When an employee submits you through their company's internal system, putting your resume in front of a human instead of a filter.
- Graduate scheme / apprenticeship
- Programs built specifically to hire and train people with no experience. Often your best-odds target.
- CTC / base / equity
- CTC is total cost to company (the headline number). Base is your fixed salary. Equity is company shares, common at startups and worth far less than the headline until the company succeeds.
The honest summary
The whole guide in one view. Every step here is something you can start this week.
Your progress: 0 of 8
Tick steps as you go. Your progress is saved on this device.
It is hard and getting your first job takes time, but none of this is out of reach. Pick the first step and start today.
Keep learning
Not sure what to learn first? Follow a roadmap
Skills are what turn all of this into offers. Our roadmaps lay out, step by step, what to learn for a cloud or DevOps career, all free to follow. Use them to guide your projects and fill the gaps the job posts reveal. If at some point you want the guided lessons, labs, and interview prep, you can enroll, but that is entirely your choice. Start with the free roadmap.