The pitch is compelling. I wonder how many teams will be able to operate sharded database setups in production as a result of this.
12 karma · joined September 14, 2012
The pitch is compelling. I wonder how many teams will be able to operate sharded database setups in production as a result of this.
Hi HN. I am an Engineering Manager at Nectar Social, and we're hiring across product, design and engineering.
The traditional playbook of buying ads on social media platforms no longer works for most brands. Buyers make purchasing decisions from organic conversations on social media platforms like Instagram, Reddit, X, and LinkedIn. Nectar listens to conversations in real time, surfaces actionable insights, attributes engagement to revenue, and drives conversions.
We came out of stealth last year and we are on a fast growth trajectory working with brands like OLIPOP, Hatch, K18, and Little Spoon. The company is ~30 FTEs and has many interesting challenges:
1. We ingest data from major social media which brings scaling and performance problems
2. We run AI agents on the content which requires us to control cost and optimize quality
3. We need to present lots of information about social conversations in an understandable way which requires good design.
4. We need to build resilient systems that can work within the constraints of our third party dependencies.
Our tech stack is React, Typescript, AWS, Pulumi, Postgres, Clickhouse and Turbopuffer. We use AI tools thoughtfully to optimize our daily work - Cursor, Claude Code, Graphite, v0 / Replit, and Granola.
The roles we are hiring for:
- Staff Backend Engineer - https://jobs.ashbyhq.com/nectar-social/e5797dfd-275e-4a7a-b9...
- Staff Product Engineer - https://jobs.ashbyhq.com/nectar-social/2f942c62-bc21-41a2-ae...
- Founding Mobile Engineer (React Native) - https://jobs.ashbyhq.com/nectar-social/192caa1d-8f36-472f-b9...
- Senior Product Designer - https://jobs.ashbyhq.com/nectar-social/673bbd54-9a3b-4478-84...
- Senior Product Manager - https://jobs.ashbyhq.com/nectar-social/b63c6254-df3d-406e-83...
Please email careers@nectarsocial.com with "HN" in the subject line if you're interested.
At the beginning, it's nice to know that team A is responsible for service B, so that if there are any bugs/feature requests, you know who to go to.
This neat story falls apart if team A gets dissolved or merged with another team. The new group owning service B doesn't feel the same level of ownership. When maintenance work comes in (security vulnerabilities, stack modernization, migrations), the team is forced to internalize it rather than share it with other teams.
Operational maintenance also becomes a lot harder - deploying many services correctly is much more difficult locally, in pre-prod, and in production. Any benefits you get from writing a single HTTP server quickly are erased in the time spent on integration work with the rest of the company.
Here is a blog post that makes a more expansive argument against microservices: https://www.docker.com/blog/do-you-really-need-microservices...
I use Claude 3.5 for my daily coding tasks, but used Gemini Pro 1.5 to analyze a new Github repository the other day because it has a much larger context size.
You simply run `llm -m gemini-1.5-pro-preview-0409 "<your question>"`
There's very little guesswork about what it's going to do to a database because your migrations are raw SQL statements with no additional layers of complexity or translation.
In my experience, the open source tooling around GraphQL is much better than the tools that generate types from other SDLs like protobufs.
This makes it really easy for servers and clients to behave in a typesafe manner.
I've seen a backend service / front-end SPA use REST, grpc and then GraphQL to communicate. Type safety has been the easiest to understand and scale across the eng team using the GraphQL ecosystem.