Neetha Sebastian

Software Engineer at Google

San Jose, California, United States
email-iconphone-icongithub-logolinkedin-logotwitter-logostackoverflow-logofacebook-logo
Join Prog.AI to see contacts
email-iconphone-icongithub-logolinkedin-logotwitter-logostackoverflow-logofacebook-logo
Join Prog.AI to see contacts

Summary

🤩
Rockstar
🎓
Top School
Neetha Sebastian is a software engineer with seven years of professional experience based in San Jose, California, currently working at Google. She has a strong academic foundation with MS degrees from IIT Madras and Columbia Engineering and a BS from Visvesvaraya Technological University. Her background includes a Microsoft design engineer role and contributions to backend systems, with recent open-source work on Grafeas where she refined vulnerability protos to improve security metadata modeling. Neetha combines API design sensibilities with practical engineering—removing distro-specific fields and introducing an effective severity model shows attention to long-term API evolution and data consistency. Colleagues describe her as a thoughtful engineer who bridges research-quality rigor from her academic training with production-focused delivery at major tech firms.
code7 years of coding experience
job1 year of employment as a software developer
bookIndian Institute of Technology Madras
bookBachelor of Science (BS), Bachelor of Science (BS) at Visvesvaraya Technological University
bookMS, MS at Columbia Engineering
github-logo-circle

Github Skills (5)

vulnerabilities10
go10
protobuffer10
protobuf10
api-design9

Programming languages (1)

Go

Github contributions (4)

github-logo-circle
grafeas/grafeas

Feb 2019 - Jul 2022

Artifact Metadata API
Role in this project:
userBack-end Developer
Contributions:24 reviews, 94 commits, 28 PRs in 3 years 5 months
Contributions summary:Neetha primarily worked on modifying the protobuf definitions related to vulnerability information within the Grafeas project. They removed a distro-specific severity field and introduced a new effective severity field in the vulnerability message for the v1 protos. They also addressed comments on the vulnerability proto definition and removed generated files, ensuring consistency across different API versions. These changes indicate a focus on API evolution and data model refinement related to security vulnerability reporting.
metadata-apiapiartifactmetadata
nms2140/grafeas

Feb 2019 - Jul 2022

Cloud artifact metadata CRUD API and resource specifications
Contributions:4 PRs, 70 pushes, 6 branches in 3 years 5 months
apicrud-apidata-catalogcrudspecifications
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.
Request Free Trial
Neetha Sebastian - Software Engineer at Google