-
-
Notifications
You must be signed in to change notification settings - Fork 131
Update LinkedIn guide content #1759
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Merged
Merged
Changes from 2 commits
Commits
Show all changes
7 commits
Select commit
Hold shift + click to select a range
e4f13be
Update LinkedIn guide content
ozgulsal 8002247
Merge branch 'main' of https://github.com/CodeYourFuture/curriculum i…
ozgulsal e61ef7a
Address all review comments: linkedin section updates and group activ…
ozgulsal 2028a7b
Merge branch 'main' into linkedin-edit
ozgulsal aa6640d
Merge branch 'main' into linkedin-edit
ozgulsal 6c8d623
update the content based on the comment
ozgulsal b56b5af
Merge branch 'main' into linkedin-edit
ozgulsal File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
261 changes: 237 additions & 24 deletions
261
org-cyf-guides/content/employability/linkedin-profile/index.md
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -1,32 +1,245 @@ | ||
| --- | ||
| title: Your Linkedin profile | ||
| description: | ||
| emoji: 🖼️ | ||
| weight: 4 | ||
| title: Your LinkedIn Profile | ||
| date: 2024-07-17T11:13:37 | ||
| description: Move beyond ticking boxes and use LinkedIn strategically | ||
| emoji: 🔗 | ||
| weight: 7 | ||
| --- | ||
| # Your LinkedIn Profile: From Complete to Competitive | ||
| A fully completed LinkedIn profile is 40 times more likely to receive opportunities through the platform. However, completeness alone is not enough. Your LinkedIn profile is not just an online CV — it is your public landing page. It influences how you appear in search results and how recruiters evaluate you in seconds. | ||
|
|
||
| A complete LinkedIn profile (scoring 100%) is 40 times more likely to receive opportunities through LinkedIn. This is because a completed profile ranks higher in the internal algorithm, meaning you’re more likely to be discovered. | ||
| To use this guide you should: | ||
| - Have a LinkedIn account or be in the process of creating one | ||
| - Have a target role in mind (e.g. Junior Backend Developer, QA Engineer, Data Analyst) | ||
| - Have a draft CV or a list of your skills, projects, and experience | ||
|
|
||
| Here’s what you need on your profile to get there: | ||
| After using this guide you will: | ||
| - Have a clear, searchable, and credible LinkedIn profile | ||
| - Know how to write a strong headline and About section | ||
| - Be able to describe your experience and projects using the XYZ method | ||
| - Understand how to grow your visibility and network on LinkedIn | ||
|
|
||
| - ### Profile picture | ||
| - ### Location and industry | ||
| - ### Experience (a current position, with a brief description, plus two previous positions) | ||
| - ### Skills (at least three) | ||
| - ### Education | ||
| - ### At least 50 connections | ||
| ## Start With Direction | ||
| Before editing anything, decide what role you are aiming for. Avoid listing multiple directions at once. When your profile tries to target everything, it becomes harder for recruiters to understand you. | ||
|
|
||
| LinkedIn is a key platform for finding job opportunities. Make sure yours is up to scratch before you start job hunting. Here is a list of things to check: | ||
| Review at least 10 job descriptions for your target role and look for patterns: | ||
| - Repeated job titles | ||
| - Common tools | ||
| - Frequently mentioned skills | ||
|
|
||
| ## Linkedin profile criteria | ||
| Use this language consistently across your headline, About section, and experience. LinkedIn search prioritises keyword alignment. | ||
|
|
||
| - [ ] Your profile scores 100% on Linkedin | ||
| - [ ] You have a professional profile picture | ||
| - [ ] Your bio includes the role you're looking for and your key skills | ||
| - [ ] Emphasise 3-5 key skills you want to be found for across your profile (Bio, Summary, Activity etc.) | ||
| - [ ] You have an engaging summary section | ||
| - [ ] Connect to the rest of your profile (GitHub, Email, etc.) | ||
| - [ ] Relevant experience (Including CYF) | ||
| - [ ] An accurate Education section (Including CYF) | ||
| - [ ] Share your projects and talk about them | ||
| - [ ] A banner that highlights your skills | ||
| **Exercise:** | ||
| - Find 10 job descriptions for the role you are targeting | ||
| - Highlight repeated job titles, tools, and skills across those descriptions | ||
| - Make a list of the most common keywords | ||
|
|
||
| Note: These are the words you should use throughout your LinkedIn profile. | ||
|
|
||
| ## Your Headline Is Your Positioning | ||
| Your headline is one of the most visible parts of your profile. Avoid generic phrases such as "Open to work" or "Seeking opportunities." | ||
|
|
||
| Instead, make it clear and searchable. | ||
|
|
||
| Structure idea: `Target role | Core skill | Secondary skill | Value focus` | ||
|
|
||
| Example: | ||
| > Junior Backend Developer | Node.js | APIs | Building scalable services | ||
|
|
||
| Your headline should help someone understand your direction within seconds. | ||
|
|
||
| **Exercise:** | ||
| - Write a headline using the structure above | ||
| - Check it against the keywords you identified in the previous exercise | ||
|
|
||
| Note: Does your headline clearly communicate your target role and core skills? | ||
|
|
||
| ## Write an About Section With Purpose | ||
| Your About section should answer three practical questions: | ||
| 1. What do you do? | ||
| 1. What can you help with? | ||
| 1. What are you looking for next? | ||
|
|
||
| Write in first person. Keep paragraphs short. Avoid long, dense text. If you changed careers, briefly explain why. If you completed CYF, describe what you built and what technologies you used. Keep it grounded in action. | ||
|
|
||
| End with a simple statement about what you are seeking next. It does not need to be dramatic. It needs to be clear. | ||
|
|
||
| **Example:** Junior Backend Developer, CodeYourFuture Graduate | ||
|
|
||
| > I am a junior backend developer with a background in retail operations. After several years in customer-facing roles, I decided to transition into software development and completed the CodeYourFuture full stack programme. | ||
| > | ||
| > During the programme, I built RESTful APIs using Node.js and Express, worked with PostgreSQL databases, and implemented authentication and authorisation features. For my final project, I collaborated in a team of 4 to build a task management application, where I was responsible for backend architecture and database design. | ||
| > | ||
| > I am currently looking for a junior backend developer role where I can contribute to a collaborative engineering team and continue developing my skills in Node.js based systems. | ||
|
|
||
| **Exercise:** | ||
| - Write a draft About section answering the three questions above | ||
|
|
||
| Note: Is it clear what role you are targeting? Have you mentioned specific technologies and projects? | ||
|
|
||
| ## Show Evidence, Not Responsibilities | ||
| Do not only list what you were responsible for. Show what you did and what changed as a result. | ||
|
|
||
| A helpful framework is the **XYZ method**, used by Google for writing impact statements: | ||
|
|
||
| > I accomplished **X**, as measured by **Y**, by doing **Z**. | ||
| - **X** = What you achieved | ||
| - **Y** = The measurable result | ||
| - **Z** = The action you took | ||
|
|
||
| Even without large numbers, you can still demonstrate impact. Improvements, efficiency gains, bug reductions, or successful feature delivery all count. | ||
|
|
||
| For each role or project, try to include: | ||
| - The objective or problem | ||
| - Your contribution | ||
| - Tools or technologies used | ||
| - The outcome or impact | ||
|
|
||
| If you do not yet have commercial experience, use CodeYourFuture projects, freelance work, or volunteer contributions. What matters is demonstrating applied skills. | ||
|
|
||
| **Example:** Using the XYZ method | ||
|
|
||
| > - Implemented secure user authentication for a task management application, reducing unauthorised access during testing by 100%, by building JWT-based authentication middleware in Node.js and Express. | ||
| > - Improved API response time by 25% by optimising PostgreSQL queries and adding proper indexing. | ||
| > - Delivered 12 RESTful endpoints supporting task creation, editing, and deletion by designing a structured database schema and collaborating closely with the frontend team. | ||
| > | ||
| > Tools used: Node.js, Express, PostgreSQL, JWT, Git, Postman. | ||
|
|
||
| **Exercise:** | ||
| - Pick one role or project from your experience | ||
| - Write 2–3 bullet points using the XYZ method | ||
|
|
||
| Note: Do your bullet points show what changed as a result of your work? | ||
|
|
||
| ## Optimise Your Skills Section | ||
| LinkedIn's Skills section is searchable and used directly in recruiter filters. It is not decorative — it directly affects whether you appear in search results. | ||
|
|
||
| You should: | ||
| - Add your most relevant technical and professional skills | ||
| - Reorder them so the most important ones appear at the top | ||
| - Remove skills that do not support your target role | ||
|
|
||
| For example, if you are targeting a Junior Backend Developer role, your top skills might include: | ||
| - Node.js | ||
| - Express | ||
| - PostgreSQL | ||
| - REST APIs | ||
| - Authentication and Authorisation | ||
|
|
||
| Avoid listing unrelated tools that dilute your positioning. A focused skills section makes your profile easier to understand and increases your chances of appearing in filtered recruiter searches. | ||
|
|
||
| **Exercise:** | ||
| - Review your current Skills section | ||
| - Compare it against the keyword list you created earlier | ||
| - Reorder and remove skills so your top 5 clearly reflect your target role | ||
|
|
||
| ## Education and CodeYourFuture | ||
| Include an accurate education section, including CodeYourFuture. | ||
|
|
||
| In the description, mention: | ||
| - Duration | ||
| - Focus areas | ||
| - Key technologies | ||
| - Notable projects | ||
|
|
||
| Bootcamps become stronger when you describe outcomes, not just attendance. | ||
|
|
||
| ## Add Credibility Signals | ||
| Recruiters and hiring managers are not only looking for skills. They are looking for proof and trust signals. These can significantly strengthen your profile, especially at junior level or when changing careers. | ||
|
|
||
| Consider including: | ||
| - **Recommendations** from mentors, peers, or project teammates: A short recommendation describing how you worked in a team or solved a problem adds social proof. | ||
| - **Certifications**: Relevant certifications signal structured learning and commitment. Make sure they are aligned with your target role. | ||
| - **Open source contributions**: Even small pull requests demonstrate initiative, collaboration, and real-world code exposure. | ||
| - **Volunteer experience**: Technical volunteering or community involvement shows responsibility and applied skills beyond coursework. | ||
| - **Community participation**: Hackathons, meetups, tech events, or bootcamp leadership roles all demonstrate engagement with the industry. | ||
|
|
||
| Do not underestimate these elements. When experience is limited, credibility signals show initiative, professionalism, and that you are actively building your career rather than passively waiting for opportunities. | ||
|
|
||
| ## Profile Picture and Banner | ||
| Use a clear, professional profile picture. It does not need to be formal, but it should be appropriate and well lit. | ||
|
|
||
| Your banner can reinforce your direction. It might highlight your technologies, your role focus, or a simple message aligned with your target career path. | ||
|
|
||
| ## Build a Thoughtful Network | ||
| LinkedIn becomes more powerful as your network grows. As a junior candidate, aim for at least 200 to 300 relevant connections over time. Quality still matters more than quantity, but visibility increases with a broader professional network. | ||
|
ozgulsal marked this conversation as resolved.
Outdated
|
||
|
|
||
| Focus on connecting with: | ||
| - CodeYourFuture graduates and alumni | ||
| - Engineers in your target field | ||
| - Recruiters hiring for your role | ||
| - Hiring managers in relevant companies | ||
| - Professionals who engage with content in your industry | ||
|
ozgulsal marked this conversation as resolved.
|
||
|
|
||
| When possible, add a short, polite note. For example: | ||
| > "Hi, I'm a Code Your Future graduate focusing on backend development. I'm building my network in this space and would love to connect." | ||
|
|
||
| A growing and relevant network increases: | ||
| - Profile visibility | ||
| - Access to job posts | ||
| - Referrals | ||
| - Industry awareness | ||
|
|
||
| **Exercise:** | ||
| - Identify 5 people to connect with this week (CYF alumni, engineers, or recruiters in your target field) | ||
| - Write a short connection note for each one | ||
|
|
||
| Note: Does your note explain who you are and why you want to connect? | ||
|
|
||
| ## Stay Visible | ||
| LinkedIn is not only a profile platform. It is a visibility platform. A strong profile helps you get discovered. Activity helps you get remembered. | ||
|
|
||
|
ozgulsal marked this conversation as resolved.
|
||
| You do not need to post daily. Consistency matters more than frequency. Even 1 post per week can significantly increase your exposure over time. | ||
|
ozgulsal marked this conversation as resolved.
Outdated
|
||
|
|
||
| Start with practical and realistic actions: | ||
| - Share a project you built — explain the problem, what you implemented, and what you learned | ||
| - Write about a technical challenge you faced and how you solved it | ||
| - Reflect on something new you learned during CodeYourFuture | ||
| - Share progress updates while building a feature | ||
| - Comment thoughtfully on posts from engineers, recruiters, or companies in your field — add value rather than writing "Great post" | ||
|
|
||
| When you share, keep it simple. You are not trying to impress everyone. You are showing that you are learning, building, and thinking like a developer. | ||
|
|
||
| Over time, consistent activity can: | ||
| - Increase profile views | ||
| - Attract relevant connections | ||
| - Open conversations | ||
| - Create unexpected opportunities | ||
|
|
||
| **Exercise:** | ||
| - Draft your first LinkedIn post using one of the prompts above | ||
|
|
||
| Note: Does it describe something you genuinely did or learned? Is it written in plain, honest language? | ||
|
|
||
| ## Learning Objectives | ||
|
ozgulsal marked this conversation as resolved.
Outdated
|
||
| Our goal is to collectively do the following: | ||
| - [ ] Identify a target role and build a keyword list from job descriptions. | ||
| - [ ] Write a clear and searchable headline. | ||
| - [ ] Write a focused About section that answers the three key questions. | ||
| - [ ] Rewrite at least one experience or project bullet using the XYZ method. | ||
| - [ ] Optimise the Skills section to reflect the target role. | ||
| - [ ] Identify at least one credibility signal to add to your profile. | ||
|
|
||
| ## Set-Up | ||
| - [ ] Open your LinkedIn profile in a browser | ||
| - [ ] Have your keyword list and CV or project notes ready | ||
| - [ ] Split into pairs for peer review | ||
| - [ ] Set a whole class timer for 30 minutes | ||
|
|
||
| ## Instructions | ||
| - [ ] Using your keyword list, update your headline following the suggested structure. | ||
| - [ ] Draft or update your About section answering the three key questions. | ||
| - [ ] Rewrite at least one experience or project bullet using the XYZ method. | ||
| - [ ] Review your Skills section and reorder or remove skills that do not match your target role. | ||
| - [ ] Swap profiles with a partner and give feedback: Is it clear what role they are targeting? Do they show evidence of impact? | ||
| - [ ] Using the Final Review Checklist, identify one area of your profile to improve after the session. | ||
|
|
||
| ## Final Review Checklist | ||
| Before applying for roles, ask yourself: | ||
| - [ ] Is it obvious what role I am targeting? | ||
| - [ ] Are my key skills aligned with current job descriptions in this field? | ||
| - [ ] Do I show practical evidence of impact rather than listing tasks? | ||
| - [ ] Would a recruiter understand my value within 30 seconds? | ||
| - [ ] Have I added at least one credibility signal? | ||
| - [ ] Is my profile picture clear and appropriate? | ||
| - [ ] Am I staying visible with occasional posts or comments? | ||
Oops, something went wrong.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Uh oh!
There was an error while loading. Please reload this page.