How to Get a Tech Internship: Projects Beat Portals

If you want to know how to get a tech internship, start with a fact about the people who hire for them. Engineering managers are builders, and builders trust evidence over paperwork. That makes tech one of the friendliest sectors for going around the portal, because one real project plus one direct message can outweigh a CV that would die in any screening filter.

Why tech internships reward outreach more than any other sector

Three things make tech unusual.

Managers hire for projects, and projects travel well. A hiring manager in most industries has to guess whether you can do the job. In tech you can show them. A link to something you built answers the question a portal application never asks. That link works exactly as well in a cold email as it would in a final interview, so you can put your strongest card on the table in the first thirty seconds of contact.

Portfolios beat CVs. Screening software reads keywords, and keywords say nothing about whether your code works. An engineering manager who clicks your GitHub or your deployed demo learns more in ninety seconds than the filter learns from your whole application. Outreach lets you route around the reader that judges you worst and reach the reader that judges you best.

Referrals fill a lot of seats. Ask anyone in the industry how they got a role and referrals come up constantly. Many companies pay employees for successful referrals, so an engineer who likes your message has an actual incentive to walk you in. Every alumni engineer you write to is a potential referral, and referred candidates get read by humans.

None of this means portals are useless in tech. It means the ratio of outcome per hour tilts harder toward direct contact here than almost anywhere else. The general method is in our full playbook on how to get an internship; this post is the tech specific version.

What counts as proof with no experience

The phrase "software engineering internship no experience" gets searched constantly, and the anxiety behind it rests on a wrong definition of experience. Nobody expects an intern candidate to have shipped production code at a company. What a manager wants is evidence you build things and finish them. All of the following count:

Course projects. The data structures assignment you extended beyond the spec, the group project where you built the backend, the statistics model from a seminar. Real, and better than nothing, though everyone in your cohort has them too.

A deployed anything. A tiny web app, a bot, a script with a public URL, an app store listing. Deployed matters because it proves you pushed through the unglamorous last 20 percent: hosting, bugs, edge cases. Managers weight finished heavily because unfinished is the default state of side projects.

Open source contributions. Even small ones. A documentation fix or a closed issue on a real project shows you can read someone else's codebase and follow contribution rules, which is most of what an intern does in week one.

Hackathons. A weekend build with a repo and a two line story about what broke at 3am. It signals speed, teamwork, and tolerance for chaos.

Whatever you pick, learn to compress it into one sentence with a decision in it: "I built a WhatsApp bot that scrapes my university's housing board and pushes new listings, and moved it from polling to webhooks when the scraper kept getting rate limited." That sentence does more work than a paragraph of adjectives, because it sounds like how engineers actually talk. Your CV should make the same move; the structure is in how to write an internship CV with no experience.

If you have none of the above, build the deployed anything first. Two focused weekends is enough for something small and real, and it upgrades every message you send afterward.

How to get a tech internship: who to write to

Three kinds of people, each caring about different things.

Engineering managers and team leads

The highest value target. They own the decision, they feel understaffing personally, and at many companies they can create an internship that was never posted. They care about one question: can this person contribute without consuming more mentoring than they give back? Your project link is the answer. Find them on LinkedIn by searching the company plus "engineering manager", "tech lead", or the team name from the product's careers or blog pages.

Early careers recruiters

They run the official pipeline. A direct message will rarely skip the process at a big company, but it can get your application flagged, tell you when the real window opens, and put a name on your file. They care about fit with the program: graduation date, location, work authorization. Keep messages to them short and factual.

Alumni engineers

Engineers from your university are the easiest people to get a reply from and the most likely to refer you. They care about whether you seem genuinely interested and minimally competent, because their name gets attached to yours. Lead with the shared university, ask one specific question, and let the referral emerge instead of demanding it.

A template engineering managers answer

The message that works references their product specifically. Engineers can smell a mass email from the subject line, and one concrete observation about what they built is the cheapest credible signal that you are writing to them on purpose.

Template: to an engineering manager, referencing their product

Hi Jonas, I'm Elena, a third year student in Madrid. I've been using your app's route planner for months and noticed the offline mode got much faster this spring, so someone on your team did something clever with caching. I build small things myself: most recently a housing alerts bot for my university (repo linked below) that I moved from polling to webhooks. I'm looking for a summer internship and would love to work on a real product team. If you take interns, could I send my CV? And if not, I'd still value fifteen minutes of your advice.

Under 120 words, one product observation, one project with a decision in it, one clear ask with a soft fallback. Adjust every specific to the truth. More variants for recruiters and alumni live in our cold email templates for internships.

The 20 minute GitHub and LinkedIn cleanup

Every message you send generates a profile check, so spend twenty minutes making the check land well.

GitHub, ten minutes. Pin your two or three best repositories and hide the fork clutter. Give each pinned repo a README with three parts: what it does in one sentence, a screenshot or link if it runs anywhere, and how to run it. Nobody will read your code deeply. They will read your READMEs completely.

LinkedIn, ten minutes. Headline that says what you are looking for ("CS student in Madrid, seeking summer 2027 software internship") instead of a blank default. A normal photo. Your projects listed with the same one sentence descriptions, with links. That is the whole job; polish past this point returns nothing.

A realistic target list for tech in Europe

Build a list of 25 to 40 companies across three tiers, because each tier treats outreach differently.

Big tech offices. The major firms run engineering hubs in cities like Dublin, London, Amsterdam, Zurich, Munich, and Warsaw. Structured programs, real deadlines, huge application volume. Apply through the portal early in the window, and use outreach to recruiters and alumni for flagging and referrals rather than to skip the process.

Scaleups. Fast growing product companies that raised serious funding and hire constantly. This is the sweet spot: real engineering standards, but small enough that a manager can say yes to an intern without a committee. Outreach frequently works here even with no posting live.

Local product companies and agencies. Every mid size European city has software companies nobody outside the region has heard of, and their internship postings collect a fraction of the applications the famous names do. A good message with a project link stands out immediately, and a term shipping real features there beats an unpaid coffee run internship at a brand name.

One more European specific note: timing varies by tier. Big tech programs open applications months ahead, often the autumn before a summer start, while scaleups and local companies decide on much shorter horizons, sometimes weeks before the internship begins. That means the smaller tiers stay in play long after the famous deadlines have passed, and a spring outreach push can still land a summer seat.

Weight your list toward the second and third tiers if you have no experience yet, then work it: find the right person, verify the address, personalize, send, follow up once after about three days. That loop, run by hand, is a few hours a week. Running it automatically, from finding people through the follow-up, is exactly how Oportunly works.

FAQ

Do I need a computer science degree to get a tech internship?

For many roles, no. Managers care about whether you can build and learn, and a business or physics student with two real projects often beats a CS student with none. Some big company programs do filter by degree, which is one more reason to write to humans instead.

Is my project too small to mention?

If it runs and you can explain a decision you made while building it, mention it. A tiny deployed tool you actually made beats a grand idea you didn't. Managers read projects as evidence of follow-through.

Should I write to engineers at companies with no internship posting?

Yes, especially at scaleups and local product companies. Many teams take an intern when a motivated candidate shows up even though nobody got around to posting a role. The message costs five minutes and the worst case is silence.

Building the project is your job. Finding the right engineering managers, verifying their addresses, drafting the personal message from your CV, sending from your own Gmail or Outlook and LinkedIn, and following up three days later can be Oportunly's job, with every reply landing in your own inbox. Waitlist members get 20% off when we open, no card needed, so join the waitlist and spend the saved hours shipping the thing you'll link to.