Sam Scott (cofounder/CTO of Oso) is on an epic quest for programmable authorization, and thinks we can learn a thing or two from web frameworks when building authorization systems.
Wednesday, February 15, 2023
1:30 PM - 2:45 PM EDT
As programmers, many of us got indoctrinated into ideas like “Convention over Configuration” and “Provide Sharp Knives” early on. But authorization – a problem as old as software and one that’s core to no one’s domain – is still anything but magical.
Sam Scott (cofounder/CTO of Oso) is on an epic quest for programmable authorization, and thinks we can learn a thing or two from web frameworks when building authorization systems.
During this tech talk, Sam will explain:
- Why an authorization system needs to be opinionated but flexible
- Why it’s a tricky balance to achieve
- And what happens if you get it right.
He’ll also demo Oso Cloud, a batteries-included authorization system we’ve built for application authorization.
Stay for a technical Q&A, demos from Oso engineers, special swag, and a Polar policy puzzle (there will be prizes).
See you there!
As programmers, many of us got indoctrinated into ideas like “Convention over Configuration” and “Provide Sharp Knives” early on. But authorization – a problem as old as software and one that’s core to no one’s domain – is still anything but magical.
Sam Scott (cofounder/CTO of Oso) is on an epic quest for programmable authorization, and thinks we can learn a thing or two from web frameworks when building authorization systems.
During this tech talk, Sam will explain:
- Why an authorization system needs to be opinionated but flexible
- Why it’s a tricky balance to achieve
- And what happens if you get it right.
He’ll also demo Oso Cloud, a batteries-included authorization system we’ve built for application authorization.
Stay for a technical Q&A, demos from Oso engineers, special swag, and a Polar policy puzzle (there will be prizes).
See you there .
Oso | Engineering Manager, Software Engineer | New York City (NYC) | Onsite or Remote
Old problem, new $25B+ market
Companies like AWS, Stripe, and Twilio have demonstrated that if a technology is not core to your value proposition, you should offload it. Still, every engineering team builds and rebuilds one piece: *authorization*, how you control who has access to what in your app. You’ve probably started with something quick 'n dirty – some IF statements and roles in a database...until you need to add more features, and more features. And inevitably you band-aid onto this system until you have to do a big refactor. Have you seen this before?
We're changing this picture and in doing so, we are creating the next $25B+ dollar market: the authorization market. We’re on a mission to create the global standard for authorization. Our vision is that in 10 years engineers will spend 1/10 the time and brainpower they spend on authorization today.
Why now?
This is a once-in-a-career opportunity to join a company at a stage late enough that the problem and solution are de-risked, but early enough that you can shape the product, company, and the market.
We are based in NYC and hiring folks remote or onsite.
Oso | Engineering Leader, Software Engineer, Developer Experience Engineer | New York City (NYC) | Onsite or Remote
Old problem, new $25B+ market
Companies like AWS, Stripe, and Twilio have demonstrated that if a technology is not core to your value proposition, you should offload it. Still, every engineering team builds and rebuilds one piece: *authorization*, how you control who has access to what in your app. You’ve probably started with something quick 'n dirty – some IF statements and roles in a database...until you need to add more features, and more features. And inevitably you band-aid onto this system until you have to do a big refactor. Have you seen this before?
We're changing this picture and in doing so, we are creating the next $25B+ dollar market: the authorization market. We’re on a mission to create the global standard for authorization. Our vision is that in 10 years engineers will spend 1/10 the time and brainpower they spend on authorization today.
Why now?
This is a once-in-a-career opportunity to join a company at a stage late enough that the problem and solution are de-risked, but early enough that you can shape the product, company, and the market.
At Oso, we give the written word the same level of attention and respect as code, because we know that our audience — developers — values high quality writing. Every engineer on the team writes. And if you are an engineer that can write well, this role is for you – you will be celebrated, respected (and paid the same as the other engineers on the team).
We are based in NYC and hiring folks remote or onsite.
Oso | Engineering Leader, Software Engineer, Developer Experience Engineer | New York City (NYC) | Onsite or Remote
# *Old problem, new $25B+ market*
Companies like AWS, Stripe, and Twilio have demonstrated that if a technology is not core to your value proposition, you should offload it. Still, every engineering team builds and rebuilds one piece: *authorization*, how you control who has access to what in your app. You’ve probably started with something quick 'n dirty – some IF statements and roles in a database...until you need to add more features, and more features. And inevitably you band-aid onto this system until you have to do a big refactor. Have you seen this before?
We're changing this picture and in doing so, we are creating the next $25B+ dollar market: the authorization market. We’re on a mission to create the global standard for authorization. Our vision is that in 10 years engineers will spend 1/10 the time and brainpower they spend on authorization today.
*Why now?*
This is a once-in-a-career opportunity to join a company at a stage late enough that the problem and solution are de-risked, but early enough that you can shape the product, company, and the market.
At Oso, we give the written word the same level of attention and respect as code, because we know that our audience — developers — values high quality writing. Every engineer on the team writes. And if you are an engineer that can write well, this role is for you – you will be celebrated, respected (and paid the same as the other engineers on the team).
We are based in NYC and hiring folks remote or onsite.
Oso | Engineering Leader, Software Engineer, Developer Experience Engineer, Product Leader | New York City (NYC) | Onsite or Remote
# **Old problem, new $10B+ market**
Companies like AWS, Stripe, and Twilio have demonstrated that if a technology is not core to your value proposition, you should offload it. Still, every engineering team builds and rebuilds one piece: **authorization**, how you control who has access to what in your app. You’ve probably started with something quick 'n dirty – some IF statements and roles in a database...until you need to add more features, and more features. And inevitably you band-aid onto this system until you have to do a big refactor. Have you seen this before?
We're changing this picture and in doing so, we are creating the next $10B+ dollar market: the authorization market. We’re on a mission to create the global standard for authorization. Our vision is that in 10 years engineers will spend 1/10 the time and brainpower they spend on authorization today.
**Why now?**
This is a once-in-a-career opportunity to join a company at a stage late enough that the problem and solution are de-risked, but early enough that you can shape the product, company, and the market.
At Oso, we give the written word the same level of attention and respect as code, because we know that our audience — developers — values high quality writing. Every engineer on the team writes. And if you are an engineer that can write well, this role is for you – you will be celebrated, respected (and paid the same as the other engineers on the team).
We are based in NYC and hiring folks remote or onsite.
