Code Story episode
S7 Bonus: The Twilio for PDFs: Converting Messy Business Documents into Developer APIs with Josh Lewis, Co-Founder & CEO of Sensible
Sep 8, 2022 · Season 7 · 31 min
Easy data extraction from your PDF's
Josh Lewis was fascinated by computers in the late 80's / early 90's. In the early days, he was neighborhood tech support, fixing people's computers around the block. He quickly moved into programming, but he moved off from technology in college, targeting philosophy and going to grad school. In doing research with a computer science component, he was pulled back into tech and went to work in Palo Alto. Outside of tech, he's a Dad taking care of his young family. Also, he plays competitive drafts of Magic the Gathering, along with Tennis.
At his last company, Josh experienced a recurring problem in spades, where account managers were spending large amounts of time with data entry of standardized forms and information. When he looked for the Twilio for PDF's, he couldn't find a tool to solve his problem.
This is the creation story of Sensible.
Sponsors
AirbyteDopplerHost.ioIPInfomablLinks
Website: https://www.sensible.so/LinkedIn: https://www.linkedin.com/in/joshlewisml/
Checkout our episode stacks on Stacklist! https://stacks.codestory.co/
Advertising Inquiries: https://redcircle.com/brands
Privacy & Opt-Out: https://redcircle.com/privacy
More episodes
Keep listening
Topics
Explore related conversations
Technical due diligence checklist for startups
A technical due diligence checklist for founders and investors: what reviewers examine across architecture, security, team and process, and how to prepare before a raise.
Fractional CTO vs full-time CTO: which does your startup need?
A practical comparison of a fractional CTO and a full-time CTO: cost, scope, when each makes sense, and the questions to ask before you hire either one.
CTO vs VP of Engineering: how the two roles actually differ
CTO vs VP of Engineering explained: who owns architecture, who owns delivery, when to split the roles, and how to avoid the overlap that breaks engineering teams.