“I worked closed with John from 2018-2020 at Google Cloud. I was a sales rep and he was a sales engineering manager leading a team of sales engineers. Google Cloud was relatively early in it's growth curve at the time and the organization's size and revenue grew tremendously during this time. John worked at AWS and Azure when those organizations were going through similar relatively early growth stages. Therefore, John's experience with breaking into organizations and foresight to anticipate potential objections was extremely valuable for my colleagues and I. While his experience is great, what I most appreciated about working with John was his attitude. He always reminded us to keep doing the right things, put the customer first, and wasn't afraid to dive in and work with the sales reps and sales engineers rather than simply telling us what to do. As an organizational leader, John was always thinking one step ahead about scale. He would invest a lot of time off hours to figure out how to build solutions that would help the sellers be more efficient and get access to the data we needed to help bring compelling value to our clients. Examples include building tools to help us forecast better, size workloads quickly, and last but not least build a better sense of culture/community/we are in it togetherness. On a more personal note, John was a friend and mentor when I needed it most. My first 18 months or so at Google were difficult in terms of seeing results, but John always reminded me to focus on what I can control and praise me for my long term mindset when I needed it the most. For organizations looking for a hands on, positive, customer focused experienced technical sales leader who always is thinking about enabling scale, I would highly recommend John Mancuso.”
Experience
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
Education
-
-
-
-
Licenses & Certifications
Recommendations received
2 people have recommended John
Join now to viewOther similar profiles
Explore more posts
-
StreamNative
🚨 Data streaming is due for its Iceberg moment. In this new post, our CEO, Sijie Guo, and Principal Sales Engineer, David Kjerrumgaard, explore why tightly coupled streaming architectures like Apache Kafka are hitting their limits—and what the future looks like. 👉https://hubs.ly/Q03tR4QS0 Drawing lessons from the lakehouse revolution (e.g., Apache Iceberg), they propose a three-layer architecture for streaming: 🔹 Data – Durable, scalable object storage 🔹 Metadata – Decoupled and authoritative 🔹 Protocol – Stateless, multi-interface routing Streaming should be as modular, cloud-native, and vendor-neutral as modern analytics: 📉 Cut costs by up to 90% ⚙️ Evolve each layer independently 🔓 Enable open, multi-tool access Projects like #ApachePulsar and #StreamNativeUrsa are already paving the way!🌟 #StreamingData #Kafka #Iceberg #Lakehouse
-
RisingWave
It’s been the headline of the week: 𝐈𝐁𝐌 𝐢𝐬 𝐚𝐜𝐪𝐮𝐢𝐫𝐢𝐧𝐠 𝐂𝐨𝐧𝐟𝐥𝐮𝐞𝐧𝐭. A big question on everyone’s mind is how this will reshape the streaming landscape. In Yingjun Wu’s words, this acquisition does not mark the end of anything! It only accelerates a shift that was already in motion. The whole data infra stack is moving upward, away from raw plumbing and toward products that deliver visible value. This shift shows up in three places: ▪️ How analytics vendors treat ingestion ▪️ How Apache Iceberg changes the role of Kafka ▪️ How Kafka itself has to evolve. For details, read: https://lnkd.in/gXUMRyPA #risingwave #streamprocessing #datainfra
-
Abhay Reddy
Open source moves at its own pace. In this Perspectives on PostgreSQL 18 clip, Jacob Champion describes the four-year path to PostgreSQL’s new OAuth feature and how EDB supports the collaborative work that powers releases like PG 18. See the full discussion for more on OAuth, testing, and what’s next for PG 19: https://bit.ly/49RgEMP #EDBPostgresAI #PG18 #PostgreSQL18 #PGCommunity #Oauth #OpenSource #DeveloperCommunity
-
Mike Vitale
If your streaming workflow needs precise business logic, custom modules are the answer. This Thursday, Ian Zenoni and I are digging into how to extend Wowza Streaming Engine through scalable, real-world implementations. We’ll cover when modules make sense, walk through a practical example of custom metadata injection, and share hard-earned tips on testing, debugging, and running modules in production. If you’ve ever said “I just need Engine to do one more thing,” this session is for you. I will, of course, be dressed in my finest sports coat and strongly encourage audience participation. Bring your questions.
-
Marc Brooker
People often ask me about the differences in architecture between Amazon Dynamo (the 2007 SOSP paper), DynamoDB (the AWS serverless NoSQL database), and Aurora DSQL (the AWS serverless SQL databases). I captured the key points on durability, high availability, programming model, and trade-offs in my blog: https://lnkd.in/gkMG_tVD TL;DR: Despite the shared name, Dynamo and DynamoDB have little in common architecturally, and make very different trade-off decisions.
8 Comments -
Andi Gutmans
Great news for Spanner and BigQuery users. Datastream now provides a seamless, serverless bridge from Spanner’s transactional power to the high-performance analytical capabilities of BigQuery and BigLake. Get the most scalable and available database that runs Google with BigQuery and BigLake’s serverless AI-Native Lakehouse!
3 Comments -
Viktor Kessler
Most teams don’t fail at Iceberg because of the tech — they fail because of everything around it. You can have the best format, fastest engine, and cleanest tables… and still sink your Lakehouse if your tactics and strategy don’t align. On October 16, Yingjun Wu and I will talk about why Iceberg adoption can be tricky — and how not to mess it up. Expect real stories, tactical advice, and maybe one or two jokes about data teams turning schema evolution into a full-time job. 🧊 This isn’t just about config files — it’s about mindset, ownership, and the reality of running open data infra in production. 🎟️ Save your seat: https://luma.com/fga9usb8 #Lakehouse #Iceberg Apache Iceberg #DataEngineering Vakamo RisingWave
1 Comment -
Chiron
Chiron’s next generation observability approach just got another validation. Confluent’s new Real Time Context Engine shows that the industry is finally realizing that data infrastructure needs a fundamental rethink. Simply layering new technology on top of the old foundation will not work. When it comes to observability, even existing streaming platforms face these same limits. Chiron has been working closely with a few beta partners to use modern tech to provide better MTTR at reduced TCO, and we’re open to bringing more on board. www.chironvison.ai The world is gradually recognizing that real progress starts with rethinking how data moves, connects, and provides context in real time. Confluent: https://lnkd.in/ggYpe5R5
Explore top content on LinkedIn
Find curated posts and insights for relevant topics all in one place.
View top content