AU Campus Recruitment 2026
Full Stack Developer – Individual Technical Assessment
Overview
As part of AU Campus Recruitment 2026, candidates shortlisted for the Full Stack Developer role must complete
an individual 24-hour technical assessment.
Each candidate must select any ONE of the two problem statements provided in the document and build a
complete working solution.
The assessment evaluates:
● Frontend development skills
● Backend API design
● Database architecture
● AI/ML integration (light to medium level)
● Deployment and system integration
The project must be fully deployed as per the instructions in the problem statement.
Submissions after the 24-hour deadline will not be considered.
Start : 5:30 PM (18-02-2026)
Deadline : 5:30 PM (19-02-2026)
——————————————————————————————————————————————
Deliverables
Candidates must submit:
● Deployed Frontend URL (Vercel – mandatory)
● Deployed Backend URL
● Public GitHub Repository
● Database schema explanation (ER diagram preferred)
● README with setup and run instructions
● 3–5 minute demo video explaining the application
● Incomplete or non-deployed projects will not be evaluated.
Submission Link
● Submit all deliverables through the following link:
[Link]
?usp=publish-editor
Problem Statement 1
Intelligent Assignment Evaluation & Feedback Platform
Objective:
Build a full-stack web platform where students submit assignments and instructors receive automated
evaluation, feedback, and plagiarism risk analysis.
The focus is on system design, backend logic, and integration of applied AI/ML.
1. Frontend Requirements (Mandatory)
The application must provide:
Student Dashboard:
● Submit assignment text or PDF
● View submission status
● View feedback
Instructor Dashboard:
● Create assignments
● View submissions
● Review AI-generated feedback
Deployment Requirement:
● The frontend must be deployed on Vercel
2. Backend Requirements (Mandatory)
The backend must:
● Expose REST APIs for assignment creation and submission
● Handle file uploads (bonus)
● Perform input validation and error handling
● Integrate AI/ML logic for evaluation
Allowed technologies include [Link], Python, or Java-based frameworks.
3. Database Design
The database should store:
● Users (students and instructors)
● Assignments
● Submissions
● Feedback and scores
4. AI/ML Component (Light–Medium Level)
The system must implement at least one of the following:
● Text similarity scoring to flag plagiarism risk
● Automated feedback generation (rule-based or LLM-based)
Allowed Techniques:
● TF-IDF with cosine similarity
● Sentence embeddings
● Simple LLM API usage
Accuracy is less important than correct integration and justification.
5. Expected Output Example
{
"submission_id": "S103",
"plagiarism_risk": "22%",
"feedback_summary": "The explanation lacks depth in section 2.",
"score": 68
}
Problem Statement 2
Personalized Learning Progress & Recommendation System
Objective:
Develop a full-stack learning platform that tracks student performance and provides adaptive learning
recommendations using basic ML techniques.
1. Frontend Requirements (Mandatory)
The application must allow students to:
● Attempt quizzes
● View progress dashboards
● Receive topic and difficulty recommendations
Deployment Requirement:
● Frontend must be deployed on Vercel
2. Backend Requirements (Mandatory)
The backend must:
● Store quiz attempts
● Calculate progress metrics
● Generate learning recommendations
● Expose APIs consumed by the frontend
3. Database Design
The database should store:
● Users
● Topics
● Quiz attempts
● Recommendation history
4. AI/ML Component (Light–Medium Level)
The backend must include:
● Student performance clustering
● Rule-based or ML-assisted recommendation logic
● Difficulty adjustment mechanism
Allowed Techniques:
● K-means clustering
● Logistic regression
● Heuristic-based rules
5. Expected Output Example
{
"student_id": "U55",
"current_level": "Intermediate",
"recommended_topic": "Neural Networks Basics",
"difficulty_adjustment": "Decrease"
}
Mandatory Deployment Rules
● Frontend must be deployed on Vercel
● Backend must be deployed on a public hosting platform
● Deployed frontend must communicate with deployed backend
Projects without deployment will not be considered for top rankings.
Evaluation Criteria
Area Weight What We Check
Frontend Implementation 20% Usability, API integration
Backend Architecture 25% API design, logic, validation
Database Design 15% Schema clarity and correctness
AI/ML Integration 15% Correct usage and reasoning
Deployment & Integration 15% End-to-end working system
Innovation 10% Extra features or optimizations
Time Constraint
● Total duration: 24 hours
● Internet access allowed
● Open-source libraries permitted