Meet Jellyfish at AWS re:Invent

Intelligence for your AI-native SDLC

Connect 1:1 with our leadership team. Bring your hardest AI questions to CTO Power Hour.

Why stop by

Let's talk about AI impact, not AI activity

Jellyfish is an AWS partner with the AWS AI Competency, helping 1,300+ engineering companies measure and guide their AI transformation. At re:Invent we’re showing our newest releases and meeting with teams who want to tie AI usage to real business outcomes.

On-site all week · Booth #694

Meet with our team

Our leadership team is in Vegas all week. Connect with us 1:1 about AI adoption, token spend, and engineering ROI, and see how leading teams answer those questions in their own data.

 

Spots are limited. We’ll follow up by email to confirm your time.

Wed, Dec 2 · 5–6 PM PT

CTO Power Hour

Get advice from two engineering execs who have seen it all. Shane Sweeney, AWS Executive in Residence and former SVP Technology at FanDuel, spent more than 20 years building and scaling engineering orgs in fast-moving, highly regulated businesses. Adam Ferrari, our SVP Engineering and a long-time Jellyfish customer, has spent his career at the cutting edge of data and analytics.

 

Bring Shane and Adam your hardest challenge: AI ROI, engineering transformation, executive alignment, board narratives, and more. No sign-up needed for this Expo happy hour event. Just grab a drink or snack on AWS and head over to Booth #694 for a chat.

What you’ll see at re:Invent

Intelligence built for the agent era

AI Impact

Measure how AI adoption, assistance, and agents are paying off across your teams. Answer questions like: are the engineers using the most tokens actually shipping significantly more code?

AI ROI

Monitor token and spend analytics. Answer questions like: what is my total cost per PR using humans and agents, and how does it compare to other companies like us?

AI-Native SDLC

Get insights into balancing delivery speed with code quality. Answer questions like: where and how disruptive are the new bottlenecks in our SDLC?