Like many engineers, I started my job search with a simple idea:

Apply to enough roles and eventually something will work out.

The reality was more complicated.

Some positions were already filled.
Some never responded.
Some required significantly more experience.
Some disappeared before interviews even started.

After a while, I realized something important:

Applications are necessary, but they are not the only mechanism for creating opportunities.

A Simple Probability Problem

Imagine sending 100 applications.

If the response rate is 2%, the expected number of responses is:

100 × 0.02 = 2

Now imagine spending part of that effort on:

Building projects
Writing technical articles
Creating a portfolio
Participating in engineering discussions

None of these guarantee opportunities.

But they increase the number of ways someone can discover your work.

What I Decided to Build

Instead of focusing exclusively on applications, I started working on:

Payment Gateway Design

Understanding transactions, idempotency, retries, and failure handling.

Schema Design Portfolio

Documenting database designs and architectural decisions.

Data Engineering Journey

Exploring Kafka, Spark, Airflow, and distributed systems.

Technical Writing

Sharing lessons learned while studying and building.

The Hard Part Nobody Talks About

The internet often makes personal branding sound easy.

Reality looks more like this:

Writing articles nobody reads.
Publishing posts that get little engagement.
Maintaining projects after the excitement wears off.
Spending months before seeing meaningful results.

There is no shortcut.

The value comes from consistency.

Final Thought

I'm not abandoning job applications.

I'm simply trying to build assets that continue working even when I'm not actively applying.

Applications create opportunities one submission at a time.

Projects and writing create opportunities that can compound over time.

I'm curious how other engineers balance these two approaches.