Founder Directory
Built by Keitoto
Founders4
Known for these resultsRole100%Role is parsed from founder titles in yc.db. Known for 100% of these rows — the rest have no title at all, mostly 2019–2023. Those rows stay in the result and are counted as Unknown, never as No.Bio100%Bio coverage: 100% of these founders have a bio on their YC profile. Every bio-derived facet (ex-company, school, credentials, discipline) is Unknown for the rest.Ex-company25%Ex-company is matched from bios with employment context (ex-, formerly, worked at). 25% of these rows have at least one match.School75%School is matched from bios, case-sensitive for acronyms. 75% of these rows have at least one match.
- Amgad Al-ZamkanFounder/CPO · TenorS26B2B · San Francisco
- Hamze Al-ZamkanFounder/CEO · TenorS26B2B · San Francisco
- Muhtasham Oblokulov@Muhtasham9Founder/CTO · TenorS26B2B · San Francisco
- Kyler Blue@kylerblueFounder/CEO · WavedashX25Consumer · Los Angeles
FOUNDERROLEBATCHINDUSTRYLOCATIONTEAMX_url
Amgad Al-ZamkanTenorFounder/CPOSummer 2026B2BSan Francisco, United States3—Hamze Al-ZamkanTenorFounder/CEOSummer 2026B2BSan Francisco, United States3—Muhtasham OblokulovTenorFounder/CTOSummer 2026B2BSan Francisco, United States3https://x.com/Muhtasham9Kyler BlueWavedashFounder/CEOSpring 2025ConsumerLos Angeles, United States3https://x.com/kylerblue
Showing 1–4 of 4 founders
Amgad Al-Zamkan
Founder/CPO·Tenor
PRIMARY INFO
RoleFounder/CPO
Team size3
BatchSummer 2026
LocationSan Francisco, United States
Company statusActive
StageEarly
BIO
Co-founder @ Tenor. Previously at Amazon, studied CS at UC Berkeley and TUM. As a grad student, Amgad's research focused on optimization objectives in recommendation algorithms and shaping adaptive decision systems.
Ex-company, school and discipline below are derived from this bio. Nothing is inferred when the bio is missing.
BACKGROUND
Credentialsnone mentioned
DisciplineResearcherKeyword match from the bio text, not a classifier.
TRACK RECORD
First YC company on record
COMPANY CONTEXT
TenorAI workers that attribute the outcome back to the token spend
