AI Engineering · Project-Based Training

Generative AI Application Development

Course covering generative AI application patterns used in production-oriented prototypes. Proposed catalog entry pending approval of curriculum, instructor, pricing, and schedule.

  • Python
  • LLM APIs
  • Retrieval basics
  • Evaluation harness
  • Git

This is fee-based Project-Based Training — not a paid internship. Registering interest is not enrollment and does not collect payment. Fee details will be shared before enrollment.

Overview

Program facts

Duration
2 months
Level
Intermediate
Weekly commitment
Approximately 10–15 hours per week (subject to final schedule)
Delivery
Online
Availability
Coming soon — interest registration available
Fee
Fee details will be shared before enrollment
Mentor / supervisor
Instructor or delivery owner assigned before open enrollment.
Delivery owner
Assigned before enrollment opens
Certificate policy
Certificate policy confirmed at enrollment open.
Fit

Audience, prerequisites, and selection

Audience

  • Developers building AI features into products
  • Learners who already write code confidently

Prerequisites

  • Comfortable programming in at least one language (Python preferred)
  • Basic HTTP and Git knowledge
Curriculum

Curriculum

Curriculum status: forthcoming / proposed. Topics below are indicative and not a finalized enrollment curriculum until marked approved.

  • LLM application architecturefoundational
  • Prompt design and structured outputsfoundational
  • Retrieval-augmented generation basicsadvanced
  • Evaluation and reliabilityadvanced
  • Security and responsible data handlingadvanced
Outcomes

Learning outcomes

  • Implement a grounded generative feature with evaluation checks
  • Articulate failure modes and mitigations
Project

Project specification

Build a source-grounded generative feature with evaluation checks and reliability notes.

Problem statement · Illustrative
Users need grounded answers from a curated knowledge set, with evaluation that catches unsupported claims.
Primary user workflow · Illustrative
Ask a question → retrieve sources → generate grounded answer → run evaluation checks → return answer or safe refusal.
Functional scope · Illustrative
LLM application structure, structured outputs, basic retrieval, evaluation harness, and responsible data handling notes.
Technical components · Illustrative
Application service, model API integration, retrieval layer, evaluation cases, and documentation.
Data requirements · Illustrative
Fixed illustrative corpus. Production proprietary data is not included.
Testing expectations · Illustrative
Grounded answer case, missing-evidence case, and at least one malformed input or dependency failure.
Known limitations · Illustrative
An MVP with evaluation is not equivalent to a fully production-hardened AI system.
What counts as completion · Illustrative
Working grounded feature, evaluation notes, reliability write-up, and demonstration of failure handling.

Examples

  • Source-grounded Q&A assistant with evaluation harness

Deliverables

  • Working grounded feature
  • Evaluation harness or case set
  • Reliability notes

Example or assigned project work—not a published student achievement or employment guarantee. Student work is not assumed for commercial use without appropriate agreements. Sections marked illustrative are representative examples, not a fixed commercial brief.

Assessment

Evaluation criteria

How work is reviewed — clarity of decisions matters as much as a working MVP.

  • Project rubric
  • Written reliability notes

Evaluation focuses on observable engineering evidence. Exact rubrics are published per program when approved.

  • 01

    Main workflow correctness

    Does the primary user journey work as specified?

  • 02

    Code comprehension

    Can the participant explain what the code does and why?

  • 03

    Architecture explanation

    Are component boundaries and trade-offs articulated clearly?

  • 04

    Input validation

    Are invalid inputs rejected or handled safely?

  • 05

    Testing

    Are expected behavior and at least one failure mode checked?

  • 06

    Edge-case handling

    Does the work account for realistic non-happy-path conditions?

  • 07

    Documentation

    Can another engineer set up, run, and understand the MVP?

  • 08

    Demonstration

    Is the working result shown with an honest account of limitations?

Frequently asked questions

Vasiva Academy

Ready to build something real?

Choose a pathway, review a program, and register interest when enrollment opens.