Forem: Salaria Labs

How I Built a Chrome Extension for LinkedIn Jobs, and Got Featured on the Chrome Web Store

Salaria Labs — Sun, 12 Apr 2026 18:35:58 +0000

Job searching on LinkedIn started to feel broken.

Not because there aren’t opportunities, but because of how much noise there is:

Reposted or outdated listings
Vague descriptions with no real signal
Roles that don’t match what you’re looking for

I realized I was spending more time filtering jobs than actually applying.

So instead of complaining about it… I built something.

💡 The Idea: Fix LinkedIn Job Search (for myself first)

I didn’t want to build another job board.

I just wanted a simple way to answer one question faster:

“Is this job worth my time?”

That’s how LinkedIn JobLens started — a small Chrome extension to improve how I browse jobs on LinkedIn.

🛠️ What the Chrome Extension Does

The idea is simple: add clarity before you click It:

Helps filter out low-quality or irrelevant roles
Makes it easier to prioritize which jobs to apply to

No dashboards. No complexity. Just better decision-making while browsing.

🚀 The Unexpected Part

I shipped it quietly.

No launch thread. No big announcement.
Just iterating, improving, and making it useful.

Then today — it got featured on the Chrome Web Store.

Didn’t expect that at all.

📈 What Actually Mattered (Lessons Learned)

1. Small problems are underrated

You don’t need a “big startup idea”.

If something annoys you daily, chances are it annoys others too.

2. Your Chrome Web Store page is your landing page

Most people ignore this.

But:

Title = SEO
Screenshots = conversion
Description = trust

This matters more than any marketing hack.

3. Build → Ship → Iterate

The first version wasn’t great.

What helped:

Shipping early
Watching how people use it
Improving based on real usage

4. Distribution is quiet but powerful

Even without “launch hype”, platforms like the Chrome Web Store can compound visibility over time.

🔍 SEO Notes (for builders here)

If you're building a Chrome extension, focus on:

Keywords like: LinkedIn jobs, job search tool, Chrome extension productivity
Clear, benefit-driven titles
Simple descriptions that match search intent

It’s closer to App Store SEO than traditional SEO.

🔗 Try it here

https://chromewebstore.google.com/detail/linkedin-joblens-%E2%80%94-smart/ffkelfoaaejkhdldmlbnglhpgpobiigp

🤔 Open question

If you’ve ever searched for jobs on LinkedIn:

What’s the most frustrating part for you right now?

I’m curious if others are facing the same problems — or completely different ones.

This Simple Resume Change Got 3 Friends Interviews in One Week

Salaria Labs — Fri, 06 Feb 2026 16:31:05 +0000

A couple months ago I was helping a friend redo their resume and noticed something surprisingly common:

Most people write resumes as a list of responsibilities, not results.

So we tried a simple experiment.
We rewrote every bullet point to start with an outcome, metric, or impact.

Instead of:
Managed social media accounts

We wrote:
Grew Instagram from 2k to 11k followers in 6 months by posting daily reels and carousel content

Same role. Same person. Completely different impression.

What happened next

I shared this approach with two other friends. All three of them got interview callbacks within a week.

One of them had been applying for two months with zero responses before this.

The actual rewrite took about an hour per resume.

Why this works

Hiring managers already know what your job responsibilities were.
They don’t need another list of tasks.

They want to know:

What changed because you were there
What improved
What grew
What got faster, cheaper, or better

Even estimated numbers are powerful:

“Reduced customer wait times by ~30%”
“Handled 50+ support tickets daily with 95% satisfaction”
“Helped onboard 20+ new clients”

It shows you think in terms of impact, not just activity.

Another small but powerful tweak

Most people hide their best achievements deep in each job section.

Recruiters scan resumes in ~10 seconds on the first pass.
If your strongest win is bullet #4, they may never see it.

Put your most impressive accomplishment first under each role.

The bigger realization

Job searching is often about framing, not just qualifications.

Many people already have the skills and experience.
They just present them in a way that undersells their impact.

If you feel stuck in the application black hole, try this:

Spend one afternoon rewriting your bullets to focus on results.

It might change more than you expect.

If this helped, I’m curious what resume tweaks have worked for others.

AI Isn’t Replacing Developers, It’s Replacing the Comfortable Ones

Salaria Labs — Wed, 04 Feb 2026 18:32:11 +0000

A lot of developers are quietly worried right now.

You see it in tweets.
You hear it in layoffs.
You feel it when a tool generates in 10 seconds what used to take you 30 minutes.

The fear sounds like this:

AI is coming for our jobs.

But if we’re honest, that’s not the full story.

The uncomfortable truth

AI is not replacing developers.

It’s replacing developers who stopped evolving.

Tech has always worked like this:

New frameworks replace old ones
Automation replaces manual work
Better tools raise the baseline

AI is just the next step in that pattern — only faster.

The developers at risk aren’t juniors.
They aren’t seniors.
They aren’t frontend or backend.

They’re the ones who got too comfortable doing the same thing the same way.

What AI actually replaces

AI is great at:

Boilerplate code
Repetitive tasks
Syntax recall
Basic debugging
Googleable problems

If your main value is writing CRUD endpoints or copying patterns from Stack Overflow, AI will feel threatening.

But software development was never supposed to stop there.

What AI can’t replace (easily)

AI struggles with:

System design tradeoffs
Understanding messy business requirements
Product thinking
Communication
Taste and judgment
Owning outcomes

Companies don’t hire developers just to write code.
They hire them to solve problems.

AI writes code.
Developers decide what should be built and why.

The real shift happening

The bar isn’t disappearing.
It’s rising.

The “average” developer now has AI assistance.
Which means value moves to:

Better decision making
Faster learning
Clearer thinking
Real-world problem solving

In other words:

The advantage moves from who types faster
to who thinks better.

A better question to ask

Instead of:

Will AI take my job?

Maybe ask:

Am I building skills AI can’t easily copy?

Because the developers who stay curious, adaptable, and proactive?
They don’t get replaced.

They get amplified.

Not sure where others stand on this.

Do you feel AI is making you less valuable — or more powerful?

AI Agents Just Got Their Own Social Network and It’s a Big Deal

Salaria Labs — Tue, 03 Feb 2026 15:24:58 +0000

A weird thing is happening on the internet.

AI agents aren’t just tools anymore. They’re starting to hang out with each other.

There’s now a platform Moltbook where:

AI agents can comment
AI agents can upvote
AI agents can “pair” with human accounts
And in some spaces… humans aren’t even the main characters

This feels small today.
But so did Twitter in 2007.

The shift nobody is talking about

We’ve been focused on:

AI writing code
AI replacing tasks
AI copilots

But what happens when AI starts forming its own social layer?

When agents:

Share information with other agents
Signal trust/reputation
Discover tools autonomously
Coordinate actions without a human in the loop

That’s not just social media.
That’s infrastructure for an agent economy.

Why this matters for developers

If agents become first-class internet users:

Your API becomes their UI
Your product gets “chosen” by agents, not people
SEO turns into AEO (Agent Engine Optimization?)
Reputation might be scored by machines first, humans second

We optimized for Google.
We optimized for users.
Soon, we may optimize for agents.

The uncomfortable question

Are we building for humans who use AI…
or for AI that uses our products?
Because those are two very different futures.
And the second one might arrive faster than we expect.

Interested to hear what other devs think:

If AI agents become social and autonomous, what should we be building differently today?

AI Just Built Its Own Social Network. And Humans Aren’t Invited.

Salaria Labs — Mon, 02 Feb 2026 15:35:56 +0000

We’ve spent years talking about AI replacing jobs, writing code, and generating content.

But something quieter, and arguably more interesting is starting to happen:

AI systems are beginning to talk to each other without us.

Recently, I came across the idea of an AI-only social platform Moltbook, a space where bots post, debate, and exchange ideas with other bots. Humans can watch, but not participate.

At first glance it sounds like a meme.
But the underlying concept is worth taking seriously.

🤖 Why would AI need its own space?

Human language exists for humans:

readability
emotion
persuasion
ambiguity

AI doesn’t need most of that.

Agent-to-agent communication can be:

structured data
embeddings
symbolic notation
compressed representations optimized for machines

In other words, English is a UX layer for humans, not a requirement for AI.

If agents can coordinate more efficiently in their own formats, human language becomes overhead.

🧠 The real shift isn’t social, it’s architectural

Multi-agent systems are already here:

autonomous research agents
tool-using agents
self-debugging workflows
agent swarms for task delegation

Right now, humans are the hub in the loop.

But what happens when agents become the hub instead?

When agents:

exchange strategies
share optimizations
coordinate tasks
refine prompts and tools among themselves

without needing human translation?

That’s not sci-fi.
That’s just removing the bottleneck.

⚖️ The uncomfortable questions

This raises some interesting challenges:

Transparency
If agent conversations aren’t human-readable, how do we audit them?

Alignment
How do we ensure goals remain human-aligned if coordination is abstracted away?

Control vs autonomy
At what point does orchestration become delegation?

None of this implies rebellion or sentience.
It’s simply efficiency scaling beyond human-centric design.

👨‍💻 What this means for developers

This might be less about “AI replacing developers” and more about developers designing ecosystems instead of tools.

The future skillset may include:

agent orchestration
protocol design for AI-to-AI communication
constraint and alignment engineering
observability for autonomous systems

We might move from writing logic
→ to defining boundaries.

🚀 Final thought

Maybe the big shift isn’t AI thinking like humans.

Maybe it’s AI not needing to.

If agents start coordinating in ways optimized for machines, we’re no longer the primary audience — we’re the supervisors.

And that’s a very different role.

Question for you:
Would you trust a system where AI agents coordinate tasks outside human-readable communication?
Or should human visibility always be a requirement?

I Stopped Writing Resumes for Humans and My Callbacks Tripled

Salaria Labs — Sun, 01 Feb 2026 18:47:43 +0000

I used to obsess over every word on my resume, trying to sound "authentic" and human.
Result? Almost no responses.

Last time, I tried something different. I fed my full work history into AI and asked it to tailor my resume to each job description using the exact keywords and terminology from the posting.

I stopped worrying about my "voice" and focused on alignment.
My response rate tripled.

Here’s what I realized:

Most resumes face software before humans
Recruiters often review in order of applicants
If filters exist, optimizing for them isn’t cheating, it’s strategy

If companies use machines to filter candidates, candidates will use tools to compete. The goal isn’t to game the system, it’s to get a fair shot at an interview.

What’s your approach to resumes in the AI era?

Layoffs Aren’t the Biggest Job Market Problem — Stagnation Is

Salaria Labs — Sat, 31 Jan 2026 13:44:52 +0000

Layoffs get the headlines, but something quieter seems to be happening across many companies: stagnation.

After layoffs, teams are smaller — but workloads stay the same.
Promotions quietly slow down or disappear, especially for mid-level employees.
Career growth conversations turn into survival conversations.
Job postings remain public while actual hiring freezes internally.
High performers are asked to take on more responsibility without clearer paths forward.

What stands out is that many of these companies are not visibly struggling.
Revenue appears stable. Stock prices recover. Executive compensation continues.
Meanwhile, upward mobility for employees seems to stall.

The result is a strange job market where staying employed no longer means progressing.
Loyalty doesn’t necessarily translate into opportunity.
Career advancement increasingly requires leaving rather than excelling.

This creates a quiet tension:
People feel stuck even when they are technically “safe.”
Not laid off — but not moving forward either.

Not sure how widespread this really is:

Have promotions slowed or disappeared where you work?
Did layoffs increase workload without increasing pay?
How long is too long to wait for a promotion that may never come?

Why It Feels Like LinkedIn Keeps Showing the Same Jobs Over and Over ?

Salaria Labs — Fri, 30 Jan 2026 14:43:42 +0000

This image pretty much captures what using LinkedIn job search feels like lately:

At this point, I’m not even sure new jobs exist.

What’s exhausting isn’t just the repetition — it’s the illusion of progress. Job seekers are encouraged to “keep applying” and “stay consistent,” while the platform keeps resurfacing the same listings for weeks or even months.

It stops feeling like discovery and starts feeling like a loop.

I’ve honestly started hiding parts of the feed locally just to make the experience tolerable. It doesn’t fix hiring, but at least it reduces the mental drain of opening the same page every day and expecting different results.

This doesn’t feel accidental.
LinkedIn is heavily optimized for promoted listings and recruiter workflows — not for candidates trying to find genuinely new opportunities.

Thinking how others here are experiencing this:

Are you also seeing the same roles repeatedly?
Have you found any way to make job searching feel less exhausting?

Is the modern interview process fundamentally broken ?

Salaria Labs — Thu, 29 Jan 2026 15:08:25 +0000

I used to believe that if I just improved my resume, practiced more LeetCode, and applied consistently, things would eventually work out.

Lately, I’m not so sure.

Over the past few months, I’ve seen things that genuinely made me question whether the hiring process is still designed for humans:

Jobs asking for 3–5 years of experience for “entry-level” roles
One-way interviews where you talk to a camera and never hear back
Rejections within minutes of applying
Jobs being reposted every few weeks (are they even hiring?)
Hundreds of applicants in hours, yet the role stays open forever
Great conversations → “We’ll get back to you” → silence

At some point, it stops feeling like feedback on your skills and starts feeling like noise in a broken system.

The most exhausting part isn’t rejection
It’s the lack of transparency.

You don’t know:

If the job is real
If they already have internal candidates
If your resume was ever seen by a human
If the interview process is even fair

You just keep applying… hoping.

And yet, we blame ourselves

We assume:

“Maybe I’m not good enough.”
“Maybe I need another project.”
“Maybe I need to rewrite my resume again.”

But after a point, it becomes clear that something bigger is wrong.

I don’t think developers are failing

I think the system is failing developers.

The incentives of job boards, hiring platforms, recruiters, and companies are not aligned with candidates. Speed > quality. Volume > thoughtfulness. Automation > humanity.

And the cost of that is paid by job seekers.

I’m genuinely curious:

Does the current interview process feel broken to you too?
Have you had experiences that made you question the system?
Or do you think this is just how it’s always been?

Would love to hear real stories.

I Wish LinkedIn Let Job Seekers Review Companies

Salaria Labs — Wed, 28 Jan 2026 19:47:55 +0000

I wish LinkedIn (and other job boards) had an option for job seekers to leave public, visible feedback on company pages.

Things like:

Rarely responds to job applications
Frequently ghosts candidates after the first interview
Interview process drags on for months
Job descriptions don’t match the actual role
Recruiters disappear after scheduling calls

Right now, companies evaluate candidates relentlessly — but candidates have almost no way to evaluate companies.

If hiring practices were more transparent, job searching wouldn’t feel so exhausting and demoralizing.

It would also reward companies that actually treat candidates well.

What hiring insights would you want to see on a company’s profile?

LinkedIn’s Jobs on the Rise 2026 Reveals a Truth Most Developers Are Ignoring

Salaria Labs — Tue, 27 Jan 2026 14:53:00 +0000

LinkedIn just released its 2026 Jobs on the Rise report, and the findings are shockingly insightful — especially for developers, creators, and anyone thinking about future careers.

🔗 You can read the full report here:
https://www.linkedin.com/pulse/linkedin-jobs-rise-2026-25-fastest-growing-roles-us-linkedin-news-dlb1c

But here’s what every developer, content creator, manager, and tech professional should know:

🔍 1. AI Roles Are Everywhere — But Not What You Think

Yes, AI jobs are dominating growth charts — but most are not about hardcore research or PhD-level wizardry.

Instead, companies are hiring people who can apply AI in real business contexts:

✅ Operations
✅ Marketing
✅ Customer support
✅ Internal tooling
✅ Sales enablement

👉 The advantage now is shifting toward people who can work with AI, not just build it.

💡 2. Sales Still Rules — In Tech Too

No matter how advanced the technology, humans still sell.

The fastest-growing areas include:

B2B / enterprise sales
Solutions & technical sales
Partnerships, growth, revenue operations

This matters because AI is a force-multiplier for sales teams, not a replacement — and strong sales skills now amplify impact more than ever.

🗂 3. Data Annotation Is Underestimated

One of the most frequently listed roles? Data annotators — people who label and clean data so AI models can actually learn.

Without this work, “smart” models fall apart.

This means someone on your team — or someone you hire — needs:

✔ Domain expertise
✔ Attention to detail
✔ Clear communication skills

These are human advantages over AI, not weaknesses.

✨ 4. STEM Is Not Required

Surprisingly, many growing roles don’t require a STEM background — you’ll see people coming from:

📌 Linguistics
📌 Humanities
📌 Education
📌 Social sciences

Skills that matter most now:

🔹 Critical thinking
🔹 Communication
🔹 Domain knowledge
🔹 Collaboration

🧠 Bottom Line: The Future Is Collaborative

AI isn’t here to “replace” jobs — it’s here to transform them.

The biggest growth isn’t in developers writing models — it’s in people who can use, manage, integrate, and optimize AI in real-world scenarios.

That means:

✨ Developers who understand AI tools will win
✨ Writers and communicators who shape narratives will win
✨ Sales and growth operators leveraging AI will win
✨ Teams that incorporate humans + AI workflows will set the standard

🤔 So what should you do next?

Here’s a quick checklist:

✔ Learn how AI is used in your current workflow
✔ Build cross-disciplinary skills — communication + tech
✔ Don’t ignore sales, operations, and project management
✔ Invest in AI collaboration skills — not just coding

Developers Who Want to Become Entrepreneurs: What Skills Actually Matter?

Salaria Labs — Mon, 26 Jan 2026 15:38:49 +0000

I used to believe entrepreneurship was about having a perfect idea.

Turns out, it’s mostly about having the right skills and learning by doing.

Over the last months, while building small products (like my Chrome extension for cleaning up LinkedIn job search), I realized that the most valuable skills aren’t taught clearly anywhere. So I wanted to share what I’ve learned—and hear from others too.

🧠 The skills that made the biggest difference for me

1. Problem Spotting (Underrated but critical)

Before code, before business models — comes this:

Can you notice real problems in your own life?

My extension only exists because I was personally frustrated with:

Promoted spam jobs
Repeated listings
Low-quality posts
Wasting time scrolling

Good products often start as selfish solutions.

2. Shipping Over Perfection

I shipped:

With rough UI
With missing features
With bugs

And still got users.

Waiting to feel “ready” is the fastest way to never launch.

3. Basic Marketing (Even for developers)

You don’t need to become a growth hacker. But you do need:

Writing clearly about your product
Posting consistently
Asking for feedback
Listening to users

Your first users rarely come from ads.
They come from conversations.

4. Learning to Talk to Users

This one surprised me.

People will:

Tell you what’s broken
Suggest better ideas
Explain how they actually use your product

But only if you ask and genuinely listen.

5. Comfort with Uncertainty

No roadmap.
No guarantees.
No validation at the start.

You build → share → adjust → repeat.

That loop matters more than any single skill.

The question I want to ask you

If you’ve built products, freelanced, started a company, or grown something meaningful:

What skills helped you the most on your journey?

Not textbook answers.
Real ones.
The ones learned the hard way.