Hacker News new | ask | show | jobs
by dlojudice 1440 days ago
There seems to be a demand for developers who know the internals of Postgres to evolve and customize it given that it is being used, at different levels of abstraction/layers, by basically all cloud providers (AWS, MS, Google, etc) and by some DB SaaS. BTW, that would be a cool job to have...
4 comments
kiwicopple 1440 days ago
We’re hiring for this role at supabase (if you’re looking): https://boards.greenhouse.io/supabase/jobs/4307456004
link
httgp 1440 days ago
A ton of companies are building on top of PostgreSQL — Yugabyte, Supabase, EdgeDB and Neon.
link
thejosh 1440 days ago
Hopefully pushing back upstream. I don't really care what they do, as long as they push back their usually awesome changes upstream.

Great to see these sorts of things, Postgres has been amazing and glad people realise it.

link
sudhirj 1440 days ago
Most of the changes aren’t relevant to upstream - a lot these companies seem to be using Postgres as a frontend over some kind of secret sauce, usually related to custom storage or deployments or the like. Postgres seems very modular and pluggable that way.

I assume for the common Postgres core changes everyone is already incentivised to contribute changes back upstream - the companies are banking on Postgres popularity can need it to have an excellent reputation even outside of their specific customised offering.

link
yashap 1440 days ago
Another recent one, AlloyDB from Google Cloud. Looks pretty interesting/promising. Sort of like their competitor to AWS Aurora, built on top of Postgres, with the added ability to handle OLAP workloads well (along with apparently great OLTP performance).

TimescaleDB and Citus are notable too.

But yeah, if you’re building a DB product, starting with Postgres and customizing from there seems like an excellent approach.

link
LoriP 1440 days ago
Timescale is hiring for a Software Engineer (Database Internals) and this could also be a senior-level hire. It's based on PostgreSQL but if the rest of the resume stacks up it's not 100% essential that you've worked on PostgreSQL internals before. Global, remote.
link
avinassh 1439 days ago
> It's based on PostgreSQL but if the rest of the resume stacks up it's not 100% essential that you've worked on PostgreSQL internals before

What would be an ideal resume for someone who never worked on Postgres

link
johnthescott 1440 days ago
more like ice cold.
link