Skip to content
← Back to writing

August 3, 2025

Laid off. Time to build.

Getting laid off from a Senior TPM job in July 2025, moving back in with my parents, and deciding to run the job hunt and build HomelabARR in parallel.

Thursday

HomelabARR as the Wayback Machine captured it on July 11, 2025 — the project sitting there waiting to become the second track.

The meeting invite had no agenda. Just a title: "Quick Sync," 15 minutes, my manager and someone from HR.

I knew before I joined the call. My last performance review was strong, my teams were delivering, and my dashboards were saving leadership hours of reporting every week, so it wasn't about my work, it was the timing.

The call lasted eight minutes. Terminated, effective immediately. They'd mail the paperwork, and my access would be revoked within the hour. That was the end of a career I'd spent about a decade building.

The job I lost

I want you to understand what I was doing, so you understand what was lost.

I was a Senior Technical Program Manager at Neptune Technology Group, a subsidiary of a multi-billion-dollar industrial technology company. I managed twelve Scrum teams working on IoT water metering infrastructure: connected devices, cloud telemetry, data analytics. Serious work for a company that supplies utilities across the country.

I oversaw roughly a million dollars a month in AWS spend. On a given sprint, 800-plus Jira issues moved across my boards. I tracked velocity, managed dependencies between teams, forecasted delivery timelines, and reported to VP-level leadership.

Before Neptune, I was at Healthcare Integrations managing a SaaS product portfolio. Before that, G5 TEK doing networking deployments across six states. I hold a PSM I, CSPO, and SAFe 6 Agilist. I read PMBOK for fun.

I wasn't coasting. The dashboards I built became the template other PMs used. The release process I designed cut cycle time by 40%. I named a major initiative Project Phoenix after The Phoenix Project, bought the team copies on Audible, and we ran a Discord listen party to discuss it, and that's the person they let go.

The aftermath

The first week was shock. My routine was gone. For years I'd woken up, checked Jira, run standups, and managed sprints. Now I woke up to nothing.

I moved in with my parents in Georgia. Me and my kid, back in the house I grew up in. I had some savings, so I started doing the math: what I had divided by monthly expenses, and the number was not encouraging.

By the second week the shock was wearing off and the math was coming into focus. Savings I was burning through, a kid to take care of, and a resume that needed a rewrite. By the third week the question had changed from "what happened to me?" to "what am I going to do now?"

The job hunt

Everyone in my life said the same thing: update your resume, get on LinkedIn, start applying. You have great experience, you'll land something in a few months.

They were right, and I'm doing it. The LinkedIn came back up that same week, the resume went out to recruiters, and the interview prep started. A Senior TPM with my certifications and a decade of shipping enterprise software can find a job, it just takes time. The market's tight, explaining a termination is never easy, and a recruiter told me to expect 200 applications per offer. That's the math, and I'm running it. I want a corporate TPM or senior PM role, and I'm good at that work and I miss it.

Here's the part I didn't expect. I can't fill eight hours a day rewriting cover letters for companies I barely remember applying to. Three to six months of calendar time is a long stretch to sit through waiting. The application grind is necessary, but it isn't a full-time job, and treating it like one was going to break me before the first onsite.

So the job search had to be one track, and I needed a second track to survive the wait.

The second track

The second track was building.

I had a homelab full of servers, a decade of PM experience, and a community of homelabbers who knew me. I had AI tools that were getting better every month. And I had a long habit of building systems.

So I'd build in parallel with the job hunt, not instead of it. Mornings and afternoons for applications, recruiter calls, interview prep, and Coursera classes to keep my AI and cloud skills sharp. Nights and weekends for Docker Compose configs, backend code, and turning HomelabARR into something real from my parents' house with a Mac Mini and a server rack.

Either track landing first was a win. A corporate TPM offer would mean going back to work I love and am good at. An indie product getting traction would mean revenue coming in while I kept interviewing. I didn't have to pick. I had to survive until one of them hit, and keep my skills sharp in both directions.

Day one

I opened a terminal and started writing Docker Compose configs for HomelabARR. Not because it was the best business idea, but because it was the thing I knew best and could start building immediately, while the job applications went out in parallel.

There was no launch plan, no business model canvas, no competitive analysis. There was a problem I'd lived with for years, a community that shared it, and tools that let me build a solution even though I couldn't write a line of code six months earlier.

I told my parents what I was doing. They were supportive in the way parents are when they're worried but don't want to say it. "That sounds interesting, honey." Translation: please have a backup plan. The backup plan is the job hunt, and I told them that too.

I told Chloe I was going to be home more and applying to new jobs, and she said "cool" and went back to her game.

I started building, and I kept applying, both tracks at the same time, starting today.

If you're hiring a Senior TPM or Program Lead who can run twelve Scrum teams, ship products solo with AI agents, and talk to both engineers and executives, reach out. [email protected].

mjashley.com