The curricular requirement is the whole test
Curricular Practical Training exists to let a student perform work that is an integral part of an established curriculum. The employment must relate directly to the student's major and be authorised by the designated school official before it begins. For integration and middleware work, the risk is rarely the technology — it is a placement that looks like ordinary staffing rather than coursework.
The practical consequence is that scoping happens before onboarding. Talentium Technologies defines the technical scope of a student engagement, confirms it maps to the student's programme requirements, and only then requests authorisation. Reversing that order is how programmes drift out of compliance.
Scoping a middleware engagement that is genuinely academic
Good CPT scopes for integration specialists tend to be bounded, technically deep, and documentable. A student might characterise the latency distribution of an existing message-routing tier, build a schema-registry compatibility harness, or prototype an observability layer for an API gateway. Each produces an artefact the academic supervisor can assess.
Poor scopes are open-ended production support rotations. They may be excellent professional experience, but they are difficult to tie to a specific course requirement, and they generate no assessable output.
Hours, part-time thresholds, and the full-time trap
CPT is categorised as part-time or full-time based on hours per week, and the distinction carries real consequences for subsequent OPT eligibility. Employers frequently create exposure by informally extending hours during a delivery crunch — an integration cutover weekend is a classic example.
The mitigation is structural. Student engagements are excluded from on-call rotations and cutover windows unless authorisation explicitly supports the hours. Timekeeping is reviewed weekly, not at engagement close.
Documentation that survives review
A defensible CPT file contains the authorisation record, an offer letter whose described duties match the authorised scope, the academic requirement the placement satisfies, and the supervisor of record. Where duties evolve — as they always do on live integration estates — the file should show a re-authorisation, not a silent expansion.
The discipline that matters most is simple: what the student actually does each week should be recognisable in the authorised description. When those two drift apart, no amount of retrospective paperwork closes the gap.