Similar here. Lots of places where we replaced Pandas with DuckDB for transformations. Also have scriptable custom dashboards running on top of BigQuery data pre-aggregated and extracted to parquet on GCS. It's way faster and the only limiting factor is your viz library. It was pretty easy to build and the only big gotcha I encountered was finding, somewhat counter-intuitively, that it's often best minimize partitioning.
> the only big gotcha I encountered was finding, somewhat counter-intuitively, that it's often best minimize partitioning.
For parquet, I think with partitioning, it's really important to be mindful of the ordering of the data within the parquet file and also the query patterns of the main use cases. A little hard to generalize well to every pattern I guess.
Remember the context - this is while solving a whiteboard problem. Its bad in the same way asking candidate what their birthstone is - because any answer offer little or no signal about the odds of a candidates success at the company.
I'm curious to know why you think asking about AI usage is a good interview question.
If you're going to have people use AI regularly, it's worth asking so that you can get a sense of their interest/willingness, experience level, and training needs. That said, more specific questions are typically more revealing. Personally I'm fond of "If you could give Claude only 1 instruction, what would it be?"
Friendly reminder that you don't have to enable PostHog replays at all. I have a site lightly instrumented server-side with the slim bundle, and I'm still gonna double check my account settings but I'm pretty sure it's not even capable of doing the replay telemetry.
