AF/HY
The program

A story in three acts.

Act I 2021 – 2022

Sound was my first network.

  • Sound engineering is signal, timing, and the network it rides on.A diploma in sound engineering and a Dante certification for audio over IP: by the time I walked into a cinema chain, the sound was already a network.
  • A cinema chain is the biggest AV-over-IP system most people ever sit in.Projectors, cinema servers, sound processors and about 400 signage screens across twelve sites, all on the network. That is the room I walked into.
  • What I brought: the chain's sound.Calibrating the auditoriums, 5.1 and 7.1, and setting up the sound systems for new ones. The ear that tunes a room is rare. In IT it is almost unheard of.
  • In parallel, a recording studio in Tel Aviv.Managing and operating recording sessions. Two live rooms, and neither waits.
  • Signal first, then the whole estate.The projection network, the servers behind the screens, then every system the chain runs on. That is Act II.

Act II 2022 – today

Twelve sites. One network. A team of three.

  • IT Infrastructure & Technology Operations Specialist, Hot Cinema: ten cinemas, HQ and an events venue, run by a team of three.
  • About 400 devices and 20–30 servers on three segmented networks per site (projection, office, point of sale), joined site to site.
  • Identity and access: Microsoft 365, Entra ID, Active Directory, Conditional Access, MFA.
  • Security: a FortiGate at every site with VDOM and VLANs at HQ, CrowdStrike EDR, Action1 patching, Cloudflare Zero Trust, phishing simulations.
  • Audited every four to six months, SOX / ITGC and external security audits, and I take part in the remediation across the estate.

Act II, scene 2 The list

Regulation sets the list. I build the way through.

  • The sales platform ran on local servers and end-of-life systems.So it moved to the cloud: 400 terminals re-imaged across 12 sites, and nothing stopped selling.
  • Every endpoint had to leave its end-of-life system at once, and an upgrade can lose the programs a cinema runs on.So I built the upgrade automation: the right image for each machine, a silent upgrade that loses nothing, the unneeded apps stripped, the machine locked down. Two rule sets: an employee PC and a point of sale are not the same machine.
  • A room of physical servers, one box per job, each with its own problems.So the company servers went virtual: one place to maintain instead of tens of boxes, with backups that go back weeks and a disaster-recovery copy.
  • HQ was one flat network: printers, cameras and every computer together.So it was split into VLANs with explicit rules for each, and every machine is registered: plug in an unknown computer and it gets no address until it is onboarded.
  • Every audit and penetration test comes back with a list.So the list gets worked: MFA everywhere, domain rules and group policy, hosts upgraded, 2007-era servers gone, and the old endpoint protection replaced by CrowdStrike, which catches what used to slip through. If someone manages it properly. That's me.

Act III 2024 – today

Then I built a marketplace.

  • PERFIX: an on-demand home-services app (plumbers, electricians, AC technicians), live on iOS and Android.
  • Thousands of users signed up, customers and service providers, across dozens of towns, and hundreds of job requests came through the app.
  • Repeat customers from the first months: people came back for a second job.
  • The cost of a request in ads held flat as I more than doubled the spend: demand was there, money was the limit.
  • Founder and product manager: I write the spec an external dev team builds against, from the data model and job flow to the pricing engine and payments.

Act III, scene 2 The rebuild

Every weak point became part of the design.

  • The deal left the app with the first chat.So PERFIX became the seller: the customer pays one price, and PERFIX pays the provider.
  • Customers wrote "it doesn't work", and nobody can price that.So jobs now come from a catalog of standard work, priced before anyone arrives.
  • I was the matching system, by hand.So matching is a system now, gated by each provider's reliability on recent jobs.
  • More deals died on reaching each other than on price.So customer and provider talk in the app, without ever swapping numbers.
  • "Everything included" starts arguments.So every job gets a written scope, and an open dispute pauses the payout.

Behind the scenes Command Desk

One control room, one loop: wireframe, design, build, test, fix.

  • The wireframes are the spec.Every screen of both apps and the admin console is drawn first and handed to the designer as a brief, each frame with its own ID.
  • The designer's delivery is checked frame by frame.A script matches every delivered screen to its wireframe and compares the texts, the controls and the links. The designer gets a ranked fix list, with the notes placed on the frames in Figma.
  • The design becomes the source of truth, and the build is tested against it.Each release goes into two emulators; a driver steps through both apps and screenshots every step; every designed screen is marked built, built differently, dummy or missing.
  • The fixes go back where each person works.Jira tickets generated from the findings for the developers, fix notes in Figma for the designer, and one page with every link live.
  • The machine recommends. I confirm.Nothing ships on the machine's word alone. I built this while the product was being built, because the designer, the developers and I never sit in the same room.

End of reel one

Product manager: where all three meet.

The booth · The network · The product

Now showing

Ahmad Fareed

Haj Yahya

in The Booth · The Network · The Product

Skip to the program

The ProgramSeason 2026 · ahmadfareed.com

Ahmad Fareed Haj Yahya

Keeps a twelve-site cinema chain's IT and security running, through every major switchover. Founder and product manager of PERFIX, a home-services marketplace with thousands of users across dozens of towns.

Tel Aviv area, Israel · Arabic, Hebrew, English

Now playing

2022 — today

IT Infrastructure & Technology Operations Specialist

Hot Cinema · ten cinemas, HQ and an events venue

  • Runs the estate in a team of three: about 400 devices and 20–30 servers on three segmented networks per site, joined site to site.
  • Ran the technical side of moving the sales platform from local servers to the cloud: about 400 point-of-sale terminals re-imaged and redeployed across 12 sites, with no downtime.
  • Built the endpoint upgrade automation that moved every PC and terminal off end-of-life systems silently, without losing data or programs.
  • Moved the company servers (file servers, Active Directory and the rest) to virtualization (VMware ESXi, Hyper-V, Veeam), with minimal downtime; backups with weeks of retention and a disaster-recovery copy.
  • Identity and Microsoft 365: Entra ID, Active Directory, Group Policy, Conditional Access, MFA.
  • Security: a FortiGate per site (VDOM and VLANs at HQ), CrowdStrike EDR, Action1 patching, Cloudflare Zero Trust, phishing simulations.
  • Audited every four to six months (SOX / ITGC, external security audits, penetration tests); works the remediation lists.
  • Building out a new cinema now: network, point of sale and projection.

2024 — today

Founder & Product Manager

PERFIX · on-demand home-services marketplace, live on iOS and Android

  • Hundreds of job requests from thousands of users (customers and service providers) across dozens of towns; repeat customers from the first months.
  • Writes the product spec an external dev team builds against: data model, job flow, pricing engine, payments.
  • The cost of a request in ads held flat as spend more than doubled; shut down the channel that didn't pay back.
  • Turned the first version's weak points into the rebuild's design (below). The rebuild is underway.
  • 220 wireframe screens in Figma, including a 31-screen admin console, and a 1,200-page bilingual provider directory.

What the estate couldn't do and what it does now

The sales platform ran on local servers and end-of-life operating systems, at every site.
It moved to a cloud platform. About 400 terminals were re-imaged and redeployed across 12 sites, and the cinemas kept selling throughout.
Security regulation said every endpoint had to leave its end-of-life system at once, and an upgrade can lose data, programs and the special programs a cinema runs on.
I built an upgrade automation that runs on each machine: it fetches the right Microsoft image for that specific endpoint, upgrades silently without losing anything, then strips the apps Microsoft pushes in, applies the group policies and locks the machine down. Two rule sets: an employee PC and a point of sale are not the same machine. The upgrade is the easy part; keeping every program and every file is the job.
A full room of physical servers, one box per job, with constant issues across tens of machines.
The company servers went virtual, on our own hosts. One place to maintain instead of tens of boxes, with backups that go back weeks and a disaster-recovery copy.
HQ was one flat network: printers, cameras, endpoints, everything together.
It was split into VLANs with explicit rules for each, where it may go and where it may not, and every computer is registered by its hardware address. Plug an unknown machine into a switch and it gets no address until it is onboarded.
The old endpoint protection let things slip through.
The estate moved to CrowdStrike, and what used to slip through gets caught straight away. A strong product, but only if someone manages it properly. That's me.
Every audit and penetration test comes back with a list.
MFA everywhere, domain rules and group policy, the virtualization hosts upgraded, the right backup retention, 2007-era servers replaced with ones that aren't end of life. Regulation sets the list; the job is to get through it in the fewest steps, on many machines at once, without losing anything. Generic tools rarely fit a cinema chain, so I build the company-specific one.

What the first version taught and what the rebuild does about it

The deal left the app after the first chat.
PERFIX became the seller: one price to the customer, and PERFIX pays the provider. A seller can guarantee the job; a middleman can only apologise.
Customers wrote "it doesn't work", and nobody can price that.
A catalog of standard jobs: the provider names the work, PERFIX sets one price before anyone arrives, and an unclear job starts with a paid diagnosis visit.
I was the matching system, by hand.
Matching runs on a reliability score built from each provider's recent jobs. Star ratings feed it, but nobody is ranked on an average of stars.
More deals died on reaching each other than on price.
In-app chat and masked calls during the job: they can talk, but neither ever sees the other's number.
"Everything included" starts arguments.
A written scope of what is in and out, and an open dispute pauses the provider's payout until it is settled.
People paid cash, one deal at a time.
Card payments and installments. The goal isn't cheaper, it's payable.
The busiest category was the worst served.
The plan's first technician is an appliance specialist on the payroll: quick fixes by PERFIX's own people, licensed work and projects by vetted partners.

Earlier how it started

Projection & sound · Hot Cinema, 2021–2022. Dante-certified audio over IP. Ran the projection and calibrated the chain's auditoriums (5.1 and 7.1), set up the sound systems for new auditoriums, then the technical team, which at a cinema chain is also the IT team. Christie projectors, Dolby cinema servers and sound processors, about 400 digital-signage screens and the video walls.

Sound engineer · Porti Records, Tel Aviv, 2021–2022. Managed and operated recording sessions, in parallel with the cinema.

The cast tools and skills

Identity & Microsoft 365
Microsoft 365 · Exchange Online · Entra ID · Active Directory · Group Policy · Conditional Access · MFA (FortiToken)
Security
FortiGate (VDOM, VLANs, policies) · CrowdStrike EDR · Action1 · Cloudflare Zero Trust · phishing simulations · audit remediation
Network
VLANs · site-to-site and remote VPN · DNS · DHCP · TCP/IP · Wi-Fi with Ekahau site surveys
Infrastructure
Windows Server · VMware ESXi · Hyper-V · Veeam · Acronis · QNAP · backup and disaster recovery
Cinema & retail tech
~400 POS terminals · Christie · Dolby · Screenwriter TMS · Samsung MagicINFO · video walls · event streaming
Product
PRDs and specs · user flows · Figma and FigJam · wireframes · funnel instrumentation · unit economics · GA4 · Meta Ads · Jira · Notion
Cloud & build
Cloudflare (Pages, Workers, Tunnels, Access, WAF) · AWS · Firebase / Firestore · MongoDB Atlas · Tranzila payments · InforU SMS · Codemagic · TestFlight
Automation & scripting
PowerShell · Bash · Python · SQL · n8n (~63 workflows) · Git · Postman · REST
AI systems
Retrieval over private documents · multi-agent pipelines · local open-weight models · prompt and cost governance · Claude and Claude Code

Behind the scenes Command Desk, the control room I built

Command Desk is an operations control room, web and mobile, shipped to TestFlight on every push. It reads my notes and the live design files, drives the testing, holds the tasks, and routes each piece of work to the AI session that already knows the context. Around it runs one loop that keeps the designer, the developers and me on one truth. I built it, nights and weekends, while the product was being built.

1 · Wireframe
Every screen of the customer app, the provider app and the admin console is drawn before the designer starts, and handed over as a brief with every frame's ID. Every wireframe and every designer frame is extracted into a searchable catalog, refreshed daily, so a question about the design is answered in seconds.
2 · Design check
When the designer delivers, a script parses both Figma files into screen inventories, matches every screen to its wireframe and compares every visible text, control and link (headings, actions, table values, money amounts). The designer gets a ranked fix list (high, medium, low) and the fix notes are placed on the frames themselves. Last round: 84 findings on 46 screens, down from 162 on 38 the round before.
3 · Handoff
The developers get one page: a clickable prototype of the admin console (98 screens, 4,097 live links, nothing dangling, 42 operator-task tours), a 431-page developer guide with one section per screen (purpose, data, formulas, controls, rules, states), a formulas sheet, a navigation map of every click on every screen (2,263 rows), and 63 Jira tickets generated from it, each linked to its screen and its guide section.
4 · Build test
Each release goes into two fresh emulators. A driver steps through both apps and screenshots every step, with read-only peeks into the database and the admin console behind each one. Every designed screen (134 customer, 127 provider, 91 admin) is marked built as designed, built differently, dummy or missing, with its screenshot. The register and a slide deck built from it run the meeting with the dev team. A separate QA agent can be pointed at any app, web or Android, and reports what is broken and what is missing, ranked, with evidence. "Inconclusive" is never a pass.
5 · Fix
The findings go back where each person works: Jira tickets for the developers, fix notes in Figma for the designer, and the catalog itself goes live from a spreadsheet (12 trades, 124 subcategories, 188 priced units of work), checked and applied to the live database by a script, each icon approved on a Figma board before it enters the app.
The one law
The machine recommends; I confirm. Every automated step ends at a gate where I say yes. Behind the desk: a private search engine over my notes, specs and books on my own hardware, a multi-agent pipeline with each agent limited to the tools it needs, and open-weight models on my own GPU. Built with AI-assisted development: I design the system, set the rules and run it.

Credits

  • Sound Engineering Diploma Ariel University, 2021
  • Microsoft infrastructure & networking programme, MCSA curriculum John Bryce, 2023
  • Dante Level 1, audio over IP Audinate, 2021