Jeremy Horwitz Email & Phone Number

San Francisco

I returned to Salesforce to work on the Salesforce Zero project, which asked, What if Salesforce were started today? My work focused on Zero Object Service (ZOS—a new internal general-data-storage microservice):• 𝐁𝐚𝐜𝐤𝐰𝐚𝐫𝐝 𝐜𝐨𝐦𝐩𝐚𝐭𝐢𝐛𝐢𝐥𝐢𝐭𝐲: determining what aspects of current Salesforce features would need to be supported by Salesforce Zero• 𝐌𝐚𝐭𝐡/𝐚𝐥𝐠𝐨𝐫𝐢𝐭𝐡𝐦𝐬-𝐛𝐚𝐬𝐞𝐝 𝐢𝐬𝐬𝐮𝐞𝐬: solving particularly painful or difficult problems that were especially in my wheelhouse (e.g., compactly encoding Java/Kotlin Decimal objects monotonically)• 𝐃𝐨𝐜𝐮𝐦𝐞𝐧𝐭𝐚𝐭𝐢𝐨𝐧: making sure that our projects were well-documented (since we initially lacked a dedicated documentation professional)

San Francisco

Helped write core tools for use by company developers, including tools for encryption and digital signing; migrated internal projects onto tools. [Java]

San Francisco

During the first part of my Salesforce career, I worked on various back-end projects:• 𝐇𝐚𝐫𝐝 𝐝𝐞𝐥𝐞𝐭𝐞: removing soft-deleted customer data based on customer-specific retention policies• 𝐌𝐢𝐠𝐫𝐚𝐭𝐢𝐨𝐧: moving data between database instances ‣ Why? Examples: current server was too crowded, or customer needed their European data on European servers, or customer wanted their data on servers geographically closer to their machines ‣ Developed a tool to limit downtime (and read-only time)• 𝐊𝐞𝐠𝐞𝐫𝐚𝐭𝐨𝐫 𝐬𝐩𝐫𝐞𝐚𝐝𝐬𝐡𝐞𝐞𝐭: organizing seventeen separate kegerator maintainers, keeping up to date an index of what beers were available where at any given timeThe second part of my time at Salesforce was spent working on cryptography tools:• 𝐎𝐧𝐞-𝐬𝐭𝐨𝐩 𝐜𝐫𝐲𝐩𝐭𝐨 𝐬𝐡𝐨𝐩: the company’s security CTO asked me and one other developer to come up with tools to encrypt and decrypt (as well as sign and verify) arbitrary objects with various goals: ‣ Simplifying using cryptography for developers at Salesforce ‣ Providing a single place to update (in case of vulnerabilities, new algorithms, etc.) ‣ Discouraging others from “rolling their own” cryptographic tools ‣ Combatting certain attacks that an arbitrary developer might not consider (e.g., string-comparison timing attacks)• 𝐄𝐧𝐜𝐫𝐲𝐩𝐭𝐢𝐨𝐧 𝐚𝐭 𝐫𝐞𝐬𝐭: using the one-stop-shop tools to help develop Salesforce’s at-rest encryption feature

Santa Clara, California, United States

Taught courses (e.g., cryptography, cryptanalysis, discrete math, calculus), advised students, worked on Putnam competition, etc.

Seattle, Washington, United States

Led a team developing cryptographic foundations for Widevine products. Company was acquired by Google in 2010. [C]

Stanford, California, United States

RA: researched identity-based encryption, discrete logarithms, broadcast encryption, etc.TA: taught sections and lectures, graded.

Florham Park, New Jersey, United States

Researched the effect of partial key leakage on various fundamental results in cryptography.

Redmond, Washington, United States

Researched random Cayley digraphs; researched design of cryptographic primitives (e.g., discrete-logarithm algorithms) and anti-piracy technology.

Redmond, Washington, United States

Summers 1994–1997. Wrote code for Windows 95/NT internals—ScanDisk, telephony, DVD support. [C, C++]

Doctor Of Philosophy - Phd, Computer Science

Ph.D., Computer Science

Master Of Science - Ms, Mathematics

Bachelor Of Science - Bs, Mathematics And Computer Science

B.S., M.S., Mathematics & Computer Science