{"@attributes":{"version":"2.0"},"channel":{"title":"Data on Openinx Blog","link":"https:\/\/openinx.github.io\/tags\/data\/","description":"Recent content in Data on Openinx Blog","image":{"title":"Openinx Blog","url":"https:\/\/openinx.github.io\/%3Clink%20or%20path%20of%20image%20for%20opengraph,%20twitter-cards%3E","link":"https:\/\/openinx.github.io\/%3Clink%20or%20path%20of%20image%20for%20opengraph,%20twitter-cards%3E"},"generator":"Hugo -- 0.125.7","language":"en","lastBuildDate":"Sun, 04 May 2025 23:16:23 -0700","item":{"title":"What I learned from ByteDance","link":"https:\/\/openinx.github.io\/posts\/2025-05-04-review-bytedance-journey\/","pubDate":"Sun, 04 May 2025 23:16:23 -0700","guid":"https:\/\/openinx.github.io\/posts\/2025-05-04-review-bytedance-journey\/","description":"I recently had the pleasure of joining Databricks, but I often reflect on my profoundly rewarding experience at ByteDance. Before joining ByteDance, I was a software engineer who had written code for a decade. My core responsibility was to tackle system design and code development for complex software while ensuring robust operations in production environments. At ByteDance, however, I led a 16-person technical team (mostly Senior+ engineers) responsible for building the competitiveness of ByteDance\u2019s public cloud EMR open-source engines\u2014a role that was immensely challenging yet transformative for me."}}}