# Erik Munson > Founding Engineer @ Day AI | The CRM for AI Native Companies Location: San Francisco, California, United States Profile: https://flows.cv/erikmunson 20+ years of building things on the web. Everybody's gotta do something, I build business and productivity software. I like the feeling I get when somebody's day is a bit better because of what I (or my teams) built. I'm a generalist that tends to find new things to learn no matter how hard I try to stay in my lane. I've spent time at companies of all shapes and sizes, from seed-stage startups with no product to public companies responsible for a large share of the world's internet traffic. Technically, I've worked on visual/product design, client-side UIs, large-scale distributed backends, cloud infrastructure, and a whole lot in between. I've been an individual contributor, built + led teams, and executed projects across large organizations. While I tend to enjoy smaller companies and earlier stage projects, I've found something interesting and fun in all of it. I've been incredibly lucky in my career — feels like I've been in the right place at the right time more often than not. Most recently I've had the chance to reunite with some old friends to build Day AI, and help AI native companies get and stay customer obsessed. Having lots of fun, and just getting started. ## Work Experience ### Founding Engineer @ Day AI Jan 2023 – Present | San Francisco, California, United States Day AI is the Customer Intelligence solution that puts customers at the center of every decision by reimagining CRM for the AI Age. We combine the features of a Meeting Assistant, CRM, and Knowledge Base into a single unified solution that replaces the manual, complicated interfaces of legacy CRM, and keeps you connected to what customers want. ### Engineering Manager, End Developer Delivery @ Netflix Jan 2023 – Jan 2023 | Los Gatos, California, United States After my previous team launched a re-imagined CI/CD experience within Netflix and drove it to product-market fit, I worked with other engineering leaders to re-organize the Delivery group around scaling adoption of the new experience and expanding it to more of Netflix's engineering ecosystem. As a result, I took over the newly formed End Developer Delivery team which consolidated ownership of all the major developer-facing experiences for CI/CD and aimed to unify them into a single, seamless workflow. ### Engineering Manager, Managed Delivery @ Netflix Jan 2020 – Jan 2023 | Los Gatos, California, United States I led the Managed Delivery team, which aimed to rethink how Netflix interacted with continuous delivery. The team operated as a startup within the existing Netflix Platform organization, experimenting with a new CI/CD experience in close partnership with representative customers across the major engineering functions. We also regularly met with industry peers to drive a common language and set of concepts for abstracted or "managed" CI/CD at FAANG scale. After some research and development, we launched in closed beta and eventually found product-market fit within several large engineering departments. By the time the team was spun down to move into a more scale-up focused configuration, the product was the default for new services at Netflix and was growing at over 100% YoY. ### Senior Software Engineer @ Netflix Jan 2018 – Jan 2020 | Los Gatos, California, United States I worked on Spinnaker, Netflix's deployment, cloud infrastructure management, and pipelining/orchestration platform used by engineers across the company. My feature development focus was on the UI, but I was also on the PagerDuty rotation for the overall system including a constellation of Java services that ranged from a Netflix-scale cloud infrastructure cache to the core orchestrator that ran workflow steps in a JSON-based graph/DAG specification. Spinnaker was open sourced in 2015 so you can read all about the services involved in its operation on the docs site (link below). That rotation also included Slack-based user support for all the engineers at Netflix who needed help, ranging from setting up deployments correctly to helping remediate critical streaming outages. The time I spent in this role was incredibly challenging, but was also one of the most illuminating and educational experiences I've had in my career. Staffing user support and deep diving with engineering teams across the company was effectively a way to do a tour of duty with every product function at Netflix, and that combined with holding the pager for Spinnaker gave me a 2 year crash course in what it looks like to build distributed systems at Netflix scale. ### Engineering @ Streak.com Jan 2017 – Jan 2018 | San Francisco, California While working on email client extensions at HubSpot, I came upon the work Streak was doing with a developer-facing project called InboxSDK. They had accomplished an incredible amount of deep work to manage UI injection into Gmail, including robustness to Gmail UI deployments that could break extension code, and automatic reactive handling of UI transitions/interactions. Most impressively, they'd made a lot of progress on the problem of coordinating UI injection across the many different email extensions a user might have installed — effectively a distributed consensus problem — which had been one of the most frustrating parts of email extension development for years. We quickly transitioned much of HubSpot's bespoke extension code to InboxSDK, and as I got to know the Streak team better I decided it would be an exciting adventure to move to San Francisco and go even deeper on some of the tough platform engineering work I'd already gotten a taste of. What ensued was an incredibly learning-packed year, I probably went deeper on the browser platform/runtime during this time in my career than I'll ever go again. The SDK also supported millions of email clients through companies like Dropbox and Giphy using it for their extensions, which helped prepare me for the scale I would soon be working at in the next chapter of my work. ### Technical Lead @ HubSpot Jan 2014 – Jan 2017 | Cambridge, MA I was hired to join a very small 'startup-within-a-startup' team, kept largely separate from the rest of the company. Together we built the first version of what became HubSpot's Sales Hub and CRM product lines. At the time HubSpot was getting ready for an IPO fueled by the success of their marketing product suite, and the executive team wanted to invest in the next major pillar of the company's growth. A lot of our early work launched at HubSpot's 2014 Inbound conference, and over the next couple of years growth was extremely rapid. The tiny early stage team turned into a larger one over time, and we eventually integrated back into the overall HubSpot product organization. While I played a fairly generalist role, a big focus for me was the Gmail and Outlook email client extensions that brought CRM and Sales features directly into users' email workflows. Augmenting email clients with custom UI and background workers is notoriously challenging and deep work, with high reliability expectations. Managing a large install base (hundreds of thousands) of long-lived stateful clients where the cost of a bad deployment could be several days of degraded service taught me a lot about the fundamentals of reliability and distributed computing. Later in my time at HubSpot I led a team focused on making it easy for product teams across the company to bring their features into users' email clients, building on the earlier versions of our email integrations. We shipped a lot of cool developer SDKs and expanded support to the web-based Outlook365 client in addition to Gmail and Outlook desktop. This began a multi-year detour into the world of platform engineering and developer tools. ### Founding Engineer @ WHOOP Jan 2013 – Jan 2014 | Boston, MA I joined WHOOP as they were closing their seed round in 2013. At the time the hardware part of the product was a toaster-sized prototype the founders were lugging around to investor meetings, and we were working out of a tiny shared office space in the Harvard Innovation Lab. I fondly remember us all wearing uncomfortable chest-strap heart rate monitors to generate test data for algorithms and web UIs, while the hardware team worked as fast as they could to turn the tabletop prototype into what became the first WHOOP strap. I worked directly with the founders and our UX designer to help design and build the first version of the web app in Angular, D3, and Node.js. During that time, we worked out how to represent many of the core concepts that still exist in the product today. As is always the case at companies in their earliest stage, I also did plenty of other things ranging from helping out with branding revision/selection to assembling furniture in our first real office in Fenway. ### Co-Founder @ Ipsum Creative Jan 2005 – Jan 2013 | Albuquerque, NM I got into what was then called “web design” with my co-founder in 2005, when we built a website with the original WordPress Kubrick theme (!!) and realized it was a lot of fun and people would pay us to do it. Next came some Flash sites (lots of long intro animations as was fashionable at the time). Eventually we were doing steady contract work with local small businesses and startups we met online, building full-service websites, branding/logo packages, and marketing materials. 8 years was a very long time in web development in the 2000s: eventually WordPress and Flash turned into JavaScript frameworks + Node backends, Photoshop + Illustrator turned into Sketch, and small businesses had more options for building websites that didn’t require a dedicated web development team or knowledge of coding. Eventually we moved on to other things and shut the shop down. I was unusually lucky to be at just the right place, at just the right time to learn a broad set of technology, sales/marketing, and business skills all while making a living independently. ## Contact & Social - LinkedIn: https://linkedin.com/in/erikmunson - Website: http://erikmunson.com --- Source: https://flows.cv/erikmunson JSON Resume: https://flows.cv/erikmunson/resume.json Last updated: 2026-04-05