Tiago Costa is a Principal/Area Lead software engineer based in Porto, Portugal with 11 years of experience focused on front-end and JavaScript engineering while also contributing deeply to build systems and back-end tooling. He currently works on Kibana at Elastic and has a track record of improving large codebases—migrating security components to Babel, stabilizing tests, and resolving complex build and integration issues. Tiago is an active open-source maintainer and contributor to well-known projects like webpack-contrib/thread-loader and rules_nodejs, where he fixed memory leaks, improved worker pool stability, and modernized TypeScript/Bazel integration. Equally comfortable across the stack, he blends pragmatic refactoring and infrastructure work with a strong emphasis on build reliability and developer experience. Outside code, he brings a problem-solving mindset shaped by a lifelong curiosity—he’s passionate about aircraft, travel, and dreams of one day coaching football.
11 years of coding experience
1 year of employment as a software developer
Master's Degree, Informatics and Computer Engineering, Master's Degree, Informatics and Computer Engineering at Faculdade de Engenharia da Universidade do Porto
Software Engineer (focused on build tools and utilities)
Contributions:13 commits, 29 PRs, 2 pushes in 8 months
Contributions summary:Tiago primarily focused on maintaining and improving the `thread-loader` project, a webpack loader for parallelizing tasks. Their contributions included bug fixes, particularly addressing memory leaks, lifecycle management, and worker pool errors. They also updated dependencies, improved build processes by correcting worker calculations, and enhanced code stability by handling edge cases. Additionally, the user optimized the project by utilizing `neo-async` for asynchronous operations.
Contributions:817 reviews, 1874 commits, 2637 PRs in 4 years 8 months
Contributions summary:Tiago was primarily focused on migrating code to the babel transpiler for the security solution components, involving changes to package builds and configurations. They also addressed various build and integration issues, including skipping flaky tests, fixing issues around file pathing, and updating the codebase to align with the new upgrade to rules_nodejs v5. This indicates involvement in build, testing, and code refactoring, likely within the codebase of a large system. Additionally, they made contributions to improve the accuracy of tests.
elasticdashboardskibanaobservabilitywindow
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.