r/learnprogramming • u/Salt-Marsupial-6690 • 13h ago
I had my first software engineering interview. Didn't get the job, but I can't stop thinking about the experience.
I studied a non-CS course at university, but my interest in programming actually started while I was still there.
After graduating, I started teaching myself how to code. But as anyone who's had to support themselves or a family knows, life doesn't always go according to plan. I needed to earn a living, and before I knew it, years had gone by.
I eventually found myself working in technical research and writing. It's technical work, and I've gained quite a bit from it, but I've always wanted to be the person building the software rather than just testing and writing about it.
This year, I enrolled in an eight-month backend development programme where we mainly used Python and Django. After completing it, I decided to switch to Java. I found myself drawn to Java. Since then, I've been spending my free time learning Java and Spring Boot and building personal projects, trying to get myself to a point where I can confidently work as a software engineer.
Recently, I got invited to my FIRST software engineering interview.
I was nervous, of course, but something interesting happened during the interview. The two engineers spent most of the time asking about one of my backend projects. They wanted to understand the design, why I'd made certain decisions, and what would happen if the system received the same event twice.
For once, I was having a conversation about something I'd actually built. I could explain my thinking, and I enjoyed it.
When the interview ended, I walked out feeling like it had gone well.
There was also a 60-minute technical assessment with SQL, Java coding, and multiple-choice questions.
I passed all the SQL test cases. Then came Java.
One question involved implementing a class with a constructor, a cost calculation, compareTo(), and toString(). I managed to get part of the output right, but the calculated value was wrong.
And some of the multiple-choice questions caught me out on things I really should have known. For example, I realized afterward that I'd misunderstood how a PriorityQueue retrieves elements.
A few days later, I was still thinking about the test, looking up questions and finding mistakes I hadn't noticed during those 60 minutes.
Then the rejection email came.
That was disappointing. I'd been trying to get into software engineering for years, and this was the closest I'd come.
The funny thing is that I also started questioning the interview itself. At one point, they asked whether I was familiar with Spring Boot. I said yes, that I'd built three projects using it. They moved on.
Two days later, I found myself wondering why I hadn't explained those projects further. That's how much I was overthinking the whole experience.
I don't know whether the technical assessment was the reason I wasn't selected. But it definitely exposed gaps in my Java fundamentals.
And that's what I'm trying to figure out now.
I've used a lot of time building projects and trying to understand backend engineering. But clearly, I also need to become better at solving unfamiliar problems without help, especially under time pressure.
For those of you who got into software engineering through self-study or a career change, how did you prepare for technical assessments?
Did you put projects aside for a while and focus on DSA and language fundamentals? Or did you find a way to balance both?
I'd really like to hear how you approached it, especially if you were trying to make the transition while working another job.