From planning to delivery, Jellyfish combines system and sentiment data to uncover productivity blockers, maximize engineering impact and drive better business outcomes.
Billy Robins, Head of Partnerships, shares details on Jellyfish and what it’s like to work there.
In This Video
We discuss:
- What does Jellyfish do?
- Their use of AI
- How the platform works
- The culture at Jellyfish
- Why now is a great time to join Jellyfish
Video Transcript
Here is the transcript from the conversation between Keith and Billy Robins from Jellyfish, edited for clarity and readability.
Keith: Billy, thanks so much for joining us.
Billy: Hey Keith, thanks for having me on.
Keith: Really appreciate it. I’m excited to talk to you because we’re going to talk about Jellyfish, which is one of the top tech companies in the Boston tech scene. It’s a company that has been growing year after year. For those not familiar with the company, what does Jellyfish do?
Billy: Jellyfish has been around a little over seven years. We help connect engineering to the business and help companies drive better business results from their limited resource of software developers. There is the old Andreessen comment—which I’m sure I’m not the first person on VentureFizz to reference—that every company is a software company these days. We provide the telemetry to help companies like DraftKings, Keller Williams, Blue Yonder, and 700-plus others drive better business results from the software they are shipping.
Keith: Every company is a software company now, and software has radically changed since AI. Every engineer is using some form of AI tool to be more productive. What is your lens as it relates to that?
Billy: We’ve certainly seen that shift in the market over the last couple of years, but it seems to get faster every month in 2025. I think our customers see two systems in play for every company shipping software.
System one is what you put into production. You instrument this finely and buy things like DataDog, CloudWatch, or Grafana to understand if the software is up. That is a more legacy “cost center” view.
System two—where Jellyfish lives—is the people and processes building system one. This is where you unlock value. Historically, that involved GitHub, GitLab, and issue tracking, but now it includes AI. Jellyfish provides transparency into which developers are using AI and who is using it effectively. Are you shipping faster? In which use cases? There is also the question of quality and security: if AI is writing the code, is it secure? Jellyfish brings telemetry to all of those areas.
Keith: Looking at the history of the company and past conversations with your CEO, Andrew Lau, there was always this idea that marketing and sales were measured by data, but that wasn’t always the case for software engineering before Jellyfish. How does it all work?
Billy: I’m not a co-founder—I’m just lucky enough to work with Andrew. Jellyfish ingests data from all the applications engineers use regularly. We have a system-level view of Git, issue tracking (like Linear), and AI tools (like Cursor, Claude, or Augment).
We bring all that into our patented algorithms to see what percentage of work is innovation versus tech debt or bug fixes. We see how long it takes an engineer to deliver projects and can slice and dice that data. We have more customization coming in the year ahead as we work with more enterprise-oriented customers who want to configure their own dashboards for visibility.
Keith: What is the latest at Jellyfish? What should people be aware of?
Billy: We spent all of last year working with AI partners like Amazon Q, GitHub Copilot, Augment, and Cursor. We are starting to see this notion of “hybrid teams” where engineers and agents collaborate. We are providing more visibility into agentic performance and alerts around how agents are working.
Because there is an increasing “morass” of data, we are using AI to create executive summaries. This makes it easier for a CTO to articulate to the CEO, CFO, and the board exactly what is happening with the engineering team and how work is progressing. The fundamental question of what outcomes engineering is driving persists, even if the methods change.
Keith: Jellyfish continues to grow. What’s it like working there, and what is the culture like?
Billy: It’s a great culture. I’m based in San Francisco—I’ve been out here 20-plus years—and this is my first time working for a Boston-based company. It is certainly different than a Bay Area company, especially in a post-ZIRP world. It is a very bottoms-up and collaborative culture, which comes from the founders. They allow the team to experiment.
About 60% of the crew is in Boston or the surrounding area, so there is a group in the office regularly. For remote folks like myself, we come in for big events like the company kickoff, the summer picnic, and other events throughout the year. It’s a good blend of office culture and remote flexibility.
Keith: Top-tier talent always has opportunities regardless of market conditions. Why is now the ideal time to join Jellyfish?
Billy: This wave of AI is radically altering how software is developed and how all knowledge workers work. Jellyfish provides the telemetry and insights to help market leaders figure out the right tools to use to advance their business. Jellyfish is the market leader in that space. We’re excited for the year ahead and would love to get more top-tier talent on board for the journey.
Keith: If you are interested in exploring opportunities at Jellyfish, go to their company page on VentureFizz at venturefizz.com/jellyfish. Billy, thanks so much for bringing us up to speed.
Billy: This was awesome. Thanks for having me on, Keith. Best of luck in the year ahead.
