My Struggles as a Software Engineer in 2026

#learning #softwareengineering #writing #networking

This post is adapted from my YouTube vlog, "My Struggles as a Software Engineer in 2026!"

I started my journey to become a software engineer two years ago, and the landscape has shifted dramatically since then. One of the most persistent struggles I have faced while trying to break into the industry is the constant feeling of never being good enough or knowing enough. Imposter syndrome is real, and it is a battle I have fought from day one.

When I first started, my goal was simple: learn React, JavaScript, MongoDB, and PostgreSQL, and build a project. I felt a massive sense of pride after building my first two projects. However, the reality of the New York City job market quickly set in.

I noticed a saturation of MERN stack developers.
I realized that knowing React alone would not be my gateway into a solid software engineering role.
I needed to make myself highly useful to an organization, which meant diving deep into backend development.

Choosing the Right Backend Language

I debated between Go and Java for a long time. After analyzing the market on platforms like ZipRecruiter and Indeed, and speaking with industry professionals, a clear pattern emerged. Entry-level opportunities for Golang developers were virtually non-existent, whereas the market showed more opportunity for Java developers.

Once I committed to Java, I was introduced to Spring Boot and Docker containers. This fundamentally shifted how I approached application development.

Development Approach	Methodology
Frontend-First (Past)	Build the UI first. Once the visuals are set, write the logic to support it.
Backend-First (Current)	Wireframe and break down the feature logic first. The UI is built on top of a fully realized architecture.

This backend-first approach makes significantly more sense to me now. By the time I get to the frontend, I already know exactly what the feature must do, making full-stack development much smoother.

Escaping Tool Fatigue with "The Izzy Stack"

The tech industry is relentless. Every day, there is a new tool, a new model, or a "game-changing" framework. Chasing every trend is the fastest way to guarantee you will never feel competent.

To combat this overwhelm, I decided to lock into a specific tech stack, become proficient in it, and only test new tools briefly before integrating them if they truly add value. I refer to my core setup as The Izzy Stack:

Frontend: React, TypeScript, and Tailwind CSS.
Backend: Java, Spring Boot, PostgreSQL, and Supabase.

Switching between frontend and backend development was initially quite challenging, but with time, I gradually became proficient in both areas.

React and TypeScript handle the visual UI (managing state and effects), while Java requires building services, DTOs, and controllers. The implementation details are vastly different, but mastering both domains is necessary for the next level of growth.

System Design vs. LeetCode

In the pursuit of improvement, I evaluated whether to focus on Data Structures and Algorithms (DSA) or System Design.

Honestly, in 2026, grinding LeetCode makes little sense to me when modern AI models can instantly solve those problems. While I understand that some companies still require DSA for interviews, you will rarely use those specific academic puzzles in daily backend work.

System design, however, immediately clicked. I recently picked up System Design Interview by Alex Xu.

Within the first twelve pages, I was learning vital concepts I had never encountered:

Database replication
Vertical and horizontal scaling
The critical role of load balancers in managing web traffic

If your target companies require DSA, you must study it. But for the type of backend systems I want to build, system design provides significantly more practical value.

The Reality of the 2026 Job Market

Let's be honest: the 2015–2020 hiring boom is over.

You can no longer build a simple tic-tac-toe or to-do list app and expect to land a job. The bar has been raised. Recently, I built an entire asynchronous video analysis pipeline using Java, Spring Boot, Supabase, React, TypeScript and various LLMs.

The system ingests video input.
It analyzes the presentation for filler words and body language.
It evaluates the content and overall delivery against professional speaking standards.

Despite the complexity of the project, I still feel the pressure to improve. I have secured multiple interviews thanks to an incredible network of mentors and peers, but converting those interviews into offers remains a challenge. I have received various reasons for why things haven't followed through, which can be frustrating.

However........

All we can do is focus, lock in, and keep building. Opportunity will come. An organization will take a chance on me, and I will maximize that opportunity just like I did during my internship at Archetype Dynamics. So, if you’re navigating this market with me, understand that every rejection is just one step closer to a "yes."

Let's keep grinding.