News for hackers. Stuff that matters.

ctc24

Re:Ask HN: Who is hiring? (March 2026) on Monday March 02, 2026 @02:33PM (#47222944)
Prequel | Software Engineers (backend or full-stack) | NYC (ONSITE) | $170k-$210k | prequel.co

Prequel enables software companies to sync data to their customers' data environments, at massive scale. With the rise of agents, syncing data to customers' data environments is becoming table-stakes for a lot of software companies. We make that incredibly easy for them.

We're a team of four engineers based in NYC. We're cash-flow positive and growing fast. We're solving a number of hard technical problems that come with syncing hundreds of billions of rows of data every day with perfect data integrity: building reliable & scalable infrastructure, making data pipelines manageable without domain expertise, and creating a UX that abstracts out the underlying complexity to let the user share or receive data. We're powering this feature at companies like Stripe (Metronome), Gong, Iterable, and more.

Our stack is primarily Golang/K8s/Postgres/DuckDB/React/Typescript and we support deployments in both our public cloud as well as our customers' clouds. Due to the nature of the product, we work with nearly every data warehouse product and most of the popular RDBMSs.

Apply here: https://www.ycombinator.com/companies/prequel/jobs/VNoKffl-s... or email jobs (at) prequel.co and reference this post.

I'm with you on the misspellings. This is why we ultimately ruled out any of those options.
Agreed, I like `ingest` as well. It does somewhat violate principle d), but the other solutions violate more of those. And to your point, they're principles, not rules.

Ask HN: What would you call a package whose purpose is to import data?

Let's assume you're writing Go, Python, or any other language in which `import` is a reserved keyword. Let's assume also that you're writing a new package, whose purpose is to "import" data.What do you name this package?Our team went through this exercise semi-recently, and we're curious about how everyone else would think about it. Here's a (non-exhaustive) list of options we considered:...

( Read More... | 12 comments | 7 points | on HN )
Re:Ask HN: Who is hiring? (April 2025) on Wednesday April 02, 2025 @11:19AM (#43557679)
Prequel | Staff Frontend / Full Stack Engineer / SWE Intern | ONSITE in New York City | Full Time | https://prequel.co

- Prequel is the customer data access platform. We enable SaaS companies like LaunchDarkly, Gong, and LogRocket to make data accessible to their customers.

- Transferring trillions of rows between data stores every month.

- Revenue is up 50% since Jan 1.

- We're launching a new product which is quite frontend heavy, and want to bring a pro onboard who can act as tech lead for it. This is not your standard CRUD app -- a big part of it is building complex SDKs and APIs used by engineers at top-tier companies.

- Frontend in Typescript/React, backend in Go.

- Team is stacked, with alums from Stripe, GIPHY, Google, Flatiron Health, and more.

- We're based in NYC with our HQ in Chelsea.

Apply here: https://www.ycombinator.com/companies/prequel/jobs/wdjx5KE-f... or email careers (at).

Disagree on the data silo issue. There's a growing trend of SaaS providers making data available to their customers by feeding it back into their DWs. It started with the likes of Segment and Heap, and has now grown to include companies like Stripe, Salesforce, and Zuora to name a few. I'd wager that making data accessible is only going to become more table-stakes over time.
That's a bit of a strawman argument. Per the post, you can't leverage this on a read replica, it has to be run on primary. So you're going to stand up and manage a full new Postgres instance for this?

I'm sure there are many cases when that makes sense, but there are many cases when that's also overkill. An in-memory cache inside your server will give you better performance, and a lot of less infrastructure maintenance complexity.

Why wouldn't you simply use SQLite (or some other in-memory flavor of SQL) instead of hacking the main Postgres db and adding load to the primary instance?

The author makes a valid point that there's something nice about using familiar tooling (including the SQL interface) for a cache, but it feels like there are better solutions.

Re:Ask HN: Who is hiring? (December 2023) on Friday December 01, 2023 @04:43PM (#38492886)
Prequel | https://prequel.co | Senior/Staff Software Engineer | Full Time | GoLang, Postgres, Typescript, React, K8s | $150k-$200k + equity | ONSITE in NYC

Prequel is an API that makes it easy for B2B companies to sync data directly to their customer's data warehouse, on an ongoing basis.

We're solving a number of hard technical problems that come with syncing tens of billions of rows of data every day with perfect data integrity: building reliable & scalable infrastructure, making data pipelines manageable without domain expertise, and creating a UX that abstracts out the underlying complexity to let the user share or receive data. We're powering this feature at companies like LogRocket, Modern Treasury, Postscript, and Metronome.

// Full job posting here -- https://prequelco.notion.site/Senior-Software-Engineer-Prequ...

// To apply -- email [email protected] and include [HN] in the subject line

Re:OpenAI announces leadership transition on Friday November 17, 2023 @04:45PM (#38310907)
I don't thing there's necessarily anything there. Microsoft might be burning money because they've decided that browser adoption and usage is worth it to them. It doesn't have to involve OpenAI in any way.

Older »