Let's talk ↗
← All posts
Nov 1, 2025 · 15 min read

My Career Journey: From Intern to Mid-Level Engineer

A reflection on my path through the tech industry, the lessons learned, and advice for aspiring developers.

#career#growth#advice
--

Looking back at my journey from a curious intern to a mid-level software engineer, I'm reminded of how each role, project, and challenge shaped not just my technical skills, but my approach to problem-solving and collaboration. Here's my story.

The beginning: Sprobe Inc.

June 2022 — August 2022

My journey started as an intern at Sprobe Inc. in Cebu Business Park. Still attending university, I was eager to apply what I'd learned in theory to real-world problems. The experience was transformative — I helped build an internal platform from the ground up, implementing features across the full stack.

Key takeaway

The importance of documentation. Creating ERDs, HLDs, and LLDs wasn't just busywork — it taught me to think systematically about architecture before diving into code.

Growth: Alliance Software Inc.

July 2023 — August 2025

At Alliance, I had the opportunity to work on multiple projects for a major airline company in the Philippines. Starting as a Technical Specialist I, I contributed to an Agile Scrum team, developing features that directly impacted employees and customers of the airline company.

SharePoint migration
Migrated an Angular master page from SharePoint 2016 to SharePoint Online — a lesson in careful planning and incremental migration.
Security & maintenance
Production support, critical bug fixes, and security fixes from Checkmarx and Qualys findings.
Modernization
Upgraded Angular apps and rebuilt a .NET API into a more scalable Node.js + Express service.

As I progressed and got promoted to Associate Technical Specialist (two levels up from my previous role), my responsibilities expanded. I started getting assigned to projects where I was the sole developer — a great opportunity to learn how to work independently and manage my time effectively.

Managing multiple airline booking websites simultaneously taught me the art of context-switching and prioritization. In a fast-paced environment, you learn to balance urgent production issues with long-term improvements.

Acceleration: Winedrops

August 2025 — November 2025

My time at Winedrops was a masterclass in startup velocity. Coming from more structured environments, stepping into my first true startup was a bit of a culture shock — everything moved fast, decisions were quick, and priorities shifted daily. I joined as a Senior Full Stack Engineer, which was a big leap from my previous role at Alliance.

I truly believe I wasn't fully ready for this level yet, but I dove in anyway and embraced the challenge. Even though my stay was brief, I quickly adapted to the intense pace of iteration, shipping features across two Next.js web applications and a mobile app.

Working with React Native was a new challenge. Mobile development requires a different mindset — touch interactions, performance constraints, and platform-specific patterns — and every release goes through an app store review cycle that can take days.

Eventually, I chose to move on — not because I couldn't handle the pressure, but because I had a different vision for the path I wanted to take as a dev. You never truly know what you're capable of until you try.

Lessons learned

  1. 01Documentation mattersGood docs save hours of debugging and onboarding time.
  2. 02Security is everyone's responsibilityRegular scanning and proactive fixes prevent costly breaches.
  3. 03Modernization is worth the effortLegacy code can be a drag, but thoughtful refactoring pays dividends.
  4. 04User feedback is goldDirect interaction with support escalations provides insights you can't get from metrics alone.
  5. 05Context-switching is a skillManaging multiple projects teaches you to prioritize and focus.

Advice for aspiring developers

  1. 01Start with fundamentalsDon't rush to frameworks. Understanding JavaScript, HTML, and CSS deeply will make everything else easier.
  2. 02Build real projectsDon't just follow tutorials. Build something you're passionate about, even if it's small.
  3. 03Embrace documentationGet comfortable reading docs and writing your own. It's a superpower.
  4. 04Learn to debugMost of your time will be spent debugging. Get good at it.
  5. 05Stay curiousThe technology landscape changes fast. Keep learning, but don't chase every new trend.
The takeaway

Every seasoned engineer was once a junior. Keep building, keep learning, and most importantly, keep shipping.

Next postVibe Coding vs AI-Assisted Coding
Book a call
patr1ck@dev — zsh
patr1ck.dev shell — type `help` to begin.
❯