Sebastiano Poggi
Senior UX Engineer at Google
Veneto, Italy
Summary
🤩
RockstarSebastiano Poggi is a Senior UX Engineer at Google with 14 years of hands-on software engineering experience and a long history in Android development dating back to 2009. A Google Developer Expert, he blends deep platform knowledge with practical UX-focused engineering—shipping polished UI experiences in Android Studio while previously building mobile features and infrastructure at Novoda. He’s an active open-source contributor, having improved static analysis tooling in detekt (including bug fixes and build automation) and incubated Android Slices demos in Novoda’s spikes repo. Trained in mechatronics and with a past in guerrilla videomaking, he brings a multidisciplinary, design-minded approach to problem solving and developer ergonomics. Based in Veneto, Italy, he pairs low-level platform familiarity with a knack for making developer tooling and UI workflows more robust and enjoyable.
14 years of coding experience
Github Skills (13)
kotlin10
linting10
uid10
static-code-analysis10
gradlew10
front-end-development10
ui-design10
android10
build-automation10
groovy10
gradle10
javas8
java8
Programming languages (17)
Github contributions (5)
novoda/spikes
Dec 2016 - Jul 2018
Where ideas & concepts are born & incubated
Role in this project:
Mobile Developer (Android)
Mobile Developer (Android)Contributions:45 commits, 25 PRs, 28 pushes in 1 year 7 months
Contributions summary:Sebastiano contributed significantly to the `novoda/spikes` repository, primarily focused on building and improving an Android application demonstrating Android Slices functionality. They developed infrastructure components, including Gradle build files and initialization scripts, and also implemented core features by creating multiple Kotlin-based Slice implementations. The user's contributions included the creation of UI elements, such as a demo and search-based slices, and improvements to the UI of the host app.
androidnovodaspikejavaproof-of-concept
detekt/detekt
Jun 2017 - Mar 2020
Static code analysis for Kotlin
Role in this project:Back-end Developer & Build Automation Engineer
Back-end Developer & Build Automation EngineerContributions:74 commits, 17 PRs, 144 comments in 2 years 9 months
Contributions summary:Sebastiano primarily contributed to the project by modifying a Groovy script related to GitHub milestone reporting, making parameters optional and trimming names. They also updated the Gradle wrapper to use Gradle 4.1-rc-2. Furthermore, the user addressed multiple bugs in the MagicNumber rule, refactoring the code for better test output, adding configurability, and making the rule more robust and comprehensive.
linterlintanalysisstatic-code-analysiscode-quality
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.