Date: 24th April 2026

Time: 9:00 AM

Venue: Aurolab, No. 1, Sivaganga Rd, Veerapanjan, Madurai, Tamil Nadu

625020

Please ensure that the candidates arrive in formal attire. The process will
include a technical round focused on their projects, certification courses,
and the tools they have knowledge with. Their general subject knowledge
will also be tested.

Kindly instruct the students to bring their updated CVs and academic
documents for the interview.

We developed a team-based Attendance Tracker Web App to automate

and enhance academic attendance management. My key role was in
backend development and database management. The system offered
real-time tracking, alerts, and analytics dashboards. We tackled scalability
challenges, enabling bulk Excel uploads and predictive attendance
analysis. In the future, we plan to expand by adding comprehensive
student profiles—integrating academic records, achievements, and
documents—so that the system scales seamlessly for broader institutional
use. Overall, the project improved efficiency, accuracy, and student
engagement, with a data-driven approach, and we see great potential for
further enhancement.

technical

Ah, absolutely! Let’s add some technical depth. For example, we can
specify that the backend API was built with [Link] and Express, the
database used MongoDB for flexible, scalable storage, and that we
leveraged React on the frontend for a dynamic UI. We used Python
(Pandas, NumPy) for bulk analytics processing, and integrated Excel file
handling with the xlsx library. If we add this technical detail, it’ll show a
deeper understanding of how each part works. Does that feel aligned with
what you were aiming for?
Transcribing…

Nice — that flow is correct 👍

Let me turn it into a clear technical explanation you can confidently
say in interview (with a bit more depth).

🎯 OD WORKFLOW — TECHNICAL EXPLANATION

🔁 End-to-End Flow

Student Form → Express Route → Multer Upload

MongoDB (ODRequest Collection)

Faculty Dashboard (EJS Render)

Approve/Reject → Update DB

Reload UI

🧩 1️⃣ Student Form Submission

 The student fills an OD form and uploads proof (PDF/image).

 The form uses:

enctype="multipart/form-data"

👉 This allows file upload.

⚙️2️⃣ Express Route + Multer Middleware

 Request hits backend route:

POST /submit-od

 Multer middleware:

[Link]("proof")

What Multer does:

 Extracts file from request

  Stores it in /public/uploads

 Adds file info to:

[Link]

3️⃣ MongoDB Storage

 Backend creates a document:

studentID,

name,

reason,

filePath,

date,

status: "Pending"

 Stored in:

ODRequest collection

👉 Status is initially Pending

4️⃣ Faculty Dashboard Rendering

 Backend fetches all OD requests:

[Link]()

 Sends to EJS:

[Link]("faculty-dashboard", { odRequests })

 EJS dynamically displays:

o Student name

o Reason

o Proof link

o Status

o Approve/Reject buttons
✅ 5️⃣ Approve / Reject Action

When faculty clicks:

✔ Approve

POST /api/approve-od/:id

❌ Reject

POST /api/reject-od/:id

Backend Logic:

const od = await [Link](id);

[Link] = "Approved" // or "Rejected"

await [Link]();

👉 Only status field changes

🔄 6️⃣ UI Refresh

[Link]("/faculty-dashboard");

 Page reloads

 Updated status shown instantly

🧠 KEY TECH CONCEPTS USED

 Multer → file handling

 Express Routes → API handling

 MongoDB → persistent storage

 EJS → dynamic UI rendering

 REST APIs → approve/reject actions

💬 PERFECT INTERVIEW ANSWER (SHORT)

“In my system, OD submission is handled through a multipart form where

the student uploads proof. The backend uses Multer to process and store
the file, and the request is saved in MongoDB with a ‘Pending’ status.
The faculty dashboard fetches all requests and displays them dynamically
using EJS.
Faculty can approve or reject requests, which updates the status in the
database through REST APIs, and the UI refreshes to reflect the change.”

🚀 If you want to sound even stronger

Add this line:

“The system follows a clear separation between frontend rendering,

backend API handling, and database persistence, ensuring scalability and
maintainability.”

How can I answer when the interviewer asks, like, so did you develop the
project by yourself?”

Ah, that's a great question, and it's really all about being honest while
highlighting your ownership and collaboration. You could say something
like: "Yes, I developed the core structure and most of the logic by myself. I
did follow some best practices I learned from open-source examples and
collaborated with peers to get feedback. So, while I built it myself, I did
make sure it aligned with best practices and got peer validation." That
way, you’re showing confidence in your work but also acknowledging a
healthy collaboration process.

What platform do you use to connect with your peers and what is the
open source you were using to develop your project? Answer these two
questions.”

Of course! For collaborating with my peers, I primarily used GitHub for

version control and code reviews, along with Slack for real-time
communication and coordination. As for open-source, I leveraged [Link]
for the backend, MongoDB as the database, and I used EJS templating. I
also relied on [Link] for routing and server-side logic, and [Link] for
visualizations.

;;;;;;;;;;;;;;;;;

👉 “How does email automation work in your project?”

Say this:

“In my project, I implemented email automation using Nodemailer. When

attendance data is processed, the system checks if any student’s
attendance falls below 75%. These students are filtered and sent to a
backend API. The server then uses Nodemailer with Gmail SMTP to send
automated warning emails to each student. This helps notify students in
real time and improves attendance monitoring.”

/////////////////////////////////////

🎯 WHAT THEY WILL TEST (REALISTIC)

1️⃣ 🔧 Project Deep Dive (MOST IMPORTANT)

They will focus heavily on your Smart Attendance System

Expect questions like:

 “Explain your project architecture”

 “Why did you choose [Link] + MongoDB?”

 “How does OD approval work internally?”

 “How do you handle file uploads?”

 “How is data stored in MongoDB?”

 “What challenges did you face?”

👉 They are checking:

 Do you actually understand your code?

 Or just copied it?

2️⃣ 💻 Technical Questions (Core Subjects)

🔹 Java

 OOP concepts (very important)

 Exception handling

 String vs StringBuilder

 Collections basics

🔹 DBMS / SQL

 Joins

 Normalization

 Queries (like the ones you practiced)

  Indexing basics

🔹 Web / Backend (VERY IMPORTANT for you)

 REST APIs

 GET vs POST

 Middleware (Express)

 MVC architecture

3️⃣ 🧠 Practical Thinking

They may ask:

 “How will you scale your project?”

 “How will you handle 10,000 users?”

 “What if database fails?”

 “How to improve security?”

👉 They want your thinking ability, not perfect answers

4️⃣ Communication

 Clarity

 Confidence

 Structured answers

🧠 HOW TO PREPARE (SMART PLAN)

✅ 1. MASTER YOUR PROJECT (Top Priority)

Be ready to explain:

✔ Architecture

Frontend (HTML/CSS/JS)
↓
[Link] (Express APIs)
↓
MongoDB

✔ Key Features
  Attendance tracking

 OD submission + approval

 Email alerts

✅ 2. PREPARE THESE 10 QUESTIONS (VERY IMPORTANT)

Practice answering:

1. Tell me about your project

2. How does OD workflow work?

3. How do you store data in MongoDB?

4. What is REST API?

5. Difference between GET and POST

6. What is middleware in Express?

7. What is normalization?

8. Difference between ArrayList and LinkedList

9. What is exception handling in Java?

10. What challenges did you face?

✅ 3. PREPARE YOUR STORY

They will ask:

👉 “Did you build this yourself?”

Say:

“Yes, I developed the core backend logic, database design, and frontend
integration myself. I also referred to documentation and best practices
when implementing features like file uploads and email automation.”

✅ 4. PRACTICAL DEMO PREP

Even if you don’t show laptop:

Explain clearly:

 Login flow

 Attendance entry
  OD request

 Approval

⚠️COMMON MISTAKES (AVOID)

❌ Saying “I don’t know anything”

❌ Memorized answers
❌ No clarity in project
❌ Ignoring basics (DBMS/Java)

💬 PERFECT INTRO ANSWER

“I developed a Smart Attendance Tracking System using [Link], Express,

and MongoDB. It includes features like attendance monitoring, OD request
handling with file upload, and automated email alerts for low attendance.
The system uses REST APIs and follows a structured backend
architecture.”

🚀 FINAL STRATEGY (1-DAY PLAN)

⏰ Morning

 Revise project (very important)

⏰ Afternoon

 Java + DBMS basics

⏰ Evening

 Practice speaking answers

🔥 FINAL TIP

👉 They are NOT expecting perfection

👉 They want:

 Understanding

 Confidence

 Problem-solving