How shivamrawat1/techtonic works
Project type and purpose
• This is a full-stack Django web application for simulating both technical and behavioral interviews, providing structured feedback (STAR, UMPIRE) and candidate assessment.
• Key domains/modules: “users” (authentication, dashboard, landing pages), “interview_technical”, “interview_behavioral”, “assessments” (analysis & scoring).
File structure
• Top-level:
• manage.py, Dockerfile, cloudbuild.yaml, deploy.sh: orchestration and deployment
• capstone_django/: core Django settings, middleware, URL routing
• users/, interview_technical/, interview_behavioral/, assessments/: four Django apps
• staticfiles/: collected static assets
• node_modules/: front-end assets for any JS build
• Each app follows Django’s MVC/MVT: models.py, views.py, templates/, static/, services/ or utils.
• “openai_client.py”, “deepgram_service.py”, “gtts_service.py”: external AI/voice integrations.
• CI/CD: cloudbuild.yaml, crontab, Dockerfile, Procfile, start.sh indicate Docker/GCP/Heroku pipeline plus scheduled tasks.
README for additional insights
• Uses Python 3.12, pip, npm.
• Runs migrations, collects static files, then launches via Django’s runserver (but production likely through Docker + Gunicorn).
• Environment variables loaded from .env.local.
Elements
• Clear labels for: Browser, CDN, Load Balancer, Nginx, Gunicorn, Django apps (users, interview_technical, interview_behavioral, assessments), Database, External APIs, Scheduler, CI/CD
– HTTP(S) requests/responses
– Data flow between views → services → external APIs → models
– Build/deploy flow
– Another for core app layer (Django + Gunicorn)
– Another for persistence (Database)
– Another for external services (OpenAI, Deepgram, GTS)
– A different style for CI/CD pipeline