Raúl Ochoa retweeted
After being away from LinkedIn (well, everywhere) for several years, I’m catching up. What makes me happiest is seeing people I met at Tinybird building their own startups or doing incredible things at top companies.
It’s such a joy to come across these stories.
After almost 7 years, I am no longer with Tinybird.
I spent that time building the company from the initial versions of the product to a platform processing trillions of rows and petabytes of data on ClickHouse.
Scaling the tech was a great challenge, but building and working with the engineering team behind it was the best part.
I’m exploring new opportunities.
My interest is in data infrastructure, high-concurrency, and technical leadership. I like building things that shouldn't work at scale, but do.
If you're building a technical org or solving hard data problems, my DMs are open. No rush, just looking for the right fit.
Raúl Ochoa retweeted
Tinybird is the infra backbone for @dubdotco Analytics, helping us go from 0 → 250M clicks in the last 2 years.
We're now doing ~75M clicks/mo and with that, it's critical that any DB migrations we make don't break prod.
Tinybird's code-first DX is a game-changer for this.
🌅 Tinybird Forward is here »
Forward is a major evolution of Tinybird, designed to make shipping software with big data requirements faster and more intuitive.
No complex infra project. No context switching. No esoteric architectures. Just code.
Here's what's new:
» Local-first developer experience
» Instant feedback loops during local dev
» Native integration with AI coding agents
» End-to-end testing in CI/CD without cloud
» Single-command deploy/rollback
» Frictionless schema migrations in production
» Self-managed Tinybird deployments, for free
(🔊 sound on! 👇)
Just a reminder: on Azure, data transfer across availability zones using private or public IPs is free.
We take care of keeping ClickHouse up-to-date for our customers. You don’t want to worry about that.
So, how do we currently roll out new versions of ClickHouse for our customers?
What do we want to do?
Roll out new ClickHouse versions as we release any other software in our stack.
The flow should be like this: create a pull request with the target ClickHouse version, run the tests in the CI, merge it, deploy it, repeat.
If that sounds interesting to you, let’s talk. We are hiring to work on this problem.
tinybird.co/job-offers/click…