How internship hiring works

Behind the "apply now" button

You've practiced live coding and built a small bank of STAR stories for behavioral rounds. Both get tested once you're already talking to someone: a recruiter on a call, an engineer sharing a coding screen. Before either conversation happens, though, your application has to get through a process that has nothing to do with how well you code or tell a story. It has to be read, noticed and pulled out of a list that might hold three hundred other applications.

This course covers what happens before, around and after the interviews you already know how to handle:

• the CV that gets your name pulled from that list;
• the GitHub and LinkedIn profiles someone checks before calling you;
• where to look for internship openings;
• the Brazilian rules that decide what kind of contract you're signing;
• how to follow up without becoming the candidate nobody wants to email back.

The stages between "apply" and "offer"

A typical internship pipeline has more steps than most beginners expect. Knowing its shape in advance means the next step never surprises you. It usually looks something like this:

Application submitted
        |
Automated / recruiter screen  <- most candidates are filtered out here
        |
Recruiter or HR call (15-30 min)
        |
Technical stage: live coding, take-home, or both
        |
Hiring-manager or team interview (often behavioral, sometimes mixed)
        |
Offer (or rejection, at any stage above)

Not every company runs every stage, and a small startup might fold three of them into one call. The shape holds often enough to be worth learning, though, because each stage is won or lost with different material. The automated or recruiter screen rarely involves anyone reading your whole CV. It's a filter, and lesson 2 is about getting through it. The technical and behavioral stages are what the last two courses prepared you for. This course fills in the rest: what gets you past the filter, and what happens once you've cleared every round and hold an offer.

Why the first filter is rarely a person

A popular internship posting can draw hundreds of applications in its first day or two. No recruiter reads them all by hand. Many companies run applications through an applicant tracking system (ATS). It parses your CV as text and lets recruiters search and filter it against the posting's requirements, so a CV that matches rises to a human and one that doesn't sinks quietly down the list.

That cuts both ways for you. A plain, well-structured CV that uses the posting's own words travels further than a polished one a parser can't read cleanly. And because the filter looks for skills, real project work can carry weight even without a list of job titles you don't have yet.

That matters more for an internship than for almost any other hiring. A mid-level posting filters for years of production experience. An intern posting filters for potential and evidence that you can learn and ship: a repository with real commits, a project you can explain, coursework you saw through to the end. You aren't competing on a track record you don't have. You're competing on how clearly you show the one you're building now.

One habit worth building early is reading a posting's wording carefully. Companies use "entry-level" and "intern" loosely, sometimes interchangeably. An "entry-level" posting may expect a finished degree, which rules out an estágio, since an estágio requires you to be enrolled as a student. An "intern" posting almost always means the estágio structure that lesson 5 covers. When the label is unclear, a short message to the recruiter saves you from applying with the wrong idea about hours, pay or contract type.

Why intern hiring is judged differently

It helps to know what a company is solving for when it opens an intern position, because it changes how you read every step. An experienced hire is expected to be productive almost at once, so the screen weighs past production work. An intern is a different bet. The company pays in supervision time, in a bolsa-auxílio and in onboarding effort for someone who needs real ramp-up time. In return it meets promising people before other companies do, often at a lower cost than someone with two years of experience.

So for an intern, the CV, the GitHub profile and the interview all answer the same questions:

• Can this person learn fast?
• Do they finish what they start?
• Do they say so clearly when they're stuck?
• Are they curious, or reciting buzzwords copied from the posting?

Every lesson in this course helps you give clear, honest, specific answers to those questions in whatever format the pipeline asks for: a CV, a profile page, a follow-up message or a signed offer.

What's ahead in this course

• Lesson 2: writing a CV that gets through an ATS and still reads well once a person opens it.
• Lesson 3: GitHub and LinkedIn, the two places a recruiter almost always looks around that first screen, and how to make both worth the look.
• Lesson 4: where to search for internship openings, in Brazil and remote, without treating any one channel as a shortcut.
• Lesson 5: the lesson you can't skip if you're studying in Brazil. What an estágio legally is and isn't, how it differs from CLT and PJ, and how remote international internships are usually contracted.
• Lesson 6: following up without pestering anyone, and getting something useful out of a rejection.
• Lesson 7: all of it as one repeatable process, and a pointer to what comes after the offer.

None of this needs charm or connections you don't have. It needs knowing which document a filter reads first, which profile a person checks next, and which few sentences turn silence into an answer. The next six lessons cover each in turn.