Module 6: Your Professional Materials in English
5. LinkedIn and Your Professional Profile
Description
There's a mistaken idea that ruins a lot of LinkedIn profiles: thinking it's a social network where you post things and wait for people to find you. It isn't, or not for what matters to you. For a recruiter, LinkedIn is a searchable database. Someone types terms into a search bar — React developer remote LATAM, for example — and on the other end a ranked list of profiles shows up. Your job isn't to "have a presence"; it's to show up in that list when they search for you, and when someone opens your profile, for them to understand in ten seconds who you are and what role you fit. These are two different skills: being findable, and being convincing. This lesson handles both.
And here it's worth defusing the most common fear right away, the one you're probably carrying: "my English isn't good enough to write a professional profile." Good news. A LinkedIn profile that works isn't made of elegant paragraphs or flawless English. It's made of a headline with the real name of your role, a five-sentence "About" that's clear, an experience section consistent with your résumé, and a handful of short, well-written messages. You can do all of that with the technical English you've already been building in this guide. In fact, on LinkedIn, overwrought English works against you: the search engine rewards concrete words and the human reader rewards direct sentences. Simple wins, again.
Connection to the module: In the previous lesson you learned to tailor your résumé to each job posting — the correspondence map, the keywords, the precision strategy. LinkedIn is the same material for a different channel: you send the résumé to a specific posting; your LinkedIn profile is always on, waiting for someone who doesn't even know you exist to find you. That's why coherence between the two isn't a cosmetic detail, it's a trust signal: when a recruiter compares your résumé against your profile and the dates or the titles don't match, that raises a red flag. The next lesson closes out the construction of your evidence with GitHub and your portfolio — the triangle's third vertex. Here we handle the vertex most people neglect and that, done well, makes opportunities come to you instead of you chasing every single one of them.
LinkedIn is a search engine, and you're a search result
Before touching a single section of the profile, understand the mechanics, because it changes your decisions. Recruiters don't browse profiles at random. They use LinkedIn Recruiter — the paid version built for recruiting — where they type search criteria and get a list of candidates. For all practical purposes, it's a search engine, and you are one of the indexed pages. The analogy is exact: if a webpage doesn't contain the words someone searches for on Google, it doesn't show up in the results. Your profile works the same way.
What does a recruiter type into that search? It almost always combines four things:
| Search criterion | Example (in English, as a recruiter types it) | Which field of your profile it comes from |
|---|---|---|
| The role / title | Backend Developer, QA Engineer | Your headline and current role |
| The technology or skill | Python, Django, AWS | Your headline, your experience, your skills |
| The location | Colombia, Remote, Latin America | Your location field |
| The level | Junior, Semi Senior, Mid-level | Your headline and your experience |
Notice where those matches come from: your headline, your job titles, your location, and your skills list. Those are the fields the search engine actually weighs. A beautifully written "About" doesn't make you show up if your headline says "Passionate learner" instead of "Backend Developer"; the search engine doesn't guess, it matches text. Hence the lesson's first operating rule: the words a recruiter would type to search for you have to be there, literally, in the fields the search engine indexes — not in a hidden paragraph, but in your headline, your job titles, and your skills.
This isn't "gaming keywords." It's the same thing you did in the previous lesson with the job posting: using the market's real vocabulary wherever it's true of you. If you're a React developer, the word React has to be visible and up top. If it isn't, for the search engine you don't exist as one, even if you've been writing components for two years.
The headline: the most important field on your entire profile
The headline is the line that appears right below your name. It shows up in search results, in your comments, when someone hovers over your name — it's everywhere. And it's, by far, the field with the most weight per character on all of LinkedIn, because it does two jobs at once: it makes you findable (the search engine indexes it heavily) and it makes you readable (it's the first thing a human reads).
The most common mistake, the one that people with impostor syndrome make on reflex, is filling it with humility or poetry. Compare:
| ❌ Weak | ✅ Strong |
|---|---|
Aspiring developer | Always learning | Backend Developer | Python, Django, PostgreSQL |
Passionate about technology and code | Frontend Developer | React, TypeScript | Open to remote |
Bootcamp graduate looking for opportunities | QA Engineer | Automation with Playwright & Python |
Computer Science student | Dreamer | Junior Data Engineer | Python, SQL, Airflow |
Read the left column with a search engine's eyes. Aspiring isn't a role anyone searches for. Passionate isn't a technology. Looking for opportunities doesn't help people find you; the recruiter already assumes you're open if they found you. Those words take up your profile's most valuable space without bringing a single searchable term. The right column states the real name of the role and the technologies — exactly what someone types to search for you.
The formula that works is simple and fits in the ~220 characters LinkedIn gives you:
[Real role] | [2-4 key technologies] | [optional signal: seniority or availability]
Three notes on this formula's English:
- The role goes in its standard industry name:
Backend Developer,Software Engineer,Data Analyst,DevOps Engineer— the same titles you saw in module 1's job postings. Don't invent a title ("Code Ninja," "Tech Enthusiast"): nobody searches for that. - Avoid
aspiringandwannabe. In English they sound like "not there yet." If you did the work — even in your own or bootcamp projects — you're aJunior Backend Developer. The wordJunioris honest and searchable;aspiringonly subtracts. - The
|separator (vertical bar) is the convention;·(middle dot) is also used. Avoid filling the headline with emojis: they subtract seriousness and add nothing for the search engine.
What to expect: when you rewrite your headline this way, the first version is going to sound "too direct," almost presumptuous, if you're coming from a habit of downplaying yourself. That discomfort is the sign you're doing it right. You're not lying — Junior Backend Developer is a verifiable fact — you're just no longer hiding it.
The "About": five sentences in first person
The About section is your summary: a free-text block where you introduce yourself. A lot of people leave it blank, and it's a waste, because it's the first long piece of text read by someone who already decided to open your profile — someone interested. But it doesn't need to be an essay either: five to seven clear sentences are enough.
Two English decisions before the structure. First: it's written in first person ("I build...", "I'm a..."), not third ("Juan is a..."). Third person sounds stiff and distant; first person is the tech norm and easier for you to write. Second: it's written in English if you're targeting English-speaking markets. An About in Spanish on a profile searching for remote international postings tells the English-speaking recruiter "this person might not be comfortable working in English," and gives them a reason to move to the next one. If your market is mixed, English is the safe bet.
A structure you can fill in today, with the English mold and its nuance alongside:
| Sentence | English mold | What goes there |
|---|---|---|
| 1. Who you are now | I'm a [role] focused on [area]. | Your role and your focus, in present tense |
| 2. What you do / with what | I build [what] with [technologies]. | What you build and your stack |
| 3. Brief evidence | Recently, I built [project] that [result]. | A concrete project and its effect |
| 4. Where you're headed | I'm looking for [type of role] where I can [what]. | The role you're looking for |
| 5. How to reach you | Feel free to reach out at [email] or here on LinkedIn. | A clear contact method |
A complete example, for someone coming out of a bootcamp:
I'm a Junior Backend Developer focused on building APIs. I work mainly with Python, FastAPI, and PostgreSQL. Recently, I built a URL shortener with click analytics that handles authentication and caching — the code and README are on my GitHub. I'm looking for a backend or full-stack role, remote or hybrid, where I can grow with a team that reviews code seriously. Feel free to reach out here or at juan@email.com.
Read it and notice what it doesn't have: hard English. There's not a single word you haven't seen in this guide. It doesn't apologize for being junior, it doesn't say "although I still have a lot to learn," it doesn't beg. It says what you do, shows proof, says what you're looking for, and how to reach you. That's the standard, and it's within your reach this week.
An antipattern worth naming: the pure-adjective About. "I'm a passionate, hardworking, detail-oriented developer with a strong desire to learn and grow in a dynamic environment." That sentence says nothing — anyone could sign it, including someone who can't code. Passionate, hardworking, detail-oriented are empty words a technical reader already skips over. Swap them for a fact: instead of detail-oriented, a project where detail actually mattered. Evidence always beats an adjective.
Experience: consistent with your résumé, not identical
The Experience section is the one most compared against your résumé, for a practical reason: a recruiter usually has both open at the same time. Here the rule is strict: the roles, companies, and dates on your LinkedIn have to match your résumé. Not "resemble" — match.
Distinguish "consistent" from "identical," because they're not the same:
- Identical in what's verifiable: the job title, the company or project name, and above all the dates (start and end month and year). If your résumé says you were a
Backend Developerfrom January to December 2025 and your LinkedIn saysSoftware Engineerfrom March 2025 to today, you've created a contradiction. The recruiter doesn't think "must be a typo"; they think "which one is true?", and that doubt costs you the interview. Hard data gets copied, not reinterpreted. - Consistent, not cloned, in how you word your achievements. Your résumé carries the sharpened bullets from this module's lesson 3. On LinkedIn you can use the same achievements in a slightly more human tone and with more room, since there's no one-page limit. What can't happen is LinkedIn claiming an achievement your résumé doesn't mention and that you can't defend: everything on either one has to be something you can hold up out loud, in English, for five minutes. That's the module's golden rule.
A detail about personal and bootcamp projects, which is probably your case: LinkedIn has a Projects section separate from Experience, and lets you list a bootcamp under Education. Use them. Don't inflate a course project by disguising it as a job — that collapses at the first technical question — but don't hide it either. A real project, well described, in its correct section, is legitimate evidence. The next lesson goes deep into how to present those projects; here it's enough that they go in their right place and match your résumé.
Skills, photo, and the signals that add up or subtract
Beyond the big blocks, LinkedIn has small signals that, added together, form the impression of "this person takes this seriously" or "this profile is half-finished." They don't weigh the same, but they're cheap to fix:
| Signal | Adds when... | Subtracts when... |
|---|---|---|
| Skills | You list your stack's real technologies; the search engine indexes them | They're empty or full of generic skills (Microsoft Word, Teamwork) |
| Profile photo | It's an actual photo of you, facing forward, decent lighting, visible face | There's no photo, or it's a logo, an avatar, or a party photo |
| Cover photo (banner) | It's sober or tech-related (or simply neutral) | It's the default generic blue image (signals an abandoned profile) |
| Profile language | It's in English if you target English-speaking markets | Everything's in Spanish while targeting international postings |
| Recommendations | You have 1-2 from real colleagues or mentors, in English | Zero, or obvious "I'll recommend you if you recommend me" trades |
| Activity | You comment or share something technical once in a while | Totally inactive profile (not fatal, but adds little) |
| Custom URL | linkedin.com/in/yourname (edited in settings) | The long URL with random numbers (looks careless on a résumé) |
Two honest clarifications so you don't overweight this table. Your photo matters more than a lot of us would like to admit: you don't need a professional photoshoot, just a photo of yourself, facing forward, with window light and a neutral background, taken with your phone. A profile with no photo gets much less of a response, and fixing it takes ten minutes. On the other hand, activity (posting, commenting) is the signal that weighs least toward getting hired: don't fall into the guilt of "I should be posting every day." A silent but complete, findable, coherent profile performs much better than one that posts daily with an empty headline.
On Skills: think of them as tags for the search engine. Add the concrete technologies you want people to find you for (Python, React, Docker, PostgreSQL) and move the three or four most important ones to the top, because LinkedIn highlights the first ones. Leave out the generic ones.
Availability and location for remote markets
If you're targeting international remote work, two adjustments deserve attention because they often get done wrong.
Location. The location field is one of the filters recruiters use most. Put your real location (city and country): lying here creates problems once the conversation about time zones, legal hiring zone, or work authorization comes up, and those conversations do come up. What's worth doing is making your remote availability crystal clear in the fields you do control: the headline (| Open to remote) and the About. A recruiter searching Remote LATAM values seeing your country show up and your profile shouting "I work remote with no problem." Don't hide your location; frame it as a time-zone advantage when it is one — several LATAM countries share a time zone band with the US, and that's an argument in your favor.
"Open to Work." LinkedIn has a feature to signal you're job-hunting, and it comes in two flavors worth distinguishing:
| Mode | What it does | When it's worth it |
|---|---|---|
| Recruiters only | Shows your availability only to recruiters using LinkedIn Recruiter; nobody else sees it | Almost always; discreet and no image cost |
The public green frame (#OpenToWork) | Puts a green banner visible to everyone on your photo | When you prioritize visibility volume over perception |
The "recruiters only" mode is the safe default: you show up in recruiters' searches, without the cost of the green frame. The public green frame is more debatable — some recruiters don't mind it, others read a certain urgency signal into it — so don't obsess over it: if you want maximum visibility, use it without guilt; if you prefer discretion, the recruiters-only mode fulfills the same searchable function. What is a fact: turning on either one makes you more findable than turning on neither. The worst state is invisible.
Contact messages that don't get ignored
Having a good profile is half the job. The other half is writing to people — recruiters, engineers on a team you're interested in, someone who posted an opening — without your message dying ignored. And here the English you need is again small and simple; what decides is the message's structure, not flowery language.
Before the templates, understand why a message gets ignored. It gets ignored when it's long, when it's generic (it's obvious you sent it to fifty people), when it asks for too much upfront ("can you get me a job?"), or when it forces the other person to decode what you want. It gets a reply when it's short, shows that you know who you're writing to, and has a single clear, easy-to-grant request.
The anatomy of a message that works has four pieces in order: a greeting with the name, a specific reason you're writing to that person, your concrete request, and a short close. Here are three templates for the most common situations. Fill in the brackets.
Connection request to a recruiter (short note, fits LinkedIn's character limit):
Hi [name], I saw you're hiring for a [role] at [company]. I'm a [your role] working with [tech], and it looks like a strong fit. I'd love to connect and share my profile. Thanks!
(Hola [nombre], vi que están contratando para [rol] en [empresa]. Soy [tu rol] y trabajo con [tecnología], y parece encajar bien. Me encantaría conectar y compartir mi perfil. ¡Gracias!)
Writing to an engineer on a team you're interested in (you're not asking for a job, you're asking for context):
Hi [name], I'm exploring [role] positions and [company]'s work on [something specific] caught my attention. Would you be open to a quick question about what the team looks for in candidates? No worries if you're busy — thanks either way.
(Hola [nombre], estoy explorando posiciones de [rol] y el trabajo de [empresa] en [algo específico] me llamó la atención. ¿Estarías abierto a una pregunta rápida sobre qué busca el equipo en los candidatos? Sin problema si estás ocupado; gracias de todos modos.)
Replying to a recruiter who reached out to you:
Hi [name], thanks for reaching out — this sounds interesting. Yes, I'm open to hearing more. I'm a [role] with experience in [tech], currently based in [country] and available for remote work. When would be a good time to talk?
(Hola [nombre], gracias por escribir; suena interesante. Sí, estoy abierto a saber más. Soy [rol] con experiencia en [tecnología], vivo en [país] y estoy disponible para trabajo remoto. ¿Cuándo sería buen momento para hablar?)
Notice the patterns that repeat and that you can reuse in any message:
| Function | Model phrase in English | Nuance in Spanish |
|---|---|---|
| Opening with the reason | I saw you're hiring for... / ...caught my attention. | Vi que están contratando... / me llamó la atención |
| Introducing yourself in one line | I'm a [role] working with [tech]. | Soy [rol] y trabajo con [tecnología] |
| Lowering the pressure of the request | Would you be open to...? / No worries if you're busy. | ¿Estarías abierto a...? / Sin problema si estás ocupado |
| Confirming availability | I'm available for remote work. | Estoy disponible para trabajo remoto |
| Closing without demanding | Thanks either way. / When would be a good time? | Gracias de todos modos / ¿Cuándo sería buen momento? |
A couple of rules worth more than any template. One: a single request per message. If you ask to connect, review your résumé, tell you about the team, and pass along a referral, all at once, you're not going to get anything. Two: Would you be open to...? is one of the most useful formulas in professional English, because it gives the other person a comfortable out, and paradoxically that makes a yes more likely. Three: No worries if you're busy isn't weakness; in English-speaking professional culture it's standard courtesy that reduces pressure and raises the response rate.
What to expect: most of these messages aren't going to get a reply, and that's normal, not a judgment on you or your English. Cold response rates are low for everyone. The goal isn't for everyone to reply; it's for the ones who do reply to do so because your message was clear. Send ten good short messages before one long, perfect one.
The triangle: résumé, LinkedIn, and portfolio tell the same story
Let's close with the idea holding up this whole module. Your three materials — résumé, LinkedIn, and portfolio — aren't independent documents. They're three views of the same person, and whoever's evaluating you cross-checks them. When all three tell the same story, they reinforce each other and your credibility rises. When they contradict each other, each contradiction is a red flag, and red flags don't add up, they multiply, because each one plants the doubt of "what else doesn't match?"
Think of it as an evaluator with three tabs open. Here are the inconsistencies they jump to look for:
| Coherence point | The red flag it triggers |
|---|---|
| Role and title | The résumé says Backend Developer, LinkedIn says Full-Stack Engineer for the same period |
| Job dates | A 2024-2025 job on the résumé shows up as 2023-2024 on LinkedIn |
| Target role | The résumé targets QA, the LinkedIn headline says frontend, the portfolio is data projects |
| Technologies | The résumé claims Kubernetes; it doesn't appear in any portfolio project or on LinkedIn |
| The name / the identity | The résumé's flagship project isn't linked or mentioned on LinkedIn |
None of those contradictions necessarily means you lied. Most are oversights: you updated the résumé and forgot LinkedIn. But the evaluator doesn't see your intent, they see the inconsistency, and their incentive is to discard when in doubt, because they have a hundred other profiles. Coherence, then, isn't perfectionism: it's removing every excuse the decision-maker has to discard you.
The good news is that coherence is pure mechanical work, not talent or advanced English: a checklist you run in twenty minutes.
- Is the target role the same in your LinkedIn headline, your résumé title, and what your portfolio shows? All three point at the role from your module 1 target role brief.
- Do the job titles and dates match exactly between résumé and LinkedIn?
- Do the technologies you claim on one side have real backing on the others? No phantom stack.
- Is your main project linked from both LinkedIn and the résumé, and does its README confirm it?
- Is the language consistent with your market — English where you're targeting English?
Run that list every time you change something on any of the three. If you touch your résumé, check that LinkedIn still matches. It's the cheapest, highest-return maintenance in your entire job search.
Exercises
Exercise 1 — Rewrite the weak headline.
Your current headline says: "Recent bootcamp graduate | Passionate about coding and always learning something new." You work with Python, Flask, and MySQL, you're looking for your first job as a junior backend developer, and you're open to remote work. Rewrite it with the lesson's formula ([Real role] | [2-4 technologies] | [optional signal]).
See solution
Something like: Junior Backend Developer | Python, Flask, MySQL | Open to remote
Why this works: the real role (Junior Backend Developer) replaces Recent bootcamp graduate — the search engine can match against that title, not against "recent grad." The three technologies stay visible and searchable where Passionate about coding used to be, which isn't a term anyone types. Open to remote adds one more filter without spending extra space. None of this is harder to write than the original; it's shorter and more specific.
Exercise 2 — Write your About in five sentences.
You're a QA Engineer, trained in test automation with Playwright and Python. You recently built a 40-test automated suite for a to-do app that cut manual regression time from two hours to fifteen minutes. You're looking for a QA or automation role, remote or hybrid, and your email is ana@email.com. Use the lesson's five-sentence template to write the full About in English.
See solution
I'm a QA Engineer focused on test automation. I work mainly with Playwright and Python. Recently, I built a test suite of 40 automated tests for a to-do app that cut manual regression time from two hours to fifteen minutes. I'm looking for a QA or automation role, remote or hybrid, where testing is treated as a real engineering discipline. Feel free to reach out here or at ana@email.com.
Why this works: each sentence fulfills exactly one function from the table — who you are, what you work with, your evidence with a concrete number, what you're looking for, how to reach you — and none of them uses empty adjectives like passionate or detail-oriented. The "two hours to fifteen minutes" data point is the proof that replaces any generic claim about being good at your job.
Exercise 3 — Find the triangle's red flags.
A recruiter has your résumé and your LinkedIn open at the same time. Your résumé says: QA Engineer, TechCorp, Mar 2024–Feb 2025, automated tests with Selenium and Python. Your LinkedIn says: QA Analyst, TechCorp, Jan 2024–Present, manual and automated testing with Selenium, Cypress and Python. Identify the inconsistencies and decide, for each one, whether it's an easy oversight to fix or something you first need to verify is true.
See solution
Three red flags: (1) the job title doesn't match — QA Engineer on the résumé versus QA Analyst on LinkedIn, even if it's the same job; (2) the dates don't line up — the résumé ends in February 2025 and LinkedIn says it's ongoing (Present); (3) LinkedIn claims Cypress, a technology the résumé doesn't mention at all. The first two are mechanical oversights: fix them by copying the same title and the same exact dates on both sides, choosing whichever version is actually true. The third is different: before leaving Cypress on LinkedIn you have to be able to hold it up in a technical interview; if your contact with Cypress was minimal or nonexistent, remove it or scale it down (familiar with Cypress), the same way you did with Redis in the résumé-tailoring lesson.
Why this works: separating "hard data that gets copied" from "claim that gets verified" is the same distinction the lesson draws between being consistent and being identical — and it's what removes any excuse the evaluator has to discard you out of doubt.
Exercise 4 — Write the contact message.
You see a job posting for Backend Developer (Python/Django) at a company called Nimbus. Write a short connection-request message to the recruiter who posted it, following the lesson's four-piece anatomy: greeting with a name, specific reason, concrete request, short close.
See solution
Hi Laura, I saw you're hiring for a Backend Developer role at Nimbus. I'm a Backend Developer working with Python and Django, and it looks like a strong fit. I'd love to connect and share my profile. Thanks!
Why this works: it names the person, gives a specific, verifiable reason (the posting she published, not a generic "I saw your profile"), makes a single, easy-to-grant request (connecting), and closes in one line. It doesn't ask for a job directly or demand a long reply, which is exactly what makes this kind of message actually get answered.
Summary and next step
Let's recap the thread. LinkedIn is a search engine before it's a social network: your first job is being findable, and that's decided in the fields the search engine indexes — headline, job titles, location, and skills — with the real words a recruiter would type. The headline is your most valuable field: the role's real name plus your technologies, no aspiring, no poetry. The About is five clear sentences, in first person and in English. Your experience matches your résumé exactly on what's verifiable. For remote, real location plus clear availability and "Open to Work" turned on. Contact messages are short, specific, and carry a single easy-to-grant request. And it all closes with the coherence of the résumé-LinkedIn-portfolio triangle, where every contradiction is a red flag you can avoid with a twenty-minute checklist.
Before moving on, this quick checklist:
- Does your headline name the real role and 2-4 technologies, with no
aspiringor filler? - Does your About have five sentences in first person, in English, with one concrete project as evidence?
- Do your roles and dates in Experience match your résumé exactly?
- Is your location real, and is your remote availability clear in the headline and the About?
- Did you turn on "Open to Work" in the mode that suits you?
- Do you have at least one short message template ready with a single request?
If you've made it here dragging the feeling that your English isn't enough to "sell yourself" on LinkedIn, look at what we actually asked you to write: a one-line headline, a five-sentence About, and a few three-line messages. Not one elegant paragraph, not one complicated grammatical structure. Backend Developer | Python. I build APIs. Would you be open to a quick chat?. None of that is above the English you already handle. The hard part of LinkedIn was never the language; it was deciding to present yourself with the clarity of someone who knows what they're doing. Before moving on, you should be able to open your real LinkedIn profile and, in under an hour, rewrite your headline, your About, and run the coherence checklist against your résumé — and after this lesson, you can already do that.
In the next lesson we build the triangle's third vertex: GitHub and the portfolio as evidence. There we stop talking about how you describe yourself and move to what an evaluator can clone, run, and verify with their own hands — where your projects stop being a line on a profile and become the proof that you can do what you say.
Resources
- Let recruiters know you're Open to Work — LinkedIn's official Help page explaining the difference between "recruiters only" mode and the public
#OpenToWorkframe. - Edit the About section on your profile — LinkedIn's official guide to editing the About section step by step, on desktop and mobile.
- Manage your public profile URL — how to customize your URL (
linkedin.com/in/yourname) and how many times you can change it. - LinkedIn Recruiter — the product page recruiters use to search for candidates; confirms why the headline and skills are the fields that weigh most in a search.
- Tips For Creating LinkedIn Headlines (With Examples) — Indeed Career Guide's guide with more strong headline examples and the logic behind each one.