Note! By visiting this site, you agree to abide by the code of conduct. Thanks ×
site logo

About Jr. Dev Mentoring


To make sure that everyone new to programming has the opportunity to build at least one strong relationship within the coding community.

"Corporate mentoring programs have long been recognized as an essential strategy for attracting, developing, and retaining top employees. According to a survey by the American Society for Training and Development, 75% of private sector executives said that mentoring had been critical in helping them reach their current position".


To become the first resource that those new to programming turn to for the support they need.

Mentees, this is an opportunity for you to connect with professionals in the programming commmunity to gain the insight, encouragement, and connections that it will take for you to succeed as a junior developer. “Mentors can do a number of things for your career. They can help you build your resume, guide you on a project, and help you identify resources, including referring you to other mentors and important people in your field” - Ken Williams, Director of the New Voices National Fellowship Program


To match anyone new to programming who wants a mentor, with someone willing to guide them to their first junior developer position.

Jr. Dev Mentoring, is not intented to replace the various forums, message boards, help groups, etc. that are already available for newbies to use. It is meant to be used as a supplement. Those resources are great for solving problems and answering questons related to specific issues but those new to programming also need to build relationships within the community to be successful.


Mentors and Mentees agree to partner for a 12-month time frame, connecting at least twice per month.

Relationships need to be built before any effective mentoring can take place. An environment of trust and mutuality must be established. It is important for the mentor and mentee to become acquainted with each other (Kutilek & Earnest, 2001; Mincemoyer & Thomson, 1998).