How to Find Your First Job in IT Without Experience
Practice4 minInnovialabs editorial team
In short
Search through job boards, Telegram channels and referrals at the same time, send tailored applications steadily on a weekly plan, and stand out with finished projects and a quick cover note.
The short answer
Landing a first IT job is not one lucky application — it is a system: a clear target role, ready materials (resume, GitHub, portfolio), several search channels and regular applications with a look at the results. Without experience you compete not on years but on evidence: projects, attention to detail and how fast you learn.
Step 1. Define your target role
Applying to everything works worse than searching for a specific role. Pick one or two, for example:
- Junior Frontend Developer;
- Junior QA Engineer;
- Backend developer intern;
- Junior Data Analyst.
Prepare your resume, profile and projects for that role. If you search in two directions, make two separate resumes.
Step 2. Prepare the basics before applying
Before you start, have these ready:
- a one-page resume with projects near the top;
- GitHub with pinned projects and READMEs;
- 2–4 finished projects matching the target role;
- LinkedIn with a clear headline;
- a cover note template you adapt for each vacancy.
Step 3. Where to look
Use several channels at once — each has its own vacancies.
| Channel | What to know |
|---|---|
| Job boards (hh.uz, LinkedIn Jobs and others) | The most vacancies, but also the most competition. Set up filters and alerts |
| Telegram channels with IT vacancies | Popular in Uzbekistan and the CIS. Roles close quickly — respond the day they are posted |
| Company career pages | Some vacancies are only published there |
| Referrals | Often the most effective channel: your resume reaches the hiring manager directly |
| Internships and junior programs | Designed specifically for people without experience |
| Meetups, hackathons, tech communities | Connections that later turn into referrals |
How to get a referral
Referrals are not only for people with connections. You can build them:
- tell friends and classmates that you are looking for work, and what kind;
- go to meetups and ask speakers questions;
- join hackathons — a way to show how you work;
- message developers at companies you like: briefly, politely, asking about the team rather than "please get me hired".
An example short message:
Hi! I'm a junior frontend developer and I'm interested in your company. I saw the internship opening — could you share what the team looks for in candidates? My GitHub: link.
Step 4. How many applications to send
There is no exact number — a lot depends on the market and the role. Consistency and quality matter more:
- set a weekly goal you can sustain, for example 5–10 tailored applications a week;
- tailor every application: headline, skill order, a couple of sentences in the cover note;
- keep a tracker: company, date, channel, status, next step;
- review your funnel every two weeks.
| What happens | Likely cause | What to do |
|---|---|---|
| No replies at all | Resume or choice of vacancies | Rewrite the resume, check fit with requirements |
| Calls, but rejections after the first chat | Self-presentation | Rehearse talking about yourself and your projects |
| Failing technical interviews | Gaps in fundamentals | Revisit the basics, practice typical tasks |
Step 5. How to stand out
- Apply fast: your chances are better in the first hours or day after posting.
- Write a cover note: 3–5 sentences on why this company and which of your projects fits.
- Do take-home tasks carefully: a README, clean code, a setup that runs.
- Show interest in the product: try the company's site or app and mention it.
- After an interview, send a short thank-you message.
Common mistakes
- Waiting to feel "fully ready" and not applying for months.
- Sending the same resume to hundreds of vacancies without tailoring.
- Applying only to roles that require nothing — there are few and competition is huge.
- Not asking for feedback after a rejection.