Liang Tang
Software Engineer at Facebook
New York, New York, United States
Summary
🤩
Rockstar🎓
Top SchoolLiang Tang is a software engineer with 11 years of experience building backend systems and data infrastructure, currently based in New York and working at Facebook. He has deep expertise in workflow and scheduling systems from his Azkaban work at LinkedIn—contributing cron scheduling, DB robustness improvements, and fixes across Hadoop-related job types—and later focused on Spark development as a senior engineer. Liang’s contributions show a pragmatic blend of bug fixes, refactors, and feature delivery in production-grade Java services integrating with big data ecosystems. He holds a PhD in Computer Science from Auburn University and began his industry experience with internships at LinkedIn and Salesforce, giving him both research rigor and practical product exposure. Colleagues would describe him as a backend-focused engineer who prefers to improve system reliability and developer experience rather than chase flashy front-end work. An underappreciated strength is his habit of surfacing small UX improvements in operational tooling—like email content and report end-date features—that materially reduce operator toil.
11 years of coding experience
9 years of employment as a software developer
Bachelor's degree, Bachelor's degree at Xi'an Jiaotong UniversityDoctor of Philosophy - PhD Computer Science, Doctor of Philosophy - PhD Computer Science at Auburn University
Github Skills (14)
javas10
azkaban10
back-end-development10
java10
hadoop9
javascript8
mysql8
database-design8
io5
commons5
apache-commons5
build-automation4
cicd4
sql4
Programming languages (9)
Github contributions (5)
azkaban/azkaban-plugins
Jul 2016 - Jun 2018
Plugins for Azkaban.
Role in this project:
Back-end Developer
Back-end DeveloperContributions:12 commits, 22 PRs, 11 pushes in 1 year 10 months
Contributions summary:Liang primarily contributed to the Azkaban plugins repository by addressing several issues and implementing new features. They made changes to various job types, including HadoopHiveJob, JavaJob, HadoopJavaJob, HadoopSparkJob, and HadoopPigJob, to resolve classpath issues related to dependency updates. They also introduced an EndDate feature to the Reportal plugin, including UI and backend modifications. Furthermore, the user disabled data content display in Reportal success emails and removed jobtype code, excluding Teradata-related components.
jenkins-api-pluginpluginazkabanpluginsjava
azkaban/azkaban
Jul 2016 - Dec 2018
Azkaban workflow manager.
Role in this project:Back-end Developer
Back-end DeveloperContributions:6 releases, 152 commits, 340 PRs in 2 years 4 months
Contributions summary:Liang primarily focused on modifying and maintaining the Azkaban codebase, with contributions spanning multiple areas. The user worked on fixing bugs, refactoring code, and adding new features, most notably the implementation of cron scheduling capabilities and database interaction enhancements. The user's work involved modifying Java code related to the trigger and executor systems. Furthermore, the user has refactored and updated the DB-related classes to improve robustness.
workflow-engineschedulingazkabanworkflow
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.