React is no longer a valuable skill
This open house had a wide mix of participants:
- freshers
- people with career gaps
- job seekers
- folks looking to switch domains
A common pattern: most want to work on React.
Here’s the reality—React is still useful, but it’s no longer a differentiator. It cannot be your only skill.
I haven’t written serious React code in over six months. And unless you’re solving very niche problems, deep React internals aren’t expected anyway.
With tools like AI agents (and well-defined codebases), React expertise is increasingly commoditized. Most companies already have established patterns—you’re not reinventing React there.
If you think React alone will get you hired, you’re in for a surprise.
So what should you do?
Double down on system design and engineering patterns.
AI is powerful—but you need to be in the driver’s seat. Your value comes from guiding it with good design and decision-making.
Be an Engineer first, then a Frontend Engineer
AI has blurred role boundaries. Frontend engineers can now do backend work and vice versa.
That makes foundations more important than ever.
Your tech stack matters less. What matters:
- Can you solve problems?
- Can you use AI effectively to implement solutions?
Aim to be a strong generalist.
You’re likely already a frontend specialist—good. Now expand beyond that.
With code becoming cheap, iteration is easier. What stands out now:
- product sense
- design sense
Companies hire you to solve:
- Technical problems
- Product problems
In established companies → more technical problems
In startups → more product problems (plus some tech)
Startups are exhausting—but fun.
Product engineering is the future
Even in large companies, most teams work on product, not deep technical systems.
And product work is where the highest impact lies—it directly affects revenue.
To be a strong product engineer:
- Understand the product deeply
- Understand the domain
Start with the job description. Know what the company does. Interest in the domain matters—a lot.
If you already know the domain, you have a head start. If not, learning it can be hard (and sometimes uninteresting).
Read this: Job description is there for a reason
Building product intuition
If you’re in a startup, you may not have:
- a designer
- a product manager
So:
- Study competitors
- Learn from what already works
Don’t copy blindly. Understand why something works and adapt it.
A great example of strong product + design thinking:
- Nextdoor Company — job listings, but visualized on a map. Simple idea, but a powerful UX shift.
Before writing code
Always define:
- What problem are you solving?
- How does it impact users?
- How does it drive revenue?
- What are the success metrics (KPIs)?
If you don’t measure it, you can’t evaluate it.
(Yes, this is hard—even I struggle with it.)
Design sense matters (even if it’s subjective)
Good design can elevate a bad product.
Bad design can ruin a great one.
The challenge: design is subjective.
How to improve:
- Design often
- Study patterns
- Read design material
- Get feedback
Expect disagreements. Use data where possible.
If data isn’t available:
- Compare with established products
- Justify decisions with reasoning
Don’t copy—understand intent.
For example, Jony Ive—best known for helping shape touchscreen-first products at Apple—reportedly designed the Ferrari Luce with almost no touchscreens.
References:
- Ferrari Luce
- Top Gear: “A large touchscreen doesn’t work in a car, sir” — Jony Ive on designing Ferrari Luce
Optimize for getting interviews (not just preparing)
A common question:
Should I grind DSA/LeetCode?
Yes—but not immediately.
First, optimize for getting interviews.
There’s no point preparing if you don’t have interviews.
Focus on:
- Being visible (LinkedIn, Reddit, etc.)
- Building projects
- Writing and sharing content
Applying strategy
Timebox your applications:
- 10–30 minutes per day
- Only apply during that window
This improves quality and avoids random, low-effort applications.
It works.
Read this for motivation: You will find a job
This blog post was quickly AI-generated written by me using the sticky notes from the live session. Do join our discord community to get early access to the live sessions.