I wrote this section to capture my own takeaways from the First Cloud Journey (FCJ) program and share feedback that might help future interns get even more value from the experience.
1. Working Environment
AWS offered the type of environment I imagined only after years in industry: ergonomic offices, quiet focus rooms, and tooling that actually works. What surprised me most was the accessibility of everyone around me. Senior engineers routinely paused to explain context, and managers encouraged me to ping them whenever I hit a wall. Hybrid flexibility also meant I could stay productive during deep-focus build days while still taking advantage of on-site collaboration.
Because the FCJ team treated curiosity as a strength, I asked far more questions than I normally would. With Sandbox accounts and AWS credits on hand, I spun up real infrastructure, broke it, and fixed it under guidance—something textbooks can’t replicate.
2. Support from Mentor / Team Admin
My mentor coached rather than dictated. Whenever I brought a blocker, they nudged me toward the right AWS whitepaper or tool so I could reason through the solution myself. Highlights that stood out:
Meanwhile, the admin crew cleared every logistical hurdle—from IAM requests to laptop support—before I even realized they existed. Their responsiveness let me stay locked in on shipping features.
3. Relevance of Work to Academic Major
The Bandup IELTS initiative connected directly to my computer science curriculum yet stretched me into applied cloud engineering:
| Academic Knowledge Applied | New Skills Developed |
|---|---|
| Python programming | AWS Lambda & serverless orchestration |
| Data structures & algorithms | RAG pipelines & vector search |
| Database fundamentals | DynamoDB, ElastiCache, data modeling |
| Networking basics | VPC design, subnetting, security controls |
| Software engineering | CI/CD automation, Infrastructure as Code |
Class projects rarely demand production SLAs or AI integrations. Owning Gemini audio flows and Titan embedding pipelines forced me to connect theory with real-world latency, throughput, and cost considerations.
4. Learning & Skill Development Opportunities
FCJ layered structured learning with autonomy. Over twelve weeks I:
Mentor checkpoints prevented me from drifting off course, yet I still had the autonomy to prototype ideas and learn through iteration.
5. Company Culture & Team Spirit
Every Amazon Leadership Principle I’d read about showed up in day-to-day behavior. Examples:
Feeling like an actual contributor rather than an observer kept me fully engaged from week one.
6. Internship Policies / Benefits
FCJ backed up its promises with tangible support:
What did I find most satisfying during my internship?
Shipping features that students can actually use. Watching the Speaking Evaluator ingest an audio file, run it through Gemini, and return band feedback via my Lambda pipeline was the moment everything clicked—my code made someone else’s learning easier.
What could be improved for future interns?
Would I recommend this internship to friends?
Without hesitation. If you love cloud engineering, FCJ offers:
All you need is curiosity and the willingness to put in focused effort.
Ideas to further elevate FCJ:
Would I like to stay involved?
Absolutely. My goals include:
Final thoughts
FCJ reshaped how I think about building in the cloud. I entered with classroom knowledge and curiosity; I’m leaving with battle-tested workflows, stronger communication skills, and confidence in my ability to design secure, scalable systems. Thank you to everyone at AWS who invested in my journey. 🙏
“Growth happens where curiosity meets accountability. FCJ created that intersection for me.”