AI-Powered Analytics Assistant
An interactive AI portfolio assistant combining generative AI, curated professional context, job-description analysis, and Google Calendar scheduling within a production-style Next.js application.
Business Challenge
Portfolio visitors and recruiters often need to understand a candidate's experience quickly, compare skills against a job description, identify relevant projects, or determine whether a conversation would be useful.
A static website can display this information, but users still have to search through multiple sections manually. The goal was to create an interactive assistant that can interpret questions, use verified professional context, generate useful answers, and perform meaningful actions such as scheduling a meeting.
What Abhilash AI Can Do
The assistant combines conversational AI with application workflows. It does more than generate text by routing user intent into different experiences.
Profile Q&A
Answers questions about experience, skills, certifications, projects, technologies, and career background using curated profile context.
Job Match Analysis
Compares a job description against profile evidence and identifies strong matches, relevant experience, and realistic gaps.
Meeting Scheduling
Collects meeting details, checks Google Calendar availability, presents valid time slots, and creates a confirmed Google Meet event.
AI Assistant Architecture
The application separates the user interface, server-side API routes, verified professional context, AI processing, and external actions such as Google Calendar scheduling.
Visitor
Natural-language question or action request
Next.js Application
Chat interface and server-side API routes
Context & Intent
Profile knowledge, prompts, and scheduling state
OpenAI
Language understanding and structured response generation
Action Layer
Chat response, job analysis, or calendar workflow
Core Conversation Flow
How the Assistant Works
User Intent
The visitor asks a question or selects an action such as analyzing a job description or scheduling a meeting.
Context Preparation
Verified portfolio, experience, skills, certifications, and project information are supplied to the model.
Prompt Construction
System instructions define the assistant's role, permitted claims, response style, and workflow rules.
Intent-Specific Processing
The application routes the interaction into conversational Q&A, job analysis, or scheduling logic.
External API Action
When scheduling is requested, server-side APIs interact with Google Calendar rather than relying on the language model to invent availability.
Confirmed Response
The application displays the generated answer or confirms an external action only after the backend reports success.
Portfolio Assistant Use Cases
The current portfolio implementation supports multiple recruiter and visitor interactions from the same conversational interface.
“What experience does Abhilash have with Microsoft Fabric?”
The assistant identifies relevant verified experience and summarizes Fabric work around Lakehouses, pipelines, semantic models, migration initiatives, and analytics.
“How well does this job description match Abhilash?”
The assistant compares job requirements with supplied profile evidence and provides strong matches, relevant experience, potential gaps, and a realistic overall assessment.
“I'd like to schedule a meeting with Abhilash.”
The assistant starts a guided scheduling flow, checks actual calendar availability, presents valid meeting times, and creates the event only after explicit visitor confirmation.
AI Job-Matching Workflow
One of the assistant's most useful recruiter-facing capabilities is comparing a job description against verified candidate information.
| Job Requirement | Profile Evidence | Assessment |
|---|---|---|
| Microsoft Fabric | Lakehouse, pipelines, semantic models | Strong Match |
| SQL | Data engineering and analytics workloads | Strong Match |
| Power BI | Dashboards, semantic models, KPI reporting | Strong Match |
| Unlisted Technology | No supporting profile evidence | Potential Gap |
Example assessment shown for portfolio demonstration.
AI-Assisted Meeting Scheduling
Scheduling is handled as an application workflow rather than a fabricated AI response. The chatbot gathers meeting information, calls server-side scheduling APIs, checks the connected Google Calendar, and creates a real event only after validation and user confirmation.
Scheduling Architecture
Collect Meeting Details
The assistant collects the visitor's name, email, optional company or reason, preferred date, and scheduling context.
Interpret Date
Natural-language inputs such as tomorrow, Friday, or next Monday are converted into a specific calendar date.
Confirm Date
The visitor confirms the interpreted date before the application performs an availability check.
Check Availability
A server-side availability API queries Google Calendar Free/Busy data and generates valid 30-minute meeting slots.
Select Time
Only available business-hour slots are presented to the visitor for selection.
Revalidate & Book
Availability is checked again immediately before booking to reduce double-booking risk.
Create Calendar Event
The scheduling API creates the meeting in Google Calendar and adds the visitor as an attendee.
Generate Google Meet
The confirmed event includes a Google Meet conference link and calendar invitation.
Scheduling Controls
Prompt, Context & Guardrail Design
The quality of the assistant depends on both the information supplied to the model and explicit instructions controlling what it may claim or do.
System Instructions
Define the assistant's role, response style, workflow behavior, and boundaries around unsupported claims.
Structured Context
Provide verified experience, skills, certifications, projects, technologies, and professional-impact statements.
Action Guardrails
The assistant does not claim that a meeting was scheduled, email was sent, or external action succeeded until the corresponding backend API confirms the action.
Current Architecture vs Future RAG
The current portfolio implementation uses curated profile and resume-related context supplied directly to the model. It does not represent the current implementation as a retrieval-augmented generation system.
Context-Grounded AI
Retrieval-Augmented AI
Security & Responsible AI Design
AI and external API integrations are kept server-side so application credentials do not need to be exposed to the browser.
Technology Stack
Application
Next.js
React
TypeScript
Tailwind CSS
AI
OpenAI API
LLM
Prompt Engineering
Context Design
Integrations
Google Calendar API
Google OAuth 2.0
Free/Busy API
Google Meet
Backend & Deployment
Next.js API Routes
Environment Variables
GitHub
Vercel
Business & Portfolio Value
Future Enhancements
The current assistant is intentionally grounded in curated context. A future enterprise implementation could extend the architecture with retrieval, governed business data, stronger authentication, and production observability.
AI becomes more useful when it can understand, reason, and act.
The project goes beyond adding a chatbot to a portfolio. It combines verified context, generative AI, job-requirement analysis, structured workflow logic, and a real Google Calendar integration to create a more useful and interactive application.
This case study represents the current portfolio assistant implementation and related application patterns. Retrieval-augmented generation, vector search, enterprise business-data connectors, and governed semantic-model access are presented as future enhancements and are not represented as currently implemented production features.