[{"data":1,"prerenderedAt":191},["ShallowReactive",2],{"navigation":3,"/blog/my-experience-as-a-junior-software-engineer":14,"/blog/my-experience-as-a-junior-software-engineer-surround":189},[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":10,"author":16,"body":20,"date":180,"description":181,"extension":182,"image":183,"meta":184,"minRead":185,"navigation":186,"path":11,"seo":187,"stem":12,"__hash__":188},"blog/blog/my-experience-as-a-junior-software-engineer.md",{"name":17,"avatar":18},"Aaron Bartolome",{"src":19,"alt":17},"/profile/my-pic.webp",{"type":21,"value":22,"toc":170},"minimark",[23,28,32,36,44,66,69,73,80,85,96,99,103,110,117,121,124,132,135,146,149,153,156,167],[24,25,27],"h2",{"id":26},"introduction","Introduction",[29,30,31],"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.",[24,33,35],{"id":34},"my-role-and-tech-stack","My Role and Tech Stack",[29,37,38,39,43],{},"In my role, I mostly work on ",[40,41,42],"strong",{},"frontend development"," using:",[45,46,47,54,60],"ul",{},[48,49,50,53],"li",{},[40,51,52],{},"Nuxt.js"," - Progressive Vue framework",[48,55,56,59],{},[40,57,58],{},"Tailwind CSS"," - Utility-first styling",[48,61,62,65],{},[40,63,64],{},"API integrations"," - Backend communication",[29,67,68],{},"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.",[24,70,72],{"id":71},"biggest-challenges","Biggest Challenges",[29,74,75,76,79],{},"One of the hardest parts of my first year was dealing with ",[40,77,78],{},"confidence and imposter syndrome",". There were moments when I felt like I wasn't good enough or that I was always behind.",[29,81,82],{},[40,83,84],{},"Key struggles:",[45,86,87,90,93],{},[48,88,89],{},"Task estimation (often underestimating timelines)",[48,91,92],{},"Handling unexpected issues and requirement changes",[48,94,95],{},"Keeping up with fast-paced development cycles",[29,97,98],{},"Fast-paced development made all of this even more challenging, but it also accelerated my growth.",[24,100,102],{"id":101},"biggest-lesson-learned","Biggest Lesson Learned",[29,104,105,106,109],{},"The biggest lesson I learned is to ",[40,107,108],{},"always anticipate changes"," from product owners and stakeholders. Requirements can change at any time, and being flexible is part of the job.",[29,111,112,113,116],{},"I also learned the importance of ",[40,114,115],{},"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.",[24,118,120],{"id":119},"advice-to-fresh-graduates","Advice to Fresh Graduates",[29,122,123],{},"If I could give one piece of advice to fresh graduates or my past self, it would be this:",[125,126,127],"blockquote",{},[29,128,129],{},[40,130,131],{},"Don't be afraid to ask questions and always stay curious.",[29,133,134],{},"Take time to understand:",[45,136,137,140,143],{},[48,138,139],{},"The project structure",[48,141,142],{},"The product vision",[48,144,145],{},"The goals of the team",[29,147,148],{},"Asking questions is not a weakness—it's part of learning and growing as an engineer.",[24,150,152],{"id":151},"looking-ahead","Looking Ahead",[29,154,155],{},"Looking back, my first year wasn't about being perfect or knowing everything. It was about:",[45,157,158,161,164],{},[48,159,160],{},"Learning how to adapt",[48,162,163],{},"Improving little by little",[48,165,166],{},"Becoming more comfortable with uncertainty",[29,168,169],{},"I still have a lot to learn, but I'm optimistic about the journey ahead and excited for what's next.",{"title":171,"searchDepth":172,"depth":172,"links":173},"",2,[174,175,176,177,178,179],{"id":26,"depth":172,"text":27},{"id":34,"depth":172,"text":35},{"id":71,"depth":172,"text":72},{"id":101,"depth":172,"text":102},{"id":119,"depth":172,"text":120},{"id":151,"depth":172,"text":152},"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,true,{"title":10,"description":181},"ivldgQUhxzEMtNzYrdNgU4d2DypoeBaNGSkOS6XuXgk",[190,190],null,1782865071013]