Secure delivery systems
Encryption and key handling, offline-first device software, release policy enforcement, and the audit trail that has to stand up after the exam.
A leaked question paper cancels an exam for lakhs of candidates and costs people a year of their lives. The work here is to make that failure structurally impossible — which is an engineering problem, an operations problem, and a security problem at the same time.
Examination infrastructure fails in public and at scale. Every area below exists because one of the ways it can fail needs an owner.
Encryption and key handling, offline-first device software, release policy enforcement, and the audit trail that has to stand up after the exam.
Device lockdown, adversarial review of the custody chain, key-management design, and turning security claims into things an authority can test.
Runbooks, centre readiness, device provisioning at scale, invigilator training, and the exception paths that decide whether an exam survives a bad day.
Console and workflow design for officers who cannot afford ambiguity, and candidate-facing screens that must be readable under exam pressure.
An internship here is scoped like a job: a defined problem, a mentor, and something that ships. If we cannot offer that, we will tell you rather than fill a seat.
Work on the real system under supervision, not a side project shelved at the end.
A defined problem, a mentor, and a written scope agreed at the start.
Open to students and recent graduates; duration agreed case by case.
Submitting opens a pre-filled email to gaurav@mgktech.in in your mail client, where you can attach your CV.
We keep applications open across the areas above rather than publishing a fixed vacancy list. Tell us what you want to work on and we will reply about current scope. If nothing fits immediately, we say so rather than leaving you waiting.
Yes. Internships are open to students and recent graduates. Mention your course, year, and the dates you are available in your application.
A CV or a link to your work — repository, portfolio, or a write-up of something you built. For engineering and security, evidence of what you have actually built or broken counts for more than a list of technologies.
No. Most of what matters here is careful engineering, security judgement, and operational discipline. Domain knowledge is learnable; the standard of care is not negotiable.