Software Development · Project-Based Training

Backend API Development

Proposed short course focused on backend engineering practices used in production-oriented services.

  • HTTP APIs
  • Auth patterns
  • Validation
  • Automated API tests
  • 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
1 month
Level
Intermediate
Weekly commitment
Approximately 8–12 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 specializing in server-side work

Prerequisites

  • Programming fundamentals
  • Basic HTTP knowledge
Curriculum

Curriculum

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

  • API design and validationfoundational
  • Auth and authorization patternsadvanced
  • Error handling and observability basicsadvanced
  • Testing APIsadvanced
  • Application security basicsadvanced
Outcomes

Learning outcomes

  • Design and test a small authenticated API
  • Apply input validation and safe error responses
Project

Project specification

Design and test a small authenticated API with validation, safe errors, and documentation.

Problem statement · Illustrative
Clients need a small authenticated API that validates input, returns predictable errors, and protects a primary resource.
Primary user workflow · Illustrative
Authenticate → create or update a resource through a validated endpoint → retrieve it → observe correct status codes on invalid input.
Functional scope · Illustrative
API design, validation, auth basics, error responses, tests, and short API documentation.
Technical components · Illustrative
HTTP API, auth middleware or equivalent, persistence for one resource, validators, and automated API tests.
Data requirements · Illustrative
Learner-owned sample data only.
Testing expectations · Illustrative
Auth success, validation rejection, unauthorized access case, and at least one server error path with a safe response.
Known limitations · Illustrative
Not a full microservice platform. Rate limiting at scale, multi-tenant tenancy models, and payment APIs are out of scope unless published for a cohort.
What counts as completion · Illustrative
Working authenticated API, tests for critical paths, documentation, and a walkthrough of error contracts.

Examples

  • Validated REST API with auth, tests, and documentation

Deliverables

  • Working authenticated API
  • Automated tests for critical paths
  • API documentation

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 and automated checks where provided

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.