About Oleg Ghimp
I am the technical owner you work with.
I founded Phothor to take direct responsibility for live systems: understand their history, protect customer and revenue paths, restore releases, and keep making careful changes.
Production-ownership biography
My experience follows failures across boundaries.
I have built, inherited, stabilized, and carried forward SaaS, mobile, data, media, communications, payments, and operational products—often through unfamiliar code, incidents, repairs, jobs, billing, cloud, and releases.
Production problems rarely respect a framework or org chart. A visible failure can cross a screen, API, queue, callback, database, job, and deployment. My job is to make that path understandable and owned.
I work from Chișinău, Moldova. Working hours, incident expectations, and access boundaries are agreed during onboarding. The retainer is hands-on ownership, not a 24/7 operations center or an advisory report.
Entering an unfamiliar product
Evidence before confidence. Ownership through verification.
- 01
Learn the domain
I reconstruct what the product means to customers and the business before changing the paths they depend on. - 02
Trace the system
I follow critical journeys across application code, data, jobs, integrations, infrastructure, and releases. - 03
Make risk visible
Unknowns become an access map, a prioritized risk view, explicit decisions, and a release plan. - 04
Stay for the result
I implement, release, verify, document, and keep the founder informed instead of stopping at a recommendation.
Company control
The product should become less dependent on me over time.
Work happens in company-controlled repositories and accounts wherever practical. The company keeps its code, infrastructure, documentation, and operating knowledge. If a permanent CTO or senior engineer is the right long-term answer, I can stabilize the product, document the context, and hand over cleanly.
Review selected production workTalk to Oleg directly