Internship Policy
Last Updated: June 2026
1. Onboarding & Eligibility Verification
All candidates accepted into the Matnite Infotech internship track must successfully complete profile registration and submit matching documentation.
You are required to provide genuine educational criteria, college coordinates, and valid contact indicators. Providing falsified profiles, inaccurate institutional details, or proxy accounts will lead to instant cancellation of the active cohort slot without credit options.
2. Performance & Milestones Monitoring
To fulfill training guidelines and receive performance recognitions, interns are expected to maintain an active production cadence:
3. Professional Code of Conduct
Interns represent a collaborative corporate development community. Absolute professionalism is mandatory across all communication lines, including slack spaces, live check-ins, peer workspaces, and evaluation forums.
Harassment, discriminatory remarks, identity trolling, intentional disruption of training sessions, or disrespectful behavior directed toward project managers, internal mentors, or fellow learners will meet a zero-tolerance policy.
4. Intellectual Property & Non-Disclosure
Any application logic, core repository modules, system designs, private dataset files, or custom technical infrastructure architecture created, modified, or handled during the internship tenure belongs exclusively to Matnite Infotech. Interns retain zero rights to repurpose, distribute, or license company project code configurations for external commercial purposes.
5. Program Exit, Dismissal & Disqualification
Matnite Infotech maintains exclusive administrative rights to suspend or completely terminate an intern's access token immediately under serious code violations:
- ✕Failing to submit two consecutive milestone sprints without verified medical notifications.
- ✕Unapproved distribution of internal training videos, server endpoints, or source dashboards.
- ✕Extreme behavioral infractions or failure to respect core team workspace rules.
- ✕Plagiarizing project items or submitting proxy work during code defense cycles.