This year has been particularly challenging when it comes to remote work. Across the tech and game industries, layoffs have become the norm rather than the exception. Major companies like Microsoft, Blizzard, Amazon, Apple, and Meta have all reduced staff, signaling a broader shift in how organizations are approaching hiring and long-term investment.
A common narrative floating around is that many companies are betting heavily on AI to replace or significantly reduce technical roles. Public statements from industry leaders, including comments attributed to Eric Schmidt, suggest that traditional programming jobs may shrink dramatically over the next few years. While AI has undoubtedly changed how work gets done, the idea that it will fully replace experienced engineers and technical artists still feels premature. At best, it’s a powerful tool. At worst, it’s being treated as a shortcut to justify shrinking teams for profits.
At the same time, remote opportunities are drying up. One unexpected hurdle I’ve consistently run into is; location. For reasons that remain vague, several companies seem hesitant to hire from Alaska. The explanations vary: distance, time zones, or “compliance.” The time zone argument doesn’t hold much weight, considering Alaska is only an hour off Pacific Time. Compliance concerns are mentioned often, but when pressed for specifics, no one has been able to clearly explain what those issues actually are. Having spoken directly with HR teams in the past, including at Unbroken Studios, I was told that hiring remotely from Alaska can be straightforward and even free. Here are some references: Alaska Labor and SixFifty are a good places to get started.
Rather than waiting things out, I’ve been using this time to expand and diversify my skill set. I’ve been ramping up my C++ work, particularly around exposing systems to Python in Unreal. I’ve also completed coursework in ArcGIS to explore GIS-related opportunities closer to home. On the creative and technical side, I’ve been diving deeper into procedural workflows using Blender and Geometry Nodes, and I’ve started learning Revit to open doors into architectural and drafting-oriented roles. Running a couple of other community websites.
Outside of tech, I’ve kept busy with hands-on construction and handyman projects. It’s been a practical way to generate some income, stay active, and make sure the mortgage gets paid without burning through savings too quickly. While it’s not where I expected to be at this point, it’s been grounding in its own way.
The market is clearly shifting, and adaptability feels more important than ever. For now, the focus is on staying sharp, learning new tools, and keeping momentum moving forward... one step at a time.
