Stainless | Engineers, EMs, GTM, Former Founders | NYC & SF (onsite) | Full-time
When you npm install openai or pip install anthropic, you’re pulling code generated by Stainless.
We’re building the platform for high-quality, easy-to-use APIs — and companies like OpenAI, Anthropic, and Cloudflare already rely on us.
We’re ~3 years old, ~60 people, with strong revenue, several years of runway, and backing from Sequoia and a16z.
As one of our first 40 engineers, you’ll have real ownership, autonomy to build great products, and a direct hand in shaping the future of how developers consume APIs.
We’re looking for exceptionally productive, thoughtful, and kind people who want to make software development better for everyone.
Stainless | Engineers, EMs, GTM, Former Founders | NYC & SF (onsite) | Full-time
When you npm install openai or pip install anthropic, you’re pulling code generated by Stainless.
We’re building the platform for high-quality, easy-to-use APIs — and companies like OpenAI, Anthropic, and Cloudflare already rely on us.
We’re ~3 years old, ~50 people, with strong revenue, several years of runway, and backing from Sequoia and a16z.
As one of our first 35 engineers, you’ll have real ownership, autonomy to build great products, and a direct hand in shaping the future of how developers consume APIs.
We’re looking for exceptionally productive, thoughtful, and kind people who want to make software development better for everyone.
Learn more & apply → https://stainless.com/jobs?utm_source=YlRQ8pvARO
Stainless | Engineers, EMs, GTM, Former Founders | NYC & SF (onsite) | Full-time
When you npm install openai or pip install anthropic, you’re pulling code generated by Stainless.
We’re building the platform for high-quality, easy-to-use APIs — and companies like OpenAI, Anthropic, and Cloudflare already rely on us.
We’re ~3 years old, ~50 people, with strong revenue, several years of runway, and backing from Sequoia and a16z.
As one of our first 35 engineers, you’ll have real ownership, autonomy to build great products, and a direct hand in shaping the future of how developers consume APIs.
We’re looking for exceptionally productive, thoughtful, and kind people who want to make software development better for everyone.
Stainless | Engineers, EMs, GTM, Former Founders | NYC & SF (onsite) | Full-time
When you npm install openai or pip install anthropic, you’re pulling code generated by Stainless.
We’re building the platform for high-quality, easy-to-use APIs — and companies like OpenAI, Anthropic, and Cloudflare already rely on us.
We’re ~3 years old, ~35 people, with strong revenue, several years of runway, and backing from Sequoia and a16z.
As one of our first 25 engineers, you’ll have real ownership, autonomy to build great products, and a direct hand in shaping the future of how developers consume APIs.
We’re looking for exceptionally productive, thoughtful, and kind people who want to make software development better for everyone.
In lieu of an official comment: the fraud detection that we run on account signup was overly aggressive, especially in response to the massive attention we've seen/new shapes of attacks. We've tuned it down and unbanned a number of accounts. If you're still seeing issues with your account specifically let me know the account at bkrausz at anthropic.com and I'll dig into it.
We haven't seen any issues in the last day+ with SMS delivery. Sometimes Twilio will blackhole a phone number if they suspect abuse, but not sure if that's the case here.
If you want to email bkrausz at anthropic.com with your phone number I'm happy to check logs (assuming it's still not working).
Sorry to hear about that! It sounds like you might have been using an unpinned model version, e.g. `claude-2`, which is designed to automatically get the latest models as they are released. We also support pinned model versions, e.g. `claude-2.0` or `claude-2.1`, which will not be upgraded automatically.
We've been moving away from recommending unpinned versions and are likely to only have pinned versions with future major model releases to avoid this sort of issue.
Can you contact support via https://support.anthropic.com/en/ (button in the bottom right) and mention bkrausz: that'll capture some browser information and I can dig into it from there.
We had a bug we fixed shortly after launch with how we were sending prompts to Claude that was causing worse output. I retried your prompt and it's acting much better now.
Brian and Michael here! We're 2 ex-Stripe engineers (and previously Facebook and YC). We started and helped scale Stripe's support team from just a few people in Gmail to their current size. Now we're bringing those lessons and tools to other startups. We have customers with hundreds of people each scaling their teams with Kenchi. Kenchi is about human-in-the-loop automation, currently targeting support teams. We sit inside your browser to provide a privacy-first approach to team members automating aspects of their work in any environment they sit in. We need to be snappy, resilient to running in different JS environments, and smart about how we tie into different pages to extract information in a robust and resilient way.
We're looking for full-stack devs and designers to join our team of (currently) 3. Founder-types who want to wear many hats, are curious about the innards of different frameworks, and love working across many parts of the system will thrive.
Shoot us an email at [email protected] to say hi! We'd love to hear about something you've worked on before of which you're most proud. Talk soon :)
Brian and Michael here! We're 2 ex-Stripe engineers (and previously Facebook and YC). We started and helped scale Stripe's support team from just a few people in Gmail to their current size. Now we're bringing those lessons and tools to other startups. We have customers with hundreds of people each scaling their teams with Kenchi.
Kenchi is about human-in-the-loop automation, currently targeting support teams. We sit inside your browser to provide a privacy-first approach to team members automating aspects of their work in any environment they sit in. We need to be snappy, resilient to running in different JS environments, and smart about how we tie into different pages to extract information in a robust and resilient way.
We're looking for full-stack devs and designers to join our team of (currently) 3. Founder-types who want to wear many hats, are curious about the innards of different frameworks, and love working across many parts of the system will thrive.
Shoot us an email at [email protected] to say hi! We'd love to hear about something you've worked on before of which you're most proud. Talk soon :)
Don’t fully thank me, I was also the architect of the Transfers API to Connect transition :). There’s a lot I would have done differently there were I doing it again, though much of the complexity (e.g. the async verification webhooks) were to satisfy compliance needs. Hard to say how much easier the v1 could’ve been given the constraints at the time, though I’m very impressed with the work Stripe has done since to make paying people easier (particularly Express).
When designing something like this as a service, the biggest question is what other developers will find easy to use. Every cheap host supports inbound HTTP requests, and most web developers know how to receive them.
Stripe needs to be usable by both the developers building intense, scalable, reliable systems and the people teaching themselves to code in a limited context on a limited platform.
I was responsible for Stripe's API abstractions, including webhooks and /events, for a number of years. Some interesting tidbits:
Many large customers eventually had some issue with webhooks that required intervention. Stripe retries webhooks that fail for up to 3 days: I remember $large_customer coming back from a 3 day weekend and discovering that they had pushed bad code and failed to process some webhooks. We'd often get requests to retry all failed webhooks in a time period. The best customers would have infrastructure to do this themselves off of /v1/events, though this was unfortunately rare.
The biggest challenges with webhooks:
- Delivery: some customer timing out connections for 30s causing the queues to get backed up (Stripe was much smaller back then).
- Versioning: synchronous API requests can use a version specified in the request, but webhooks, by virtue of rendering the object and showing its changed values (there was a `previous_attributes` hash), need to be rendered to a specific version. This made upgrading API versions hard for customers.
There was constant discussion about building some non-webhook pathway for events, but they all have challenges and webhooks + /v1/events were both simple enough for smaller customers and workable for larger customers.
Kenchi | San Francisco / Remote (North American Timezones) | https://kenchi.com/jobs
Brian and Michael here! We're 2 ex-Stripe engineers (and previously Facebook and YC). We started and helped scale Stripe's support team from just a few people in Gmail to their current size. Now we're bringing those lessons and tools to other startups. We have customers with hundreds of people each scaling their teams with Kenchi.
Kenchi is about human-in-the-loop automation, currently targeting support teams. We sit inside your browser to provide a privacy-first approach to team members automating aspects of their work in any environment they sit in. We need to be snappy, resilient to running in different JS environments, and smart about how we tie into different pages to extract information in a robust and resilient way.
We're looking for full-stack devs and designers. Founder-types who want to wear many hats, are curious about the innards of different frameworks, and love working across many parts of the system will thrive.
Shoot us an email at [email protected] to say hi! We'd love to hear about something you've worked on before of which you're most proud. Talk soon :)
Brian, Michael, and Kevin here! We're 3 ex-Stripe engineers (and previously Facebook and YC). We started and helped scale Stripe's support team from just a few people in Gmail to their current size. Now we're bringing those lessons and tools to other startups. We have customers with hundreds of people each scaling their teams with Kenchi.
Kenchi is about human-in-the-loop automation, currently targeting support teams. We sit inside your browser to provide a privacy-first approach to team members automating aspects of their work in any environment they sit in. We need to be snappy, resilient to running in different JS environments, and smart about how we tie into different pages to extract information in a robust and resilient way.
We're looking for full-stack devs and design. We're 3 people now, so founder-types who want to wear many hats, are curious about the innards of different frameworks, and love working across many parts of the system will thrive.
Shoot us an email at [email protected] to say hi! We'd love to hear about something you've worked on before of which you're most proud. Talk soon :)
When you npm install openai or pip install anthropic, you’re pulling code generated by Stainless.
We’re building the platform for high-quality, easy-to-use APIs — and companies like OpenAI, Anthropic, and Cloudflare already rely on us.
We’re ~3 years old, ~60 people, with strong revenue, several years of runway, and backing from Sequoia and a16z.
As one of our first 40 engineers, you’ll have real ownership, autonomy to build great products, and a direct hand in shaping the future of how developers consume APIs.
We’re looking for exceptionally productive, thoughtful, and kind people who want to make software development better for everyone.
Learn more & apply → https://stainless.com/jobs?utm_source=YlRQ8pvARO