CRC Certification Framework
CRC certificates, badges and profiles should clearly identify both the discipline and the achieved skill level. Membership status should be stated separately where appropriate.
Certification philosophy
CRC distinguishes attendance from demonstrated capability. Recognition should reflect evidence such as knowledge assessments, hands-on labs, practical assignments, project evidence, documentation evidence, and instructor or mentor review.
Membership status is displayed separately from technical certification. A learner’s CRC membership category does not, by itself, establish a discipline skill level—and a skill certificate does not automatically change membership category.
Recommended naming examples
- CRC Certificate — Programming, Beginner Level
- CRC Certificate — Database Administration, Professional Level
- CRC Specialist Recognition — PostgreSQL Performance and High Availability
- CRC Professional Member
- CRC Elite Member and Technical Mentor
Digital badges or profile recognitions may follow the same discipline and skill-level clarity.
Governance reminders
- Skill-level recognition must reflect demonstrated capability, not attendance alone.
- The term Specialist should be used only when advanced competence has been established.
- The term Architect should normally describe a role, responsibility or advanced specialization—not automatically every Specialist.
- The term Engineer may be used carefully according to local legal, professional and industry conventions.
Explore the CRC Framework
Ready to take the next step?
Explore membership, learn more about CRC, or upload documents to continue your application.
Join CRC About CRC Upload Documents