The New Reality of Breaking into Tech

7 min read

#Career #Tech Industry #AI
Photo by Brey on Unsplash Photo by Brey on Unsplash

A junior software engineer recently reached out on LinkedIn for a referral to our trainee program. I looked through his resume, and my heart sank a little. I knew immediately that he wasn’t a fit. Some of you might find my reasoning too harsh, even diabolical, but the reality for aspiring developers has fundamentally changed. This was my internal calculus:

  • Complete Tech Stack Mismatch. He specialized in a tech stack completely different from what we use. We, like many companies, primarily use front-end frameworks like React and back-end services built with Node.js or Java. We have zero projects using his stack.
  • No Time for Handholding. Our trainee program is an intense, high-pressure environment. We expect juniors to start contributing to real projects almost immediately. It’s not that the trainees won’t find any help, it’s that the nature of help would be different. His resume lacked the evidence of foundational, cross-technology knowledge required for rapid adaptation.
  • The Bar is Simply Higher. AI has reshaped client expectations. Delivery speeds are accelerated, and the complexity of what’s expected, even from a junior, has increased. You need a broader and deeper skillset from day one.

This situation highlights a critical shift in the tech industry. And this is not by choice. This is based on a series of harsh but essential decisions that we had to take based on our experience dealing with international clients. The path for junior developers is tougher than it has been in years. Here’s a straightforward guide for aspiring software engineers, from your first day of university to graduation, on how to navigate this new landscape.

The Bar for Entry is Higher Than Ever

The tech industry is a challenging environment for newcomers right now. Major tech companies have conducted significant layoffs over the past few years, initially citing economic headwinds and now shifting toward “performance-based” reductions. This signals a move toward a culture of high performance where every employee, including those in junior roles, is expected to deliver immediate value.

For junior developers, this means the expectation to hit the ground running is no longer a suggestion; it’s a requirement. Trainee programs and internships are more intense than ever. Companies expect you to contribute meaningfully to your team, not just shadow a senior developer. The evaluation process is tough, and a full-time return offer is never guaranteed.

So, does it mean that you should become an electrician/plumber, as mentioned by Nvidia CEO Jensen Huang? Not really. That’s an extreme opinion, and extremes are never good. However, you must take a series of calculated steps to adapt yourself with the changing landscape of tech industry, and showcase that your value exceeds beyond a simple word prediction machine, a.k.a LLMs.

What to Focus on in University (and Beyond)

Your university years are the training ground for your career. Don’t just aim for good grades; build a rock-solid foundation of practical, in-demand skills.

Master the Fundamentals

New frameworks pop up all the time, but the core principles of software engineering are stable. Focus on these key areas:

  • Being Tech Agnostic: JavaScript is the undisputed king of web development. Python and Java are also consistently in high demand and are sought after by a large percentage of recruiters, however, the context matters. Jobs that demand machine learning and/or data analysis will have their preference towards Python, while enterprise companies tend to look for developers well-versed in Java, C# etc. An AI agent can code in all of these languages. How can you convince someone to hire you instead of going for an AI subscription? By mastering the fundamentals of programming, so that you can apply your understanding in any language.
  • Data Structures and Algorithms: This is the bedrock of efficient coding and a staple of technical interviews. You need to understand concepts like Big-O notation to write performant code. AI agents tend to spit out code that’s not very performant, and you need to be able to catch those instances and correct them.
  • Version Control: You absolutely must be proficient with Git. It’s non-negotiable for any collaborative software development.
  • Web Technologies: Start with the fundamentals of web development like HTML, CSS, and JavaScript. Then, dive into a popular front-end framework like React.

Build a Portfolio That Proves Your Skills

A resume lists your skills; a portfolio demonstrates them. For junior developers, a compelling portfolio is often the key to landing an interview.

  • Show, Don’t Just Tell: Your portfolio needs 2-3 substantial projects that prove you can solve real-world problems. And you guessed it, they need to have the AI factor in them. Learn the basics of Retrieval Augmented Generation, Vector Stores and other necessary details that can help you interface any application with an LLM. This is what will set you apart from the crowd.
  • Tell Your Story: Your portfolio should be more than a project gallery. It should narrate your journey as a developer. For each project, explain the problem, your technical approach, and what you learned.
  • Keep it Fresh: Your portfolio is a living document. Update it regularly with new projects and skills.

AI is Your Co-Pilot, Not Your Replacement

The integration of AI is changing how software is made. As a junior developer, you must learn to use AI tools effectively. If you just hate on AI, or use AI as a crutch, both will lead to the demise of your career. Remember, the goal is to showcase that you are worth more than an LLM. Free tools like Gemini AI Studio, Gemini CLI, Grok, and the free tiers of Claude and ChatGPT can help you with the following:

  • Planning: From my limited experience in teaching undergraduates for a couple of years, I know that majority of the undergraduates love to jump right into coding, without a proper plan first. If you approach using AI tools the same way, it just won’t fly. However, you can write your technical plan first with the help of AI, make refinements, break it down into smaller tasks, and then feed those smaller tasks to an AI agent that can help you implement those tasks more reliably and efficiently.
  • Accelerating Development: AI can handle repetitive tasks, suggest code snippets, and even generate entire functions, allowing you to focus on more complex problem-solving.
  • Learning and Research: AI-powered platforms can personalize your learning and help you grasp new technologies faster.
  • Debugging: AI can assist in identifying and fixing the obvious bugs in your code.

However, there’s a word of caution to be shared: don’t become over-reliant on AI. A strong grasp of the fundamentals is so, so much more critical than having 10 projects in your portfolio that you have little idea about.

Your Path From University to Your First Job

Here is my suggested roadmap to guide you through your university years. It’s not a one-size-fits-all plan, but it has enough room for personalization:

  • Year 1-2: Focus on Fundamentals. Master a core programming language and get comfortable with data structures and algorithms. Start building small personal projects to apply what you’re learning.
  • Year 3: Deepen Your Specialization and Build Your Portfolio. Choose an area to focus on, like front-end, back-end, or mobile development. Build more complex portfolio projects (with tests) and start contributing to open-source (which will force you to write tests). Learn about deployment processes and containerization, such as Docker, as well as the basics of computer networking.
  • Year 4: Network and Prepare for Interviews. Attend tech meetups and career fairs. Connect with alumni and engineers on LinkedIn. Start practicing for technical interviews.

The path to becoming a software engineer has always been challenging. The current landscape simply requires a new level of dedication and forward-thinking. However, it’s also much easier to gain knowledge and upgrade yourself than it was a few years ago. As long as you can utilize that, with a little bit of luck, you should at least be able to get your foot in the door.

Read Next

Jest Is No Longer My Go-To Testing Framework

In the tech world, Jest is the go-to testing framework for many projects. It's easy to set up, integrates nicely with your codebase, and can get the job done pretty well. That's also the reason why all the project starter templates I have created have Jest baked into it, with other auxiliary libraries such as jest-mock-extended to make mocking services for unit tests (UTs) a breeze. But, as our test-suites started to grow in different projects, people started to complain about how long it takes for tests to run. The issue is exacerbated by the fact that the projects also have `husky` installed, and as part of the pre-commit routine, it runs at least the UTs and some integration tests. In essence, Jest was getting the job done, but it was behaving like a reluctant teenager asked to do chores.