Cracking a tech interview is one thing, but it's a whole other level of difficulty to get an interview at all: using LinkedIn
Oliver Jumpertz argues that getting tech interviews often depends more on visibility than on interview skill, and that LinkedIn is an efficient way to market yourself with limited time. He explains how LinkedIn works as a professional network with strong recruiter presence and long‑lasting organic reach, then outlines how to register, set up, and strategically optimize a profile so it ranks in recruiter keyword searches. He recommends positioning yourself as a focused specialist, crafting a keyword‑rich headline and About section, curating a relevant skills list, setting yourself as open to offers, and optionally posting content for extra visibility. In later replies he adds that work history should emphasize measurable achievements rather than tasks and that some profile details (like employer names) can be omitted or generalized when necessary.
Reading notes#
- The main challenge in tech hiring is often getting an interview at all, not just passing one.
- The author reports heavy inbound recruiter interest after optimizing his LinkedIn, framing this as evidence that the platform drives visibility.
- LinkedIn is presented as a professional social network where users have profiles, list skills, pin content, and post text plus media.
- Compared to Twitter, LinkedIn content tends to have higher, longer‑lasting organic reach, staying relevant for days instead of vanishing after a day.
- Many recruiters are active on LinkedIn, and one of the platform’s core concepts is facilitating hiring by connecting companies with potential candidates.
- With relatively little work, a user can gain enough visibility on LinkedIn to be noticed and contacted by recruiters.
- Twitter activity is encouraged but described as requiring more continuous effort, which can be difficult alongside job, family, and other responsibilities.
- LinkedIn is suggested as a good option for people who lack time to create frequent content, because much of the setup is a one‑time effort.
- First setup step: register, create a basic profile, write a headline, fill the About section, add a profile picture, and list some skills.
- Optimization is described as the key factor: recruiters search via keywords, similar to SEO for websites.
- When recruiters search with keyword strings and boolean logic, LinkedIn scans the headline, About, and skills sections for matches.
- More keyword hits in these sections increase a profile’s relevance score for a given search.
- Users are warned not to dump a random keyword cloud; the profile must still look human and professional to pass a recruiter’s judgment.
- The author advises first clarifying what kind of role you want so you can align your profile accordingly.
- Profiles should resemble focused CVs: keep information relevant and avoid listing everything you know to prevent looking unfocused.
- Main rule: present yourself as a professional specialist for the role you want, with freedom to later retarget your profile.
- You should list what you are looking for and then identify which skills are relevant to that target.
- From all identified skills, select primary ones that deserve prominence (e.g., HTML, CSS, JavaScript, and a framework for frontend roles).
- Secondary tools like bundlers (e.g., Webpack, Parcel) may be less important as headline skills for a frontend developer.
- Headline advice: include who you are, your years of experience, and your key skills.
- A generic, emotional headline such as loving software development is said to perform poorly in recruiter searches.
- Example of a stronger headline: a role title, years of experience, and core tech stack listed in one line.
- The headline acts as the first confirmation for recruiters that you match their search in terms of role, experience, and skills.
- Explicitly stating experience in the headline is emphasized because LinkedIn does not reliably aggregate years from work history.
- About section functions as a bio where you can describe who you are and what you do, while also contributing keywords.
- The goal for the About section is to embed main keywords in a compelling text that adds detail beyond the headline.
- Sample About text combines years of experience, specialization (e.g., frontend), core technologies, frameworks, and current team context.
- The author notes you can add some side skills if desired, but stresses that the sample already covers the key terms.
- The skills section is positioned as the place to list all relevant technologies tied to the roles you are targeting.
- Secondary skills such as bundlers, additional frameworks, and soft skills belong in the skills list.
- Communication ability and familiarity with agile methodologies are cited as soft skills worth listing.
- Users are urged to list only skills relevant to their target positions and to omit technologies whose relevance they cannot justify with full confidence.
- Final profile step: set job preferences and mark yourself as open to work, including up to five desired titles.
- Location preferences can include current city, a tech hub, or a city where you are willing to relocate, and you can flag openness to remote work.
- Users should also specify the types of roles they want (full‑time, part‑time, contract, etc.).
- Posting LinkedIn content is labeled optional but helpful for boosting visibility; even one valuable post per day can help build connections.
- Because LinkedIn’s algorithm keeps posts visible for days, each post can repeatedly reach potential recruiters or connectors.
- The author frames this content reach as an opportunity to gain connections that may eventually lead to interviews or jobs.
- At the end of the main thread he invites readers to like, retweet the first tweet, and follow him for similar content.
- In replies he agrees with a commenter that certain additional tactics they mentioned usually help.
- He notes that work history and experience sections can boost credibility, but says naming the company is not strictly mandatory.
- Where a company name cannot be shared, he suggests using a generic label like “Software services company”.
- He stresses that describing what you did at a company matters more than the company’s name.
- To sell your experience, he recommends framing work in terms of measurable outcomes, using numbers.
- He contrasts a vague description like “built frontend for clients” with a quantified impact example involving reduced accounting costs.
- Another example describes refactoring a build system and quantifying improvements in compilation times and resulting cost reductions.
- He encourages using the About section to state that you are looking for work and prefer remote roles, in addition to the official “looking for work” feature.
- In feedback to one user he advises adding years of experience to the headline and incorporating more skill keywords when job‑hunting.
- He compliments a user’s inclusion of many soft skills in the skills section and calls that approach good.
- He comments that old or outdated skills add little value in the headline or About section and should instead appear in work history if needed.
- For new roles, he argues that only the skills relevant to the desired position matter.
- He tells a commenter that a certain unspecified action is not worth the effort, in his opinion.
- Reviewing another profile, he says the headline looks good but recommends avoiding third‑person writing in the About section.
- He also suggests making use of the profile’s featured section to highlight examples of work.
- He reiterates that descriptions of past jobs should focus on achievements with numbers rather than generic statements of duties.
- Across his replies, he repeatedly expresses happiness and gratitude when readers say the thread helped them or share positive feedback.
- He mentions that he had posted additional lessons the previous day, implying ongoing sharing of LinkedIn optimization advice.
