Loading...
Loading...
How CodeSage works, from repository ingestion to scored examination.
Connect your repository
Paste any public or private GitHub repository URL. CodeSage clones it, parses the codebase with Tree-sitter, and embeds every code chunk via NV-Embed-QA into a Qdrant vector store.
Choose an examination mode
Pick from Viva Voce (academic defense), Technical Interview (FAANG-style), or Code Review (senior engineer feedback). Each mode calibrates the examiner's focus and scoring rubric.
Answer questions
CodeSage generates questions that reference your actual code — specific file paths, function names, and line numbers. Answer as many as you want, skip freely, end when ready.
Get scored and reviewed
The Nemotron-340B reward model grades each answer on accuracy, depth, and awareness. You get a dimension breakdown, per-question feedback, and an overall score out of 100.
Study and improve
A personalized study guide maps your weak areas to specific concepts and code sections worth reviewing. Track your scores over multiple sessions to see real improvement.
CodeSage uses 5 specialized NVIDIA NIM models, each optimized for its task in the examination pipeline.
Converts code chunks into semantic vectors for retrieval. Optimized for question-answering tasks.
Reranks retrieved code chunks by relevance to the question. Ensures the examiner sees the most relevant context.
Generates viva-ready questions from code context. Probes architecture decisions, trade-offs, and implementation details.
Evaluates answers against rubrics on accuracy, depth, and code awareness. Produces objective, reproducible scores.
Runs alongside the examiner to ensure all generated questions stay within appropriate academic scope.
Each answer is graded by Nemotron-340B on three dimensions:
Accuracy (0–100)
Is the answer factually correct? Does it demonstrate understanding of the code?
Depth (0–100)
Does the answer go beyond surface-level explanation? Are trade-offs discussed?
Code Awareness (0–100)
Does the answer reference specific files, functions, and line numbers from the codebase?
The overall score is a weighted average of these three dimensions. Scores above 80 indicate strong understanding. Scores below 60 suggest areas that need review.