Website:
udit.edu.in
Job details:
The Mission
UDIT teaches people to build things — across Design, Management, and Technology. We're now looking for someone to bring that same builder energy inward, to how the university itself runs. Admissions replies typed out one by one. Faculty timetables fixed by hand in spreadsheets. Studio and crit schedules juggled over WhatsApp. Fee reminders sent manually. The same student question landing in five different inboxes. Every department has friction like this, and right now nobody owns fixing it. You will.
This isn't a "design one big AI platform" role. It's a "sit with the admissions officer, the registrar's team, a studio coordinator, find what's slow and repetitive, and ship a fix this week" role — small wins, every week, compounding into a university that spends its time on students and studio work, not paperwork. AI is your default tool, not your last resort.
What You'll Actually Do
Find the friction
- Spend your first three weeks sitting with admissions, the registrar's office, student services, finance, marketing, and a couple of academic departments. Watch what people actually do, not what they say they do.
- Keep a running "friction log" — every repeated manual task, how long it eats up, how often it happens, and when it spikes (admissions season, crit week, exams, fee deadlines).
- Rank problems by hours saved versus effort to fix. Start at the top.
Build the fix yourself
- Ship one working automation or tool every week from month one — enquiry emails auto-classified and drafted, application documents checked for completeness, offer letters generated from the admissions sheet, fee reminders triggered automatically, studio/crit scheduling untangled, a weekly enrolment report that builds itself.
- Use Claude as your default AI layer wherever judgement or language is involved — classifying enquiries, drafting replies, summarising documents, pulling data out of PDFs and transcripts.
- Use no-code and automation tools (n8n, Lovable, or similar) to go from idea to working first version yourself, before anyone writes production code.
- When something needs to scale beyond what you can build alone, write it up clearly enough for engineering or IT to pick up — then stay involved until it actually works, not just until handoff.
Make it stick
- Document every automation in one place: what it does, what breaks it, who to call.
- Train the person who owns the task. If they can't run it without you, it isn't done.
- Track and report hours saved, monthly. That's your scorecard.
Work across the whole university
- This isn't a single-department role. You'll pick up problems wherever they surface — admissions one week, a faculty timetable the next, a finance workflow after that — rather than owning one narrow lane.
Who You Are
- 1–2 years of experience. Freshers welcome — as long as you've built something before: a side project, an automation, an internal tool, anything you can show us.
- AI-native. You already use Claude, Lovable, n8n every day — not just to get answers, but to build and automate things.
- Curious, not necessarily technical. You don't need to code, but raw data and a new tool don't scare you.
- Adaptable. If your first attempt doesn't work, you adjust and try again — you don't wait for someone else to fix it.
- Ships fast. You'd rather launch something 80% right this week than perfect a plan for a month.
- Finishes things. A half-built automation nobody uses is worse than no automation at all.
Tools & Fluency (Nice to Have, Fast to Learn)
- Comfortable prompting AI tools (Claude, ChatGPT) for real build work, not just Q&A.
- Experience with no-code/low-code builders (Lovable, v0, Bolt.new, Replit Agent, or similar).
- Basic comfort with spreadsheets and structured data; SQL is a bonus, not a requirement.
- Notion for documentation, trackers, and roadmaps.
- Exposure to automation tools (n8n, Zapier, Make) or a backend-as-a-service like Supabase.
Why Join UDIT?
- Real impact, not vanity metrics — your work changes how admissions, faculty, and staff actually spend their day.
- Own things end to end, from day one — rare for a fresher role. You won't just write requirements, you'll build and ship yourself.
- Work at the frontier of applied AI inside a real institution, not a tech demo — and inside a university built specifically around creators and builders.
- Small team, direct access to leadership — flat structure, fast decisions, no bureaucracy standing between your idea and shipping it.
- Join an institution with a decade-plus track record in Indian design education — UDIT grew out of IIAD, and now spans Design, Management, and Technology.
- An early shot at shaping what AI-native operations looks like at a university that itself teaches people to make things.
What This Role Is Not
- Not a software engineering role — you won't be building UDIT's core academic systems.
- Not IT support.
- Not a strategy role — you'll be measured on things shipped, not decks written.
How We'll Measure You
- Automations live and still running 30 days after you ship them.
- Hours saved per week across departments.
- Number of staff who can run their own automations without you.
- Time from "problem found" to "fix shipped."
How to Apply
Send us at hr@udit.edu.in
- Your CV
- One thing you've built with AI or automation — a workflow, a tool, an app, anything — with a short video or a few screenshots showing it working and what it replaced.
- One paragraph on a repetitive task you've seen anywhere — college, internship, part-time job — that you'd automate first, and how.
Applications without item 2 &3 will not be reviewed.
Click on Apply to know more.
