On 15 October 2026, I attended Config India 2026 in Bengaluru, Figma's conference bringing together people interested in design, technology, and the future of building products.
As a second-year college student involved in the AWS student-builder community, attending an event like this was an opportunity to learn beyond the classroom, explore emerging tools, and connect with people across the technology ecosystem.
But one small interaction during the event stayed with me for a different reason.
"How Did You Get the Pass?"
While talking to someone at the event, I was asked a simple question: "How did you get the pass?"
Looking around, I got the impression that many attendees were graduates, experienced professionals, or people already working in the industry. I was there as a second-year student, still exploring, learning, and building my own projects.
I explained that I was the founder of GunnerJyo, my personal brand at gunnerjyo.dev .
For me, that moment represented something important. You do not necessarily have to wait until graduation or your first job to start building your identity in the technology ecosystem. You can start creating projects, developing skills, participating in communities, and establishing your presence while you are still a student.
GunnerJyo is part of that journey for me. It represents my interest in technology and my effort to build things, share what I learn, and grow through practical experience.
Attending Config was another opportunity to step outside my usual environment and experience the wider industry firsthand.
From Design to Working Software
One of the interesting directions highlighted at Config India 2026 was Code Layers, which brings interactive, code-backed prototypes into Figma workflows.
Design and development have traditionally involved a handoff: designers create interfaces, and developers turn those designs into working applications. Tools that bring these steps closer together could make experimentation faster and collaboration easier.
As someone interested in building applications with AWS, I can see how these workflows could complement cloud services. For example, a frontend could connect to APIs built with Amazon API Gateway, business logic running on AWS Lambda, and data stored in Amazon DynamoDB.
These are possible combinations developers could explore, rather than integrations announced between Figma and AWS.
AI Needs Context, Not Just Prompts
Another interesting development was Figma Specs, which brings product requirements, design context, and technical information closer together.
For developers building AI-powered applications, this is an important idea. Generating code is only one part of the process; an AI system also needs to understand the requirements and constraints behind the product.
This connects with my interest in Amazon Bedrock and AI-powered application development. When building an AI agent, providing relevant context, suitable tools, and clear boundaries matters just as much as choosing a capable model.
For student builders experimenting with AI, it is a reminder to consider the complete development workflow rather than simply asking a model to generate code.
MCP and the Next Generation of AI Agents
Config India also highlighted the growing ecosystem around the Model Context Protocol (MCP), including Figma's announced partnership with Indian AI company Sarvam.
MCP provides a standardised way for compatible AI applications to connect with external tools and context.
AWS builders can explore related concepts through Amazon Bedrock AgentCore, including deploying MCP servers and building systems in which AI agents interact with approved tools.
I find this particularly interesting because it creates opportunities to connect AI models with useful capabilities and real application workflows. The challenge is not only making an agent work, but also ensuring that it operates securely and reliably.
Figma's announcement does not establish a direct partnership with AWS. Rather, it offers an example of the wider ecosystem in which cloud-based AI applications can operate.
What This Experience Means to Me as a Student Builder
Attending Config India gave me another perspective on the technology industry beyond the tools and platforms I work with regularly.
It reinforced three lessons for my journey:
Start building early. You do not have to wait until graduation to develop projects, explore new technologies, or establish a personal brand.
Look beyond your specialisation. Understanding design and user experience can make you a better developer, even when your primary interest is cloud computing or AI.
Learn by participating. Being present at industry events gives you opportunities to discover ideas, meet people, and understand how others approach technology.
The conversation about my event pass was a small moment, but it reminded me that being a student does not have to limit the ambitions you pursue or the communities you participate in.
There is still a lot to learn, and that is precisely why these experiences matter.
Final Thoughts
My experience at Config India 2026 brought together two things I value: exploring emerging technology and continuing to build my own identity as a developer.
The event's announcements around design, code, and AI point towards a future in which designers, developers, and intelligent tools work more closely together.
As a second-year student and the founder of GunnerJyo, I want to keep exploring these intersections, experimenting with AWS and AI technologies, and turning what I learn into practical projects.
You do not need to wait until you become a professional to start building. You can start where you are, with what you have, and grow through the work you do.
Further reading
Figma — Config India 2026 announcements
AWS — Deploy MCP servers with Amazon Bedrock AgentCore
This article reflects my personal experience attending Config India 2026 and my perspective as a student builder. The AWS connections discussed are potential technical applications, not claims of an AWS–Figma partnership.