diff --git a/src/pages/blog/2026-09-27-what-becoming-a-graphql-ambassador-at-17-taught-me/apidays-india-booth.jpg b/src/pages/blog/2026-09-27-what-becoming-a-graphql-ambassador-at-17-taught-me/apidays-india-booth.jpg
new file mode 100644
index 0000000000..bbb35c8d86
Binary files /dev/null and b/src/pages/blog/2026-09-27-what-becoming-a-graphql-ambassador-at-17-taught-me/apidays-india-booth.jpg differ
diff --git a/src/pages/blog/2026-09-27-what-becoming-a-graphql-ambassador-at-17-taught-me/apidays-india-cheatsheets.jpg b/src/pages/blog/2026-09-27-what-becoming-a-graphql-ambassador-at-17-taught-me/apidays-india-cheatsheets.jpg
new file mode 100644
index 0000000000..894f6610d6
Binary files /dev/null and b/src/pages/blog/2026-09-27-what-becoming-a-graphql-ambassador-at-17-taught-me/apidays-india-cheatsheets.jpg differ
diff --git a/src/pages/blog/2026-09-27-what-becoming-a-graphql-ambassador-at-17-taught-me/apidays-india-team.jpg b/src/pages/blog/2026-09-27-what-becoming-a-graphql-ambassador-at-17-taught-me/apidays-india-team.jpg
new file mode 100644
index 0000000000..4284b546ff
Binary files /dev/null and b/src/pages/blog/2026-09-27-what-becoming-a-graphql-ambassador-at-17-taught-me/apidays-india-team.jpg differ
diff --git a/src/pages/blog/2026-09-27-what-becoming-a-graphql-ambassador-at-17-taught-me/graphql-virtual-talk.png b/src/pages/blog/2026-09-27-what-becoming-a-graphql-ambassador-at-17-taught-me/graphql-virtual-talk.png
new file mode 100644
index 0000000000..1e8450d044
Binary files /dev/null and b/src/pages/blog/2026-09-27-what-becoming-a-graphql-ambassador-at-17-taught-me/graphql-virtual-talk.png differ
diff --git a/src/pages/blog/2026-09-27-what-becoming-a-graphql-ambassador-at-17-taught-me/index.mdx b/src/pages/blog/2026-09-27-what-becoming-a-graphql-ambassador-at-17-taught-me/index.mdx
new file mode 100644
index 0000000000..26d4e9a0a3
--- /dev/null
+++ b/src/pages/blog/2026-09-27-what-becoming-a-graphql-ambassador-at-17-taught-me/index.mdx
@@ -0,0 +1,107 @@
+---
+title: "What Becoming a GraphQL Ambassador at 17 Taught Me"
+tags: ["community", "events", "ambassador-stories"]
+date: 2026-09-27
+byline: "Ayush More"
+---
+
+> The following story was written by Ambassador Ayush More, looking back
+> on the first months in the GraphQL Ambassador Program.
+> GraphQL Ambassadors are trusted go-to community leaders
+> driven by a passion for GraphQL projects, striving
+> to nurture the growing GraphQL community through collaboration,
+> education and outreach. Find out more about the [Ambassador Program in the community pages](https://graphql.org/community/ambassadors/).
+
+When I got the email saying I was accepted as a GraphQL Ambassador, I had to read it a few times before I believed it. I was 17, sitting at home in Mumbai, and I was now part of the GraphQL Foundation's Ambassador program. I was really happy, and honestly a bit shocked.
+
+Once I actually started, I learned a few things pretty fast.
+
+## How I got here
+
+I made my first open source contribution when I was 16. It was a small docs fix on Meshery, a CNCF project. I had no idea what I was doing, and half of my PR description was me saying sorry in case I got something wrong. The maintainers still replied and gave me feedback, so I kept contributing.
+
+Over time I contributed to 7 CNCF projects. I became an Org Member at PipeCD and got a CNCF Travel Scholarship. Slowly, I started to feel like I belonged there.
+
+CNCF is huge, though. There are more than 200 projects, and it takes months just to understand how everything fits together. I wanted to be part of a smaller community too.
+
+GraphQL felt like that. The Foundation is small enough that you can get to know the people. The spec work takes its time, and people ask hard questions about how APIs should be designed. I liked that a lot.
+
+So when the Ambassador program opened up, I applied, and I got in.
+
+## Learning how GraphQL works
+
+Being an Ambassador doesn't mean you already know how to contribute to the project. I learned that quickly.
+
+I thought my CNCF experience would carry over, but every community works in its own way. In GraphQL, a lot of the work happens in [working groups](https://graphql.org/community/contribute/development/). The future of the spec is discussed in open meetings that anyone can join. I was used to just opening a PR and seeing what happens, so this took some getting used to.
+
+I was an Ambassador for a while before I made my first real contribution to a GraphQL repo. Knowing how a project works on the inside takes time. I'm still learning it.
+
+## What I didn't tell people
+
+When I got in, I told people I was now part of the GraphQL Foundation. I didn't mention that I was also googling "what is a working group", trying to figure out what TSC means, and reading the spec for the first time wondering why it looked nothing like normal docs. I felt like someone who walked into the wrong classroom and decided to stay.
+
+## What I do day to day
+
+Most of it is pretty normal stuff.
+
+I join TSC calls and listen, even when I don't understand everything yet. I read working group notes to learn how decisions get made. I made a short video series on LinkedIn to explain GraphQL to people who only know it as a query language. I also write blog posts to help people who are new to GraphQL.
+
+Sometimes it also means standing at a booth in a GraphQL t-shirt, or showing people their first GraphQL query on a live call.
+
+## At the GraphQL booth at APIdays India
+
+