Code Story episode
S7 Bonus: Making the Operating System Multiplayer: From a $13M Collaboration Engine to OpenAI with Alex Embiricos of Remotion
Jan 26, 2023 · Season 7 · 28 min
Remote engineers working remote
Alex Embiricos comes from an interesting background, having grown up all over the place - between Asia, the Caribbean, and Switzerland. He came to the states for college, and found his way into software after a stint in Aerospace. Ultimately, he found himself interested in the intersection between business and building technology. During his career, he spent a lot of time working at Dropbox, followed up by starting a company with his friends. Outside of tech, he loves to play Badminton, and when asked what his favorite food was, well... it is his Mom's food.
After his prior startup failed, Alex still had the urge to build something. He met his now co-founder, and they started to explore ways to connect people online. What they noticed was that most video chat tools were created around a presentation, but not around solving problems together.
This is the creation story of Remotion.
Sponsors
AirbyteDopplerHost.ioIPInfomablSupportZebraLinks
Website: https://remotion.com/LinkedIn: https://www.linkedin.com/in/embirico/
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.