A sharp mind that took itself seriously early.
Software, service, writing, teaching, and the close reading of people.
Open to senior engineering roles, partnerships, and product conversations.
01. Foundation
The founding scene. Read once, slowly.
The summer I turned eighteen, I took a temporary job at a luxury resort on the Egyptian North Coast. They put me on the floor of one of the restaurants. Within two weeks the senior staff had started watching me. Within two months they had me leading shifts. By my second season they handed me the entire restaurant operation, something the resort had never done with a temporary employee in its history. Guests began telling me, often and unprompted, that it was the best service they had ever experienced anywhere in the world. They were responding to a combination of things. A fast read of the room. A steady presence. The kind of memory that holds an entire menu in place before the first guest arrives. And the discipline of a person who had quietly studied every ingredient, every step of the sequence of service, every kind of guest who walked through the door. The instinct was already there. The work made it reliable. I have been operating that way ever since, in whatever room I happen to be in.
02. Disciplines
I learned my first real discipline running luxury restaurant floors at Marassi. Anticipation, sequence, presence, the small invisible cues that decide whether someone leaves remembering you. The way I run a meeting now is the way I ran a shift then.
Seven years of production work across clinics, restaurants, retailers, civic platforms, AI-driven consultancy SaaS, and a US premium travel concierge company. I move quickly. I see the whole system before I touch it. I own the work end to end, from spec and frontend through API design, deployment, observability, and analytics. I lead small engineering teams. I ship my own products under my own name.
I read people quickly and I am usually right. Six years of deliberate study on top of an instinct I have had since I was a child. Body language, behavioral psychology, the edges where social science meets criminology. I use this in interviews, in product decisions, in difficult rooms, and in negotiations. It is the quietest skill I have, and the one that changes outcomes the most.
I notice things and I cannot leave them alone. A phenomenon, a trend, an unresolved argument. I pull data, run analysis, write the findings down. None of this is part of any job I have ever had. All of it is part of how I think. The studies live under Field Notes on this site.
Physics, mostly. High school and first-year university students. I never taught a session I had not first re-mastered. The teaching shaped me as much as it shaped them.
I run scenario-based technical interviews that candidates remember years later and that hiring teams trust as signal. I see what someone actually knows under the surface of what they say. I designed the format because the standard one is broken.
Graphic design and video editing since before software became the main work. Essays and notes here on the site. Both are how I think out loud, in different materials.
What people remember.
“I could never enjoy such a perfect communicator in the food industry in the Middle East. He knows exactly what to communicate and how to.”
“Best order taking experience ever. Farahat was extremely educated on the ingredients. I knew exactly what I ordered and could anticipate the full order as it came.”
“Farahat is a wonderful guy. We really never cared about any detail. One of the smartest guys I have ever met.”
“He reviewed the spec like it was a contract and shipped it like it was his own product. I stopped double-checking his work months before I should have.”
“The design session was the first technical interview that made me think instead of perform. I left knowing exactly which parts of my craft were weak, and I fixed them.”
“He explained the physics the way our professor never could. He knew exactly where I was lost before I said a word.”
“He caught the thing everyone else missed. Not from the data. From reading the client.”
“He does not ask what you want to build. He asks what will still be true about the business in two years. Then he builds that.”
“I came to him junior and left the mentorship with a portfolio I was proud to defend. He never gave me answers. He gave me the standard.”
Scroll or drag
04. The path
Hospitality ran in parallel with engineering from 2015 to 2021. The ribbon keeps that second timeline honest. The chapters are the engineering arc.
Parallel. Hospitality.
2015
First season at Marassi. Waiter.
Month two
Trusted to lead shifts.
2016 to 2018
Running full restaurant operations as the only temp ever to be given that responsibility.
2018 to 2021
Continued seasonal service across new venues and roles.
2018 to 2020
Junior developer and database administrator at a small financial office in Tanta. Two years owning the transactional MySQL layer, writing Python for ingestion and transformation, and building small desktop tools in Tkinter and PyQt that operations actually used. Two years that taught me the people who run the business at the end of the day deserve software that respects their time.
Read more2020 to 2022
Full-stack developer at a software house. Worked across clinics, restaurants, retail, point-of-sale, and a clothing brand. The variety of contexts mattered. Each industry has its own assumptions about how software should behave, and I started to see the seams. Two years of learning to talk to operators in their own language and translate it back into a working system.
Read more2022 to 2024
Mid-level full-stack engineer. API-first thinking. Documentation discipline. The chapter where I stopped working on tickets and started owning domains. Reliability became my currency. By the end of these two years I could be handed a tangled service and produce a clear spec, a working refactor, and a deployment plan inside a week.
Read more2024 to present
Senior software engineer and tech lead at a digital consultancy. I lead a four-person team building the firm's main SaaS platform, the agents inside it, and a set of bilingual civic apps that run on top. I own the platform's infrastructure, ecosystem, and integrations. I run in-house consultations on product development cooperations. This is where I started to operate at the architecture level by default.
Read more2025 to present
Senior frontend-focused engineer at a US premium travel concierge company, remote from October City. Four hundred thirty five Jira tickets in my first year, across nine phases of work. I took the public-facing portal from a basic state into a full platform with ten plus major features. I architected and shipped two fully self-owned features: a Notion-style Trips Workspace and the Ascend Analytics dashboard. The year that proved I can land features at the speed and the standard a US startup actually needs.
Read more2018 to 2020
Junior developer and database administrator at a small financial office in Tanta. Two years owning the transactional MySQL layer, writing Python for ingestion and transformation, and building small desktop tools in Tkinter and PyQt that operations actually used. Two years that taught me the people who run the business at the end of the day deserve software that respects their time.
Read more2020 to 2022
Full-stack developer at a software house. Worked across clinics, restaurants, retail, point-of-sale, and a clothing brand. The variety of contexts mattered. Each industry has its own assumptions about how software should behave, and I started to see the seams. Two years of learning to talk to operators in their own language and translate it back into a working system.
Read more2022 to 2024
Mid-level full-stack engineer. API-first thinking. Documentation discipline. The chapter where I stopped working on tickets and started owning domains. Reliability became my currency. By the end of these two years I could be handed a tangled service and produce a clear spec, a working refactor, and a deployment plan inside a week.
Read more2024 to present
Senior software engineer and tech lead at a digital consultancy. I lead a four-person team building the firm's main SaaS platform, the agents inside it, and a set of bilingual civic apps that run on top. I own the platform's infrastructure, ecosystem, and integrations. I run in-house consultations on product development cooperations. This is where I started to operate at the architecture level by default.
Read more2025 to present
Senior frontend-focused engineer at a US premium travel concierge company, remote from October City. Four hundred thirty five Jira tickets in my first year, across nine phases of work. I took the public-facing portal from a basic state into a full platform with ten plus major features. I architected and shipped two fully self-owned features: a Notion-style Trips Workspace and the Ascend Analytics dashboard. The year that proved I can land features at the speed and the standard a US startup actually needs.
Read moreMeanwhile, at Marassi.
Parallel. Hospitality.
2015
First season at Marassi. Waiter.
Month two
Trusted to lead shifts.
2016 to 2018
Running full restaurant operations as the only temp ever to be given that responsibility.
2018 to 2021
Continued seasonal service across new venues and roles.
05. Studio
I build my own products. Most of them formalize a layer that did not have a name yet. Two are in active development. One is shipping into a Shopify-native pilot. The rest are in concept, prepared with the same care. Each one is built on the same conviction. The hidden architecture deserves a home.
Each product has its own page. The concepts are written with the same seriousness as the builds.
06. Signals
Both are being written now. Published here first, when they say something true.
From the writing.
In revision.
Where agents earn their keep, where they break, and what the escalation path owes the human in the loop.
In the pipeline.
On shipping at a premium travel concierge. On owning features end to end. On the interview format that should have been retired a decade ago.
From the field notes.
In preparation.
Deliberate, unfunded research on phenomena that refuse to resolve. First studies land here with data and method.
Coming soon.
The studies publish when the numbers survive their own audit.