After Atlassian and CleverTap, I had to confront the market honestly. Hiring is hard, timelines can stretch 12 to 18 months, and AI plus automation are already reshaping team structures.
Between roles, I burned myself out trying to win the hiring game: full days on LinkedIn, endless resume rewrites, ATS optimization, and highly personalized applications.
It became a full-time job trying to get a job. I eventually secured a role with a more senior title but lower financial outcomes than my previous position. That forced reflection.
This Time, the Approach Is Different
I am applying with intention for architecture and system design roles. At the same time, I am building. Hubsays Studio is not me trying to cosplay as a startup founder. It is my systems lab.
Inside that lab I test AI workflows, evaluate SaaS tools, simulate onboarding systems, and explore automation architecture.
Why Game Development Belongs Here
I am also exploring game development. At first glance that seems unrelated to Solutions Architecture or Customer Success. In practice, it is deeply transferable.
If a player drops after level one, that is an onboarding failure. You must analyze behavior, reduce friction, test changes, gather feedback, and iterate. That is no different from SaaS onboarding.
Game design also forces systems thinking: what triggers next, what breaks when one variable changes, and how loops behave over time. Those are the same questions I use in workflow design.
It also builds commercial muscles: distribution, pricing strategy, funnels, community feedback, and retention loops.
What This Signals to Hiring Teams
- I do not wait passively in hard markets.
- I level up continuously.
- I think in systems across domains.
- I test ideas instead of theorizing.
That is the crossroads.