Applying for a Backend Junior Position at 30: How Should I Structure My Portfolio?
I'm a non-CS major who completed a government-sponsored bootcamp and am now applying for my first job at 30. I built a simple shopping mall project using Spring Boot, but I feel it's not enough. I'm planning to actively post TIL on GitHub, but what else is currently required in the junior hiring market? Should I also study AWS or Docker?
8 answers
Starting at 30 is not too late at all. Even a single shopping mall project can be enough to make an impression. However, I recommend diving deeper into that project. For example, implementing edge cases like order cancellations or inventory management, and adding test code will make it look much better. Even just knowing the basics of AWS or Docker will be a plus in interviews.
I also got a job through a government-funded program at a similar age. When it comes to portfolios, quality matters more than quantity. Try deploying a shopping mall project on AWS and setting up a simple CI/CD pipeline. Also, posting TIL on GitHub is a really good habit. I talked a lot about my tech stack during interviews based on my TIL entries.
If you're a non-major at 30, you're probably anxious about your age, right? I felt the same way, but honestly, as long as you have the skills, it's fine. It's important to apply with just one shopping mall project, and at the interview, be honest about your shortcomings and show a willingness to learn. You only need to know how to deploy on AWS EC2, and you can learn Docker later at the company.
Does your shopping mall project include basic features like JWT login or pagination? These days, even junior developers are expected to know REST API design and exception handling. While it's good to consistently post TILs, organizing your project code with comments and a well-written README will be more helpful. If you have experience with AWS services like S3 or RDS, you'll have more to talk about in interviews.
At 30, it's actually a great age to start as a junior rather than switching to a senior role! I started at 29 myself, and I emphasized 'problem-solving processes' in my portfolio. For example, how I handled concurrency issues in a shopping mall project. You don't need to know Docker, but make sure to include deployment experience with AWS, even if it's just using the free tier.
If this is your first challenge after completing a government-funded course, prepare by refactoring a shopping mall project so you can explain 'why you designed it this way.' In today's junior job market, employers look more at performance considerations and error handling than basic CRUD. I've seen cases where knowing just AWS EC2, RDS, and basic Docker commands was enough to pass. Keep posting your TIL (Today I Learned) entries, as they demonstrate consistency.
Wow, starting at 30 is impressive! I'm in a similar situation, and I've found it helpful to note 'areas for improvement' or 'things to enhance next time' in your portfolio. Interviewers look for growth potential. Even just one AWS deployment experience can set you apart, and Docker is optional. Posting even one line of TIL on GitHub daily becomes a huge asset later on.
If you built a shopping mall project with Spring Boot, try adding unit tests and integration tests to it. These days, many companies expect even junior developers to write test code. Deploying on AWS EC2 and connecting to RDS alone can make your portfolio stand out significantly. As for Docker, you can learn it later when you join a company, so for now, focus on improving the completeness of your project.