Emily Mu is a Cambridge-based CTO and co-founder with 11 years of experience building engineering teams and product-grade tools for legal tech. She blends deep technical roots in cryptography and security—evidenced by substantive contributions to well-known projects like OpenSC, Botan, and Crypto++—with research pedigree from MIT, where she pursued a PhD in EECS. Her background spans applied AI and computer vision at Microsoft, quantitative research and trading, and practical systems engineering from internships at Google and D. E. Shaw, giving her a rare mix of research rigor and production experience. Emily is comfortable shipping low-level security features (PKCS#11, RSA-OAEP, crypto bindings) and higher-level ML/vision systems, which helps her bridge legal domain product needs with robust, auditable engineering.
11 years of coding experience
2 years of employment as a software developer
Doctor of Philosophy - PhD Computer Science, Doctor of Philosophy - PhD Computer Science at Massachusetts Institute of Technology
Open source smart card tools and middleware. PKCS#11/MiniDriver/Tokend
Role in this project:
Security Engineer
Contributions:3 reviews, 7 commits, 19 PRs in 1 year 10 months
Contributions summary:Emily primarily contributed to fixing bugs and implementing features within the `opensc/opensc` repository, which focuses on smart card tools and middleware. Their work involved addressing issues related to security, specifically concerning key derivation, certificate access, and signature encoding within the `pkcs11-tool`. The user added support for RSA-OAEP and the OpenPGP applet version retrieval, enhancing the library's capabilities. Their contributions demonstrate a focus on PKCS#11 and security-related aspects of smart card interaction.
Contributions:23 commits, 15 PRs, 17 pushes in 4 years 6 months
Contributions summary:Emily contributed significantly to the Crypto++ library, making changes to several core files. These changes involved implementing, updating, and reverting HMQV (Hashed Menezes-Qu-Vanstone) key agreement protocol, addressing issues related to macros and compiler configurations and correcting the default key length of AES for DLIES algorithm, demonstrating a strong understanding of cryptographic principles. The user also updated and maintained build configurations and incorporated fixes.
Find and Hire Top DevelopersWe’ve analyzed the programming source code of over 60 million software developers on GitHub and scored them by 50,000 skills. Sign-up on Prog,AI to search for software developers.