John Barboza
Senior Software Engineer at Amazon Web Services (AWS)
Bellevue, Washington, United States
Summary
🤩
Rockstar🎓
Top SchoolJohn Barboza is a senior software engineer with 10 years of experience building production-grade backend systems, currently designing AI-powered code generation and new Amazon Q products at AWS. He led the delivery of SageMaker’s Inference Recommender—owning the load-testing engine, CI/CD pipelines, and application security—and has a track record of shipping customer-facing ML tooling. Previously he ported and optimized low-level runtimes at IBM, including bringing libuv and Node.js to mainframe/EBCDIC platforms, demonstrating deep systems and cross-platform expertise. An active open-source contributor, his work on high-profile projects like libuv and Node.js includes platform-specific fixes for z/OS and AIX as well as protocol-compliant additions to the Lightning Network. Based in Bellevue and trained in electrical engineering at the University of Toronto, he combines systems-level C/C++ experience with modern cloud and Python/Java backend development.
10 years of coding experience
15 years of employment as a software developer
BASC Electrical Engineering, BASC Electrical Engineering at University of Toronto
Stackoverflow
1reputation
0reached
0answers
0questions
Github Skills (35)
asynchronous10
javascript10
multiplatform10
lightning-network10
async10
testing10
aix10
bitcoin10
cross-platform10
bitcoins10
c1110
c1710
zos10
nodejs10
platform-independent10
Programming languages (7)
Github contributions (5)
libuv/libuv
Jul 2016 - Oct 2018
Cross-platform asynchronous I/O
Role in this project:
Back-end Developer
Back-end DeveloperContributions:67 PRs, 3 pushes, 2 branches in 2 years 3 months
Contributions summary:John primarily contributed to the `libuv/libuv` repository by addressing issues related to cross-platform asynchronous I/O operations. Their work included fixing test cases and adding support for the z/OS platform. They implemented platform-specific features like atomic operations and implemented methods such as `uv__fs_futime` and `uv__io_check_fd`.
unixunicornsasynchronouswindowsio
nodejs/node
Dec 2016 - Aug 2018
Node.js JavaScript runtime ✨🐢🚀✨
Role in this project:Back-end Developer & QA Engineer
Back-end Developer & QA EngineerContributions:16 PRs, 94 comments, 2 issues in 1 year 8 months
Contributions summary:John primarily contributed to the Node.js runtime by addressing platform-specific issues, particularly for AIX systems. They fixed an OS release function and added testing, and avoided running `fsync` on directories on AIX. Furthermore, the user implemented and tested changes related to CLI argument parsing, including the support for the `--` option, and fixed an issue with timer callbacks. Additionally, the user worked on TLS related fixes, addressing a potential dangling pointer in a `TLSWrap` object.
windowsnode-jsjavascriptlinuxruntime
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.