Skip to content

teamleadercrm/vectera-coding-test

Folders and files

NameName
Last commit message
Last commit date

Latest commit

 

History

5 Commits
 
 
 
 
 
 
 
 
 
 
 
 
 
 

Repository files navigation

Vectera Coding Test

This repo contains the basics for the coding test. It includes:

  • Backend: Django + DRF skeleton with stubs and TODOs
  • Frontend: Angular skeleton (routing, service stubs, components)
  • Docker: Postgres + Backend
  • CI: Placeholder workflow that fails by default (you will fix it)

Target time: 4–6 hours. Complete the core tasks.

Getting Started

1) Run with Docker (DB + Backend)

docker compose up --build

Note: The backend image installs Python dependencies and runs migrations automatically.

2) Frontend (Angular)

cd frontend
npm install
npm start

3) What you implement

Backend (Django + DRF):

  • Data models for Meeting, Note, Summary
  • REST endpoints for meetings, notes, and summary flow
  • Simulated async summary using the provided services/ai.py stub
  • Basic validation, pagination, simple logging & /api/health/

Frontend (Angular):

  • /meetings list (title, started_at, note count, summary badge)
  • /meetings/:id detail (notes feed, add note form, “Generate summary”, summary panel)
  • Loading/error states, typed API models, clean module structure
  • Polling summary status until ready

Tests:

  • Backend: at least 1 model test, 1 happy-path API test, 1 validation/edge test
  • Frontend: at least 1 unit test (service or component)

4) Docs

  • Update DECISIONS.md with assumptions, trade-offs, and improvements.
  • Keep the timebox. Practical solutions are fine—avoid over-engineering.

About

Coding test for Vectera

Resources

Stars

Watchers

Forks

Releases

No releases published

Packages

No packages published

Contributors 2

  •  
  •