Arvind Mukund is a Security Engineer in San Diego with 11 years of hands-on experience across product security, embedded systems, and OS-level development. He has driven security work at Qualcomm and now Snap, contributed to flagship open-source projects including rust-lang/rust (FFI and niche optimizations) and OpenEmbedded (image and package optimization), and maintained Android device trees for LineageOS and OmniROM. His background blends graduate-level CS training with practical firmware, hypervisor, and Trusted UI integrations, plus published tutorials for MediaTek SoCs. Beyond engineering, he founded a top-1% CTF team and competed in esports, showing a rare mix of offensive security mindset and deep systems engineering.
12 years of coding experience
4 years of employment as a software developer
Bachelor of Technology, Computer Science, Bachelor of Technology, Computer Science at SRM IST Chennai
Graduate, Computer Science, Graduate, Computer Science at Khoury College of Computer Sciences
The official Git repository is at https://git.openembedded.org/openembedded-core/.
Role in this project:
Embedded Systems Engineer / IoT Developer
Contributions:16 commits in 2 years 4 months
Contributions summary:Arvind's contributions primarily involve modifying recipes and classes within the OpenEmbedded build system. They focused on splitting existing packages like `mii-tool`, `ps`, `sysctl`, `sudo`, and `ip` into individual packages, indicating an effort to optimize system size. Furthermore, the user added support for VHD/VHDX generation and integration within the build process, enabling the creation of virtual disk images for appliance deployments. These changes suggest a focus on build system customization and image optimization for embedded systems.
Empowering everyone to build reliable and efficient software.
Role in this project:
Back-end Developer
Contributions:2 commits, 1 PR, 20 comments in 1 day
Contributions summary:Arvind primarily contributed to the `rust-lang/rust` repository by implementing and refining the FFI (Foreign Function Interface) capabilities, particularly regarding how the Rust compiler handles `Result<T, E>` types and niche optimizations across FFI boundaries. They focused on improving the linting process to ensure FFI safety, adding tests for various scenarios, and addressing edge cases in type checking, ensuring that the compiler correctly handles types eligible for niche optimization. This work enhanced the interoperability of Rust code with other languages and systems via FFI.
crategarbage-collectionrustreliablecompiler
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.