[{"data":1,"prerenderedAt":199},["ShallowReactive",2],{"navigation":3,"blog-page":14,"blogs":24},[4],{"title":5,"path":6,"stem":7,"children":8,"page":13},"Blog","/blog","blog",[9],{"title":10,"path":11,"stem":12},"My Experience as a Junior Software Engineer (First Year)","/blog/my-experience-as-a-junior-software-engineer","blog/my-experience-as-a-junior-software-engineer",false,{"id":15,"title":16,"body":17,"description":18,"extension":19,"links":17,"meta":20,"navigation":21,"path":6,"seo":22,"stem":7,"__hash__":23},"pages/blog.yml","Latest Articles",null,"Sharing my experiences, insights, and practical guides to help fellow developers navigate the tech industry.","yml",{},true,{"title":16,"description":18},"QYa_wGFX0h1c3osMxrqHPsFEOaQ-EGCpXb64BltyJao",[25],{"id":26,"title":10,"author":27,"body":31,"date":191,"description":192,"extension":193,"image":194,"meta":195,"minRead":196,"navigation":21,"path":11,"seo":197,"stem":12,"__hash__":198},"blog/blog/my-experience-as-a-junior-software-engineer.md",{"name":28,"avatar":29},"Aaron Bartolome",{"src":30,"alt":28},"/profile/my-pic.webp",{"type":32,"value":33,"toc":181},"minimark",[34,39,43,47,55,77,80,84,91,96,107,110,114,121,128,132,135,143,146,157,160,164,167,178],[35,36,38],"h2",{"id":37},"introduction","Introduction",[40,41,42],"p",{},"My first year as a Junior Software Engineer has been a mix of excitement, pressure, and a lot of learning. As a fresh graduate stepping into a fast-paced environment, I quickly realized that real-world development is very different from what I experienced in school.",[35,44,46],{"id":45},"my-role-and-tech-stack","My Role and Tech Stack",[40,48,49,50,54],{},"In my role, I mostly work on ",[51,52,53],"strong",{},"frontend development"," using:",[56,57,58,65,71],"ul",{},[59,60,61,64],"li",{},[51,62,63],{},"Nuxt.js"," - Progressive Vue framework",[59,66,67,70],{},[51,68,69],{},"Tailwind CSS"," - Utility-first styling",[59,72,73,76],{},[51,74,75],{},"API integrations"," - Backend communication",[40,78,79],{},"A big part of my job involves improving existing websites and building features based on business requirements. While the tech stack itself was exciting, adjusting to the pace and expectations of a real product team was the real challenge.",[35,81,83],{"id":82},"biggest-challenges","Biggest Challenges",[40,85,86,87,90],{},"One of the hardest parts of my first year was dealing with ",[51,88,89],{},"confidence and imposter syndrome",". There were moments when I felt like I wasn't good enough or that I was always behind.",[40,92,93],{},[51,94,95],{},"Key struggles:",[56,97,98,101,104],{},[59,99,100],{},"Task estimation (often underestimating timelines)",[59,102,103],{},"Handling unexpected issues and requirement changes",[59,105,106],{},"Keeping up with fast-paced development cycles",[40,108,109],{},"Fast-paced development made all of this even more challenging, but it also accelerated my growth.",[35,111,113],{"id":112},"biggest-lesson-learned","Biggest Lesson Learned",[40,115,116,117,120],{},"The biggest lesson I learned is to ",[51,118,119],{},"always anticipate changes"," from product owners and stakeholders. Requirements can change at any time, and being flexible is part of the job.",[40,122,123,124,127],{},"I also learned the importance of ",[51,125,126],{},"unit testing my work",", even when there are QAs in the team. Testing helps catch issues early and gives me more confidence in the code I ship.",[35,129,131],{"id":130},"advice-to-fresh-graduates","Advice to Fresh Graduates",[40,133,134],{},"If I could give one piece of advice to fresh graduates or my past self, it would be this:",[136,137,138],"blockquote",{},[40,139,140],{},[51,141,142],{},"Don't be afraid to ask questions and always stay curious.",[40,144,145],{},"Take time to understand:",[56,147,148,151,154],{},[59,149,150],{},"The project structure",[59,152,153],{},"The product vision",[59,155,156],{},"The goals of the team",[40,158,159],{},"Asking questions is not a weakness—it's part of learning and growing as an engineer.",[35,161,163],{"id":162},"looking-ahead","Looking Ahead",[40,165,166],{},"Looking back, my first year wasn't about being perfect or knowing everything. It was about:",[56,168,169,172,175],{},[59,170,171],{},"Learning how to adapt",[59,173,174],{},"Improving little by little",[59,176,177],{},"Becoming more comfortable with uncertainty",[40,179,180],{},"I still have a lot to learn, but I'm optimistic about the journey ahead and excited for what's next.",{"title":182,"searchDepth":183,"depth":183,"links":184},"",2,[185,186,187,188,189,190],{"id":37,"depth":183,"text":38},{"id":45,"depth":183,"text":46},{"id":82,"depth":183,"text":83},{"id":112,"depth":183,"text":113},{"id":130,"depth":183,"text":131},{"id":162,"depth":183,"text":163},"2026-01-20T00:00:00.000Z","A short reflection on my first year as a Junior Software Engineer, covering the challenges, lessons, and growth I experienced while working in a fast-paced development environment.","md","/first-year-as-a-jr-swe.jpg",{},5,{"title":10,"description":192},"ivldgQUhxzEMtNzYrdNgU4d2DypoeBaNGSkOS6XuXgk",1782865071012]