Standing Out

The cold application is the least effective way to get a job in tech. Submitting your resume through a company's careers page puts you in a pile with hundreds of other applicants, filtered first by software, then by a recruiter spending 6 seconds per resume. The people who consistently land interviews at top companies are not necessarily better engineers — they are better at being visible. Referrals, technical writing, speaking, open source contributions, and building in public create compounding advantages that cold applications never will.

Referrals: The 10x Multiplier

A referral does not guarantee an interview. But at most companies, referred candidates skip the ATS, land directly on a recruiter's desk, and get a response within days instead of weeks. The conversion rate from referral to phone screen is roughly 10x that of a cold application.

Cold application:    ~3% chance of getting a phone screen
Employee referral:  ~30% chance of getting a phone screen

These numbers vary by company and role, but the ratio is consistent. At some companies, referrals account for 40-50% of all hires despite being a small fraction of total applications.

How to Get Referrals Without Being Awkward

The key principle: give before you ask. Build relationships before you need them.

Good approach:
  1. Identify 5-10 people at your target company (LinkedIn, meetups,
     open source communities, former colleagues)
  2. Engage genuinely with their work — comment on posts, contribute
     to their projects, share their writing
  3. Have a conversation about their work at the company — what they
     are building, what they like, what challenges they face
  4. After building rapport, mention you are exploring opportunities
     and ask if they would be comfortable referring you
  5. Make it easy: send them your resume, the specific job link,
     and a 2-sentence summary of why you are a fit

Bad approach:
  "Hey, I see you work at Google. Can you refer me?"
  (No existing relationship, no context, no effort)

Former colleagues are the easiest referral source. People who have worked with you and trust your abilities will refer you without hesitation. Maintain those relationships even when you are not job searching.

If you genuinely have no connections at a target company, start building them 3-6 months before you plan to apply. Attend meetups they host, contribute to their open source projects, engage with their engineering blog posts. This is a long game, but it works.

The Referral Conversation

When you do ask, be direct and make it easy for them:

"Hey [Name], I've been following your work on [project] and
really enjoyed our conversation about [topic] at [event]. I'm
currently exploring backend engineering roles, and I noticed
[Company] has an opening for [specific role]. Would you be
comfortable submitting a referral for me? Happy to send you
my resume and the job link to make it easy on your end."

Most people are willing to refer someone they have a genuine connection with. They get a referral bonus if you are hired, so it is mutually beneficial. Just do not ask strangers — that puts them in an awkward position.

Technical Blogging

Writing about technical topics is one of the most underused strategies for standing out. A well-written blog post demonstrates:

Deep understanding of a topic (you cannot explain what you do not understand)
Communication skills (critical in interviews and on the job)
Curiosity and initiative (you did this on your own time)
Thought process (how you approach problems, debug issues, make decisions)

You do not need to be original or groundbreaking. Some of the most valuable technical blog posts are:

High-value post types:
  - "How I debugged X" — walk through a real debugging session
  - "Comparing A vs B for [use case]" — benchmarks, tradeoffs
  - "What I learned building X" — post-mortem on a project
  - "A practical guide to X" — tutorial based on real experience
  - "Why we chose X over Y" — decision-making process

Low-value post types:
  - "Getting started with React" (thousands of these exist)
  - Rewriting documentation in your own words
  - Hot takes with no substance
  - Posts that are obviously written to game SEO

Where to publish:

Personal blog: Full control, builds your brand. A simple static site is sufficient.
Dev.to or Hashnode: Built-in audience, easy setup, good for starting out.
Company engineering blog: High credibility if your company has one. Ask your manager about contributing.
Medium: Large audience but increasingly behind paywalls. Less respected in tech circles than it used to be.

Consistency matters more than volume. One well-written post per month is enough to build a meaningful body of work over a year.

Speaking at Meetups & Conferences

Public speaking terrifies most engineers, which is exactly why it is such a strong differentiator. You do not need to keynote a major conference. Start small:

Speaking progression:
  1. Lightning talk at a local meetup (5 minutes)
  2. Regular talk at a local meetup (20-30 minutes)
  3. Talk at a regional conference (30-45 minutes)
  4. Workshop at a conference (half day)

What to talk about:

A problem you solved at work (generalized, no proprietary details)
A tool or library you built and what you learned
A comparison of approaches you evaluated for a real project
Lessons from a failure or incident (these are the most popular talks)

The preparation process forces you to organize your thinking, which makes you better at system design interviews and technical communication. And the connections you make at events lead directly to referrals.

Contributing to Open Source

Open source contributions create visibility in ways that private work cannot. Your code is public, your discussions are public, and maintainers remember helpful contributors.

Strategic contribution, not random drive-bys:

High-impact contributions:
  - Fix a bug in a tool your target company uses or maintains
  - Implement a feature requested in an issue with 50+ upvotes
  - Improve documentation that confused you (and probably others)
  - Build a plugin or extension for a popular project
  - Review and test other people's PRs (maintainers notice this)

Low-impact contributions:
  - Fixing typos in random repos (fine for learning, not for signal)
  - "Hacktoberfest" style bulk PRs
  - Adding comments to obvious code

If your target company maintains open source projects (most large tech companies do), contributing to those projects is one of the most direct paths to getting noticed. Google, Meta, Microsoft, and others have engineers who review external contributions. A strong PR creates a direct connection.

Building in Public

Building in public means sharing your work and process openly as you go, rather than revealing a finished product. It works because it builds an audience and creates accountability.

What building in public looks like:
  - Tweeting progress updates on a side project
  - Writing weekly dev logs about what you built and learned
  - Streaming your coding sessions
  - Sharing architecture decisions and tradeoffs in real time
  - Posting demos of work in progress

Where to build in public:
  - Twitter/X (tech community is active there)
  - LinkedIn (especially for career-oriented content)
  - YouTube (for longer-form content)
  - GitHub Discussions or Issues on your own projects
  - Discord or Slack communities in your tech niche

The compound effect is real. Over 6-12 months of consistent sharing, you build a network of people who know your work, follow your progress, and think of you when opportunities arise. Multiple engineers have landed jobs at their dream companies because someone on the hiring team followed their work online.

The Hidden Job Market

Not all jobs are posted publicly. Many roles, especially senior and leadership positions, are filled through networks before a job posting is ever created. This is the hidden job market.

How positions get filled informally:

1. Manager identifies a need on their team
2. They ask their network: "Know anyone good?"
3. A former colleague, conference connection, or open source
   collaborator recommends someone
4. That person gets a conversation (not even an interview)
5. If there's mutual interest, the role is created or adjusted
6. The job posting goes up after the candidate is already in process
   (sometimes just for compliance)

You access the hidden job market by being visible and connected. Every blog post, conference talk, open source contribution, and genuine professional relationship increases your surface area for these opportunities.

Networking Without the Cringe

Most engineers hate "networking" because they picture forced small talk at happy hours. Real professional networking is simpler and more genuine:

Authentic networking:
  - Help someone debug a problem in a community Slack
  - Give feedback on someone's open source project
  - Share someone else's blog post and add your own perspective
  - Follow up after meeting someone at a meetup with a specific
    reference to your conversation
  - Introduce two people who should know each other
  - Congratulate someone on a new role or accomplishment

Not networking:
  - Cold messaging 100 people on LinkedIn asking for referrals
  - Collecting business cards with no follow-up
  - Only reaching out when you need something
  - Posting generic "inspirational" content for engagement

The best networkers are people who are genuinely helpful and interesting. They share useful content, help others solve problems, and maintain relationships over time.

Combining Strategies

These strategies compound when combined:

Month 1-3:
  - Start a blog. Write one post per month.
  - Find a local meetup and attend regularly.
  - Identify 2-3 open source projects to contribute to.
  - Clean up your GitHub profile.

Month 4-6:
  - Give a lightning talk at a meetup.
  - Make your first meaningful open source contribution.
  - Connect with people at your target companies online.
  - Share your blog posts and projects on social media.

Month 7-9:
  - Your blog has 6+ posts. Share them when relevant in discussions.
  - You have 2-3 open source contributions. Mention them naturally.
  - You have connections at target companies. Relationships are warm.
  - Give a full-length talk at a meetup or regional conference.

Month 10-12:
  - Apply for roles with referrals from your network.
  - Your online presence backs up your resume.
  - Hiring managers Google you and find your blog, talks, and code.
  - You are not a random applicant — you are a known quantity.

This is a 12-month investment. You can shortcut it if you already have some of these pieces in place, but the compound effect of multiple signals is what makes it powerful.

Common Pitfalls

Waiting until you need a job to network: By then it is too late. Relationships take months to build. Start when you are not looking.
Optimizing for vanity metrics: Follower counts, star counts, and like counts are not the goal. One genuine connection at a target company is worth more than 10,000 followers who do not know your work.
Being inauthentic: People can tell when you are networking transactionally. Genuine interest in others' work and genuine helpfulness are more effective than any strategy.
Only applying cold: If you are submitting 50 cold applications per week and getting no responses, the problem is not your resume — it is your strategy. Invest that time in referrals and visibility.
Perfectionism with content: Your first blog post will not be great. Your first meetup talk will be nervous. Ship it anyway. Consistency and improvement over time matter more than initial quality.
Ignoring LinkedIn: Engineers often dismiss LinkedIn as corporate fluff, but recruiters live there. A complete, keyword-rich LinkedIn profile with your projects and writing is passive job-search infrastructure that works while you sleep.

Key Takeaways

Referrals convert to interviews at roughly 10x the rate of cold applications. Building relationships before you need them is the most important job-search investment you can make.
Technical blogging demonstrates depth, communication skills, and initiative. One post per month for a year creates a meaningful body of work.
Speaking at meetups and conferences differentiates you from the vast majority of engineers who never present. Start with a 5-minute lightning talk and build from there.
Open source contributions create public evidence of your skills and connect you directly with engineers at target companies.
These strategies compound over 6-12 months. The engineers who consistently land great roles are the ones who invest in visibility continuously, not just when they are job searching.