01 The Work
Things I have worked on — and what the work actually was.
The titles are useful, but they are not the point. The interesting part is usually the messy middle: taking something ambiguous, making it concrete, and getting enough people aligned to ship it.
-
Avaya Infinity
A large, modern contact-center platform for enterprises. My job is to help turn a lot of moving parts into one product that customers can actually run.
Show more
Avaya Infinity is a cloud-native contact-center platform built for large enterprises. It brings together voice, video, chat, email, workflow, AI, and data into a system that can run in different deployment models.
I lead major parts of the product and platform: core services, digital channels, agent experience, workflow tooling, and the cross-team execution needed to make it feel like one coherent system instead of a pile of features.
-
Facebook Live & Integrity Controls
Two very different problems at very large scale: helping creators get value from Facebook Live, and helping people better control what shows up in their feed.
Show more
I led the Facebook Live Broadcaster Value team. The work was about helping creators understand their audience, grow their reach, and get more value from live video.
Then I led the Facebook Integrity Controls team — the surfaces that let people shape what they see and what they do not want to see. Different product area, same kind of pressure: huge scale, subtle tradeoffs, and decisions that need to make sense to the person using the product.
-
Vonage Business & Programmable Comms
Nine years across the shift from consumer VoIP to business communications, developer APIs, and contact center platforms.
Show more
I started hands-on, building mobile VoIP apps and early WebRTC experiences — at a time when making a reliable call from a browser still felt less obvious than people remember.
Over time I moved into leading engineering across Unified Communications, Programmable Communications, and Contact Center. I also spent a lot of time on the less glamorous systems — billing, provisioning, business support — because that is often where the real product either works or breaks.
02 The Workshop
Smaller things I built or still maintain.
Some are maintained projects. One is old localization work that still explains a lot about how I think about usable software. I also make physical things sometimes, mostly on MakerWorld.
-
★ Open source · maintained project
Vibe
A simple idea I keep coming back to: if AI can build small apps for people, those apps should be as easy to share as documents.
Show more
AI can generate a small app in minutes. Then reality shows up: Node versions, Docker, Homebrew, terminals, dependencies, signing, trust. Vibe is my attempt to remove that gap. The app ships as one
.vibeappfile, and the recipient opens it like a document.Under the hood it has packaging, signing, verification, sandboxing, snapshots, and a macOS runtime. But the point is not the architecture diagram. The point is that trust and isolation should be part of the user experience, not a README full of instructions.
-
★ Open source · maintained project
Mini vMac for Android
A classic Macintosh running on Android. Not because the world desperately needed it, but because I wanted to play Prince of Persia on my phone.
Show more
I ported Mini vMac to Android and kept it alive for years, adding screen, sound, keyboard, mouse, disks, networking, and even clipboard support so the thing feels surprisingly usable.
It is also a good reminder that software does not end when the code works. There are releases, bugs, weird devices, and people who just want their childhood Mac to boot.
-
Historical open source work · early 2000s
GNOME in Hebrew
A long time ago, I helped make GNOME work better in Hebrew. That meant translation, right-to-left behavior, and connecting with other open source enthusiasts when the community was still young.
Show more
I coordinated the Hebrew localization effort for GNOME. It was not just translating strings. It was right-to-left behavior, consistency, community coordination, and getting enough details right that the desktop felt like it belonged to Hebrew speakers.
It taught me early that software is for people, and that the last 10% — language, accessibility, follow-through — is where it either becomes theirs or stays yours.