The FCAJ AWS Bootcamp was a valuable experience for me. It introduced me to AWS, cloud computing, practical technical projects, and a more complete way of evaluating real systems. Before joining, I had limited AWS experience and no clear direction for building a professional profile in the technology industry.
The bootcamp taught me more than technical knowledge. I also learned about developing my LinkedIn presence, expanding my network, attending technology events, and connecting with professionals and other students in the community. These were activities I had not maintained consistently before.
The weekly events broadened my perspective through practical discussions about cloud, AI, data, career paths, working environments, and industry skills. They showed me that career growth requires more than coding or theory. Product thinking, communication, self-learning, and community involvement are also important.
After the program, I have more knowledge, more connections, clearer direction, and stronger motivation to rebuild my GitHub, portfolio, and CV properly. My employment opportunities may not change immediately, but I now have a better foundation and more relationships to support future growth.
I would rate my satisfaction with the program at approximately 7/10. I gained substantial knowledge and learning opportunities. The program gave me more practical exposure to AWS, project development, technology communities, and professional profile building.
However, I did not make full use of the networking and personal connection opportunities. This was partly because I was not proactive enough and partly because the program had many students, making it difficult for administrators and mentors to follow every participant closely.
I understand that a bootcamp is not intended to guide every student step by step, and no one is responsible for providing constant individual attention. Nevertheless, additional direction, periodic check-ins, or encouragement could significantly improve the experience for beginners who are not yet proactive or do not know what questions to ask.
The most useful lesson was understanding the difference between a demo project and a project that can be presented as a real system. I previously thought that a working implementation was sufficient. The bootcamp taught me that a strong project also requires architecture, justified technology choices, testing, logs, basic security, cost controls, and clear documentation.
The second lesson was the importance of a professional profile and network. LinkedIn, GitHub, a portfolio, and a CV are not merely formal requirements. They demonstrate learning progress, technical ability, and career direction.
The third lesson was self-learning. Although I am not yet consistently proactive, the bootcamp showed me that no one in technology can guide me through every step indefinitely. I need to learn how to ask questions, research, experiment, fail, and correct my own mistakes.
The fourth lesson was the value of community. Attending events and meeting more people gave me a more realistic view of the industry and helped me move beyond the limits of university study or learning alone.
The program could include more regular check-ins or guidance for students, especially beginners who have limited experience or do not yet know how to direct their own learning. Not every participant begins with strong initiative, so light monitoring, reminders, or more personalized guidance could help students remain engaged.
Another improvement would be dividing participants into smaller groups, each followed by a mentor or administrator. Students could ask questions more comfortably, receive feedback sooner, and feel more supported. Smaller groups may also provide a safer environment for quieter participants to communicate when they face difficulties.
The bootcamp could also schedule periodic project reviews. Early feedback on ideas, architecture, scope, documentation, and presentation would make final projects clearer and reduce major changes near the end of the program.
I would also value more practical guidance on controlling AWS costs, cleaning up resources, debugging deployment failures, and presenting projects on GitHub or LinkedIn. These topics are particularly useful for students and beginners.
Overall, my main suggestion is to create more points of contact among administrators, mentors, and participants. I understand that this is difficult with many students and administrators who also have professional responsibilities, but it would substantially improve the learning experience.
I would recommend the FCAJ AWS Bootcamp to people who want to begin learning AWS or cloud computing or gain experience with a practical project. It is suitable for students and beginners who want to explore cloud, clarify their career direction, and expand their professional network.
I would also explain honestly that the program does not guide participants through every step. Participants need a self-learning mindset and should be proactive in asking questions, researching, developing their projects, and connecting with others. The bootcamp is still valuable for less proactive students like me, but they should be prepared to step outside their comfort zones.
For me, the program’s greatest value was not only AWS knowledge. It also gave me new perspectives, more connections, greater interest in maintaining LinkedIn, GitHub, my portfolio, and my CV, and a stronger foundation for future career development.