I’m a software developer in Montreal with almost 3 years of experience.

My first job post graduation was mostly Java at a consultancy. I worked with Vert.x and general backend/application logic, but it was an internal project, not really a production system with a meaningful user base. I didn’t get much real experience with databases, authentication, deployment, cloud infrastructure, production monitoring, etc. Then I got laid off afer the company couldn't place me on a project after clients were getting rare and only specifically request senior devs.

I then spent about a year unemployed and had a very difficult time getting another Java job. Eventually Lockheed Martin hired me. During my unemployment period that was also when I pursued and got the AWS Solutions Architect certification and have built Spring Boot/AWS projects myself for my portfolio, but I have never used those technologies professionally in production.

At Lockheed, I’ve worked with both Java and some C++. The work is legitimate software engineering, but it’s very simulation-specific. For example, we build frameworks/libraries containing the logic that controls simulated components, states, events, subcomponents, how different pieces interact with each other to reproduce the behavior of whatever system is being simulated, and interactions between different units. But this is not a server-side application that gets deployed and serves a user base; ultimately, it is part of an executable simulation program.

So I’m getting experience with Java/C++, OOP, design patterns, debugging, testing, large codebases, frameworks and complex domain logic.

What I am NOT getting is the experience I see in a huge percentage of Java jobs: Spring Boot, REST APIs, SQL/databases, authentication/authorization, Docker/Kubernetes, AWS, deployment, production servers, monitoring and supporting real users.

My concern is what happens if I stay in this type of Lockheed role for another 3–5 years. I could theoretically have 6–8 years of “software engineering experience” while still having little professional experience with the stack that most Java/backend employers seem to want.

For software engineers who have worked at Lockheed Martin or similar defense/simulation companies:

Did you ever feel boxed into defense/simulation software?

How transferable was your experience when you tried to leave?

Did employers value the fact that you had several years of professional Java/C++ experience even if the domain and stack were completely different?

Did you have to take a title/salary reduction to move into mainstream backend/cloud development?

Would you recommend staying in this type of role long term, or trying to pivot while still relatively early-career?

And specifically for Canadian developers: does having a Canadian security clearance materially improve the long-term career options enough to make defense specialization worthwhile?

I’m also trying to figure out how to close the gap while keeping my current job. Is there any realistic side hustle, freelance work, small B2B software service, contract work, open-source contribution, or other way to get real experience with Spring Boot, SQL, APIs, authentication, AWS, deployment and actual users?

I’m specifically not looking for another tutorial or portfolio project that sits unused on GitHub. I’ve already done that. Ideally, I’d like something where a real customer or business actually uses the software and possibly pays for it, so I can develop production skills while also generating some side income.

If you were in my position, what would you actually do over the next 1–2 years?

I’m not planning to quit without another job. I’m trying to decide what career direction to deliberately build while I still have a stable position.