I'm an Associate Software Engineer at PibyThree, building enterprise-grade data and AI platforms on top of the modern data stack. My work sits at the intersection of data engineering, cloud platform design, and applied AI β turning raw, messy, multi-source data into governed, trustworthy systems that enterprises can build products on.
- π§ Enterprise AI β designing agentic and LLM-powered systems for document understanding, fraud detection, and retrieval over structured + unstructured data
- βοΈ Snowflake β ingestion frameworks, governance, access control, lineage, and performance engineering at scale
- π§ dbt & Analytics Engineering β metadata-driven transformation, testing, and data quality as code
- π Open Source β contributing back to the dbt and data engineering community
- βοΈ Automation & Platform Engineering β Go services, Airflow orchestration, and infrastructure-as-code with Terraform
- βοΈ Cloud β AWS and Databricks across production data platforms
I care about building systems that are observable, governed, and quietly reliable β the kind of infrastructure enterprises don't have to think about because it simply works.
|
|
|
I contribute upstream to dbt-core and community packages β improving macros, tests, and documentation for the analytics engineering ecosystem β and maintain internal-turned-public tooling around Snowflake governance and data ingestion.
How this profile stays alive
Every animated asset in this README is a self-contained SVG β no third-party image services, no external rendering APIs. Two GitHub Actions keep it current:
update-stats.ymlruns.github/scripts/generate_profile_assets.pyon push and on a daily schedule, pulling real numbers from the GitHub REST + GraphQL APIs and re-renderingstats-*.svg,languages-*.svg, andtrophies-*.svgin place. Repo and star counts work out of the box; for contribution / PR / issue totals, add a fine-grained personal access token with read-only profile access as a repository secret namedGH_STATS_TOKEN.snake.ymlrenders the contribution calendar into the animated snake every 12 hours and publishes it to theoutputbranch.
Until the first scheduled run completes after upload, the stats and achievement cards render an honest "syncing" state rather than placeholder numbers.