Nicely said. I remember AWS outages (S3, EBS, and RDS) in the early 2010s when their products were younger. But given time to improve each has become more and more resilient.
I'm surprised how most chatbots focus on a 1:1 interaction with the user and the bot. I find chatbots most productive and novel when you allow the one bot to interact with a group of users. For example, deploy bots, where each user can have the bot deploy as well as they can see the chat history to get context on what has been deployed.
Button | NYC | Full time | H1B - yes | Remote - no
Roles: Front-end, Back-end, SRE
I've been a Back-end engineer at Button for 1.5 months and it's the best job I've ever had.
Some specifics:
- a monetizable product that I can get behind
- an amazing team of 16 intelligent, friendly, and experienced individuals across all parts of the organization
- a slew of fun engineering challenges
- a focus on delivering excellence in everything we do
- a team where everyone is deeply committed to making the best product, company, and lives for all of us
- a culture focused around questioning everything
At Button, we think unlocking the interconnection of mobile apps through deep linking is the next big step in the evolution of apps. Deep linking is critical on the web, so why does it barely exist on our mobile apps? Button is focused on tackling this issue, so that your app experience isn’t on-par with the web, but better! Watch our demo video on http://www.usebutton.com/ to learn more.
Come be Engineer #6 at Button! We’re looking for full-stack generalists and iOS and Android pros.
WHAT WE DO: We’re building a platform and loyalty network that connects mobile apps together. We’ve announced partnerships with Uber, Resy, and Tablelist, and we’re just getting started. (The nature of what we do puts us in touch with a lot of growing mobile startups.)
WHO WE’RE AFTER: We’re a merry band of hackers and entrepreneurs, and we’re looking for someone similarly minded. Our backend is a mix of NodeJS and Golang, and we have a rich iOS SDK (and need help building Android).
Ideally you’ll have 5+ years of experience working on hard technical problems in a related environment. But more important is an ability to work through hard problems, a drive to innovate, and an insistence on clean and well-tested code. Our lead engineers are veterans of Google and Venmo.
WHAT YOU’LL DO: As engineer #6, you’ll either specialize in our mobile SDK or our backend. Both are being built to integrate into hundreds of top-tier apps, with millions of users per day, so performance and correctness are absolutely critical. We’ve still got a lot of work to do, so as an early engineer you’ll have a lot of influence over design decisions and directions.
Also....excited to learn a new word, "exegesis"