HNHacker News
TopNewBestAskShowJobs

bastienbeurier

289 karma · joined September 23, 2013

submissionscomments
bastienbeurier··on Ask HN: Who is hiring? (February 2026)
Nango | Full-time | Remote (North America, LATAM, Europe) | https://nango.dev

Nango (YC W23) is a developer infrastructure company and the leading provider of API access for agents and apps. It enables AI applications to connect to the real world through integrations.

More than 250 paying customers rely on Nango today, including Replit, Mercor, and Exa. We are a YC-backed, multi-million ARR company with a team of 10 from AWS, Snyk, Netlify, Uber, Samsara.

We’re hiring for the following openings:

* Backend engineer

* Product engineer, Customers

* Product engineer, Growth

* Chief of Staff

* Developer Content Engineer

Find out more, and apply at: https://jobs.ashbyhq.com/Nango

bastienbeurier··on Ask HN: Is it still worth pursuing a software startup?
I personally think the hard part of building a SaaS app is not coding, it's understanding the complexities of a problem and building good abstractions to solve it. Code/software is the result, but certainly not the main challenge. And I think this reflects the time breakdown of good software engineers (mostly collaborating, brainstorming and designing interfaces vs. coding).
bastienbeurier··on Delete LinkedIn – you'll have zero fucking regrets (2021)
When recruiting, LinkedIn is useful for three things for me: 1. Propagating the job ad 2. Verifying that an applicant is real (profile picture, network, work history, etc.). I’m seeing more and more fake applications lately. 3. Letting candidates apply with just a LinkedIn URL (when they keep it reasonably up to date)

None of this is really about social networking.

Ideally, I’d much rather have a universal résumé platform with proper ID verification, and separately a job board with reach comparable to LinkedIn.

Until something like that exists, deleting LinkedIn mostly means candidates lose out on discovering jobs and applying quickly to them.

bastienbeurier··on Ask HN: What are you working on? (July 2025)
https://gogogame.org helps you find people nearby to play sports or other games with.
bastienbeurier··on Ask HN: What are you working on? (July 2025)
https://gogogame.org helps find people nearby to play sports or other games with.
bastienbeurier··on Ask HN: What Are You Working On? (June 2025)
https://gogogame.org

A free app to find and post local games — sports, board games, etc. (solo side project)

bastienbeurier··on Ask HN: What Are You Working On? (June 2025)
A free site to find sports/games around you (tennis, basket, chess, etc). You propose a game at a certain date/place, and people around can reach out to join. Let me know if you want to try it out (ready in the coming days).
bastienbeurier··on Ask HN: Who is hiring? (March 2025)
Nango | Full-stack, backend & infra engineers | Remote, EST timezone | https://nango.dev/careers

Nango is the most comprehensive product integrations platform for developers.

Fully remote, open source, dev tool & dev infra.

Expert team of veterans (Netlify, Algolia, Uber).

Backed by YC & top company execs (Cloudflare, Retool, Notion, Calendly, Sendbird).

Serving 400+ companies, 5k GitHub stars, community of 2k developers.

<10 team & fast-growing. We need you :)

bastienbeurier··on Ask HN: Who is hiring? (February 2025)
Nango | https://nango.dev | Remote (Americas, Europe) | FT | Full-stack engineer

Nango is an open-source platform that powers product integrations. It’s a developer tool built by engineers, for engineers, making it seamless to connect B2B software, natively. We serve 400+ companies with fast-growing revenues.

Apply at https://nango.dev/jobs.

bastienbeurier··on Ask HN: What Are You Working On? (October 2024)
An app to collect memories easily. You capture vocal notes, which are transcribed & corrected with AI.

As a father, I wanted to capture all the little moments of our day-to-day family life to later share with my grown-up children. However, I did not have the discipline to journal regularly. So, I made Memzy to capture them easily on the fly!

https://apps.apple.com/us/app/memzy-easy-journaling-with-ai/...

bastienbeurier··on Ask HN: Who is hiring? (October 2024)
Nango | Full-stack | Remote (Americas/Europe)

Let developers build product integrations 10x faster. Developer infrastructure / open source. Y Combinator (W23), seed stage, founded in 2022. Fully remote (Americas & Europe), 5 team members. Fast-growing revenues, 300+ companies in prod, 4.5k GH stars, community of 2k developers.

Apply here: https://nango.dev/jobs

bastienbeurier··on Ask HN: How does Merge.dev sell itself as a unified API?
If you are interested, we are working to solve these shortcomings at nango.dev.

Instead of having a black-box unified API, you can define the schemas/interactions between Nango & external APIs, in code. Which means you can do detailed data validation, specific to your use case, so you get back fully-typed objects. You control the data transformations to match your specific use case (so when APIs have different values for, let's say, "contact status", you define the mapping). You only sync the data you need, not full objects, so it's efficient.

A call to fetch records looks like this:

curl --request GET --url 'https://api.nango.dev/records?model=MODEL-DEFINE-BY-YOU' --header 'Connection-Id: YOUR-CUSTOMER' --header 'Provider-Config-Key: EXTERNAL-API'

Curious to hear what you think!

bastienbeurier··on Launch HN: Nango (YC W23) – Source-available unified API
Standard pre-built integrations are ok to get started. But rapidly customers ask for more integration capabilities, which are not supported by standard integrations. At this point, SaaS companies need to build custom integrations that fit exactly what they customers want.
bastienbeurier··on Launch HN: Nango (YC W23) – Source-available unified API
The players you mentioned pre-build standard integrations, in specific categories (e.g. HRIS). We build a platform that lets developers build custom integrations, for any API.

We do offer integration "templates", but it's only a way to get started and templates are meant to be extended.

That's also why our catalog of APIs is extensive. Anybody can rapidly add support for any new API and start building custom integrations for it, and share templates with the community.

bastienbeurier··on Launch HN: Nango (YC W23) – Source-available unified API
We've noticed the same pain point and we are providing increasingly better support for ERPs. Realistically, it takes time to build expertise on each of them, but we'll get there!
bastienbeurier··on Launch HN: Nango (YC W23) – Source-available unified API
The main difference is that Merge pre-builds all integrations, with limited customization capabilities, while Nango gives you full control over the code of the integrations.
bastienbeurier··on Launch HN: Nango (YC W23) – Source-available unified API
Yes, this works, and it's a feature we offer for free!
bastienbeurier··on Launch HN: Nango (YC W23) – Source-available unified API
Some integrations are connected at the org level (one account for the entire company), and others at the user level (many accounts per company). For the latter case, the pricing per connection is lower.
bastienbeurier··on Launch HN: Nango (YC W23) – Source-available unified API
Thank you for the insights and looking forward to chatting!
bastienbeurier··on Launch HN: Nango (YC W23) – Source-available unified API
It does!

Because Nango lets you define input & output models of integrations, it's easy to standardize them across APIs.

So, when syncing users from Slack/Discord/Teams, you define a standard User model, and all 3 integrations map to this model.

You then consume User objects from a unified endpoint, regardless of where they come from.

bastienbeurier··on Launch HN: Nango (YC W23) – Source-available unified API
1) That's right!

2) You can write your own integration scripts, in code, consuming any endpoint from the external API, so you are not limited to what Nango pre-builds (details: https://docs.nango.dev/understand/concepts/scripts).

But you can also access the original API through the proxy, which will inject credentials, log requests, help you with pagination (details: https://docs.nango.dev/understand/concepts/proxy).

bastienbeurier··on Ask HN: Who is hiring? (February 2024)
Nango | Backend Engineers | Full-time | Remote (US/Canada East & Europe) | https://nango.dev

Nango is a developer platform to build product integrations 10x faster.

We’re 5 veteran engineers (Uber, Netlify), repeat founders who did YC multiple times, top US investors back us, and we have more customers than we can handle!

Please apply at https://nango.dev/jobs

bastienbeurier··on Show HN: Nango – Open unified API for product integrations
This looks very interesting, congrats! Do you support write-backs & workflows?
bastienbeurier··on Show HN: Nango – Open unified API for product integrations
These are all fair points!

In practice, most customers we serve have use cases that could not be supported by traditional unified APIs, but are still better off not rebuilding an integration infrastructure from scratch.

We also offer professional services to outsource the customization, so you still have an off-the-shelf unified API, but specific to your company.

bastienbeurier··on Show HN: Nango – Open unified API for product integrations
(Nango co-founder here) I'll update the repo readme and other mentions of being open source. Thank you for reporting this. We are not set on the license yet. We want to promote permissive usage, particularly for the auth-related features & contributed integration templates, but we are being mindful of the competitive environment.
bastienbeurier··on Show HN: Nango – Open unified API for product integrations
(Nango co-founder here) Great. The client is just a thin wrapper around our REST API, which can be called from any language. But we plan to release SDKs for all main languages this quarter (including Java). Happy to chat on the community!
bastienbeurier··on Show HN: Nango – Open unified API for product integrations
For example, if you want to synchronize a specific object type, you would get: the authorization for the API, a helper for paginating requests, easy data deduplication, resilient background syncing, rate-limits handled, and a way to get the data that's unified across APIs and use-case: `nango.getRecords('zendesk', 'user123', 'ticket')`. And you benefit from the tooling around: all sync runs are logged, you get alerted on Slack on errors, you can inspect your integration activity per end-user, etc.
bastienbeurier··on Show HN: Nango – Open unified API for product integrations
(Nango co-founder here) That's a great point. You highlight a key limitation of traditional unified APIs and one of the reasons why we started Nango.

There's a lot of subjectivity that goes into unifying functionalities across APIs. Traditional unified APIs must make these subjective decisions for all their customers in a one-size-fits-all manner.

Nango lets you customize integrations & schemas, so you can make these subjective decisions for yourself. The result is a unified API that truly fits your business use case.

Still, some radically diverging API functionalities cannot be unified, which requires some additional API-specific logic to handle. This can be abstracted in our integration scripts, supported by our tooling, instead of living in your main code-base.

bastienbeurier··on Show HN: Nango – Open unified API for product integrations
Ok I see. Indeed, it would be worth specifying what the boundary is in our case. Thank you for the feedback!
bastienbeurier··on Show HN: Nango – Open unified API for product integrations
Thank you!

I agree that getting approved to have an OAuth app is a major pain point (for some APIs). We help customers navigate this and would like to do more in the future (partner with API providers, offer sandbox accounts without approval, and even manage the approvals for customers when possible).

Page 1 of 2Next →