AWS Builder Center
How I Became NJIT's Founding AWS Student Builder Group Leader

How I Became NJIT's Founding AWS Student Builder Group Leader

The story of building NJIT's first AWS Student Builder Group from zero — a blank page, an acceptance email, and three months of finding the right people.

How I Became NJIT's Founding AWS Student Builder Group Leader By Asmar Hasanova, Founding Group Leader, AWS Student Builder Group at NJIT
There is a strange kind of email you never forget: the one that tells you that a thing which does not exist yet is now yours to build. In May 2026, I opened one of those. I had been selected as the Founding Group Leader of NJIT's first AWS-affiliated student community, one chapter in a global network of more than 925 AWS-recognized student groups. There was no club room, no members, no logo, no meeting schedule. There was just an acceptance letter and a blank page.
This is the story of how I got there, and what the first three months of building something from zero actually look like.
How it started
I found the program completely by chance, and the chain of events is almost funny in hindsight. At the AWS GenAI Hackathon, two AWS employees ran our workshops, and afterwards I followed them on LinkedIn. Weeks later, their likes started surfacing in my feed, and one day I saw a post one of them had liked: a student at another university celebrating her acceptance as an AWS student community leader. I stopped scrolling and read the whole thing. What is this program?
My first thought was the obvious objection: I am an Electrical Engineering major, not a computer science student. My second thought beat it: I had just won an AWS hackathon, so clearly the first thought did not matter. And there was one more thing I could not let go of. A nearby peer university already had an AWS student community. NJIT did not. That settled it. I opened the application form the same day.
If I am being fully honest, there was also a simpler reason underneath all of it: in every group I have been part of, I end up being the one who organizes, plans, and leads. I had been wanting to do that for a real tech community for a long time. This was exactly that chance.
What I did have going in was a genuine history with AWS. In December 2025, my co-founder and I won first place at the AWS GenAI Hackathon, building an end-to-end serverless platform on Lambda, DynamoDB, S3, and Bedrock, an architecture that cut infrastructure costs by 94 percent compared to a traditional setup. That experience turned into Octoman, the startup we still run today. So when I wrote my application, I was not describing AWS from documentation. I was describing what it feels like when a serverless architecture you designed at 3 a.m. actually holds up in a live demo.
The application and selection
The application was more interesting than a typical form. Alongside the written questions, I had to record a video of myself explaining one AWS service, with my own PowerPoint slides, presented as if I were running a workshop for students. Not pitching to a jury. Teaching. That design choice tells you everything about what AWS is actually selecting for: not the person with the most certifications, but the person who can stand in front of a room and make a service make sense to someone hearing about it for the first time.
My honest advice to anyone applying: do not present yourself as a finished leader. Present yourself as someone who has already started building without permission. The hackathon project, the startup, the late-night debugging sessions, those said more than any leadership adjective could.
What "founding" actually feels like
Here is what nobody tells you about a founding role: the freedom and the terror are the same thing. An established club hands you a playbook. A founding chapter hands you a question: what should this even be?
I was on a train when the acceptance email arrived. I read it twice, then immediately started messaging my family and friends, and their excitement made it feel real before I had even processed it myself. Somewhere between those messages and my stop, the feeling shifted from I got accepted to there is now a chapter at NJIT, and it is currently just me. That second feeling is the founding role in one sentence.
The first three months: from zero to structure
Building the chapter end-to-end came down to three parallel tracks.
Finding a faculty advisor. Technically, I did this one backwards: I emailed a professor who teaches cloud computing before I even submitted my application. My pitch was simple: a nearby peer university has an AWS community, we do not, would you be our advisor if I get selected? His answer was refreshingly chill: "Yeah, okay. Why not?" Lesson learned: lining up your advisor before you apply turns your application from an idea into a plan.
Recruiting a Core Team. Rather than recruiting friends, I opened a Google Form and ran short, deliberately informal interviews. The structure we landed on: two Tech Co-Leads, a Community Advocate, a Coordinator, and a Training Officer. The full recruitment playbook, what worked and what I would do differently, deserves its own article, and it is coming.
Making it official. Registering a brand-new organization at NJIT and mapping out the 2026 to 2027 calendar: six events and four technical articles, backed by AWS credits and certification vouchers. Our philosophy for the coming year is to collaborate, not compete. We are planning joint events with NJIT's existing tech communities, from ACM to hackathon and cloud-focused groups, because they already know how to bring students together, and we bring AWS to the table.
The founding cohort feeling
The part I did not expect: the other founding leaders. Being in the founding cohort means there are people at hundreds of other universities staring at the same blank page you are, at the same time. My connection to them so far has been simple and unglamorous: LinkedIn messages. Casual chats about what they are building, what events they are running, what is working on their campus. Even those small exchanges change how you work, because every idea you see makes your own blank page a little less blank.
That is what a builder community is supposed to be, and it works on the leaders too.
What's next
This fall, the AWS Student Builder Group at NJIT officially opens its doors: hands-on workshops, certification study groups, and events where you build something real before you leave the room. If you are an NJIT student and any part of this story sounded like you, especially the part where nothing existed yet, come find us. The chapter is on LinkedIn as AWS Student Builder Group at NJIT; follow us there for our first events and Core Team announcements.
And if you are a student at another university wondering whether to apply for the next SBGL cohort: the blank page is the best part. Apply.


Asmar Hasanova is a senior in Electrical Engineering at NJIT, co-founder of Octoman, and a first-place winner of the AWS GenAI Hackathon. Her research on deep learning calibration was accepted at IEEE ISAIA 2026.
Any opinions in this article are those of the individual author and may not reflect the opinions of AWS.
Enjoyed reading this content? Let the author know!

Your likes, comments, shares, and saves help creators reach more builders.

Loading recommendations

Loading article