Software Development Internship — 2 Months
Learners build a full-stack application with authentication, database integration, API validation, and automated tests. The track emphasizes engineering process—not just feature completion.
- Git
- Frontend
- Backend APIs
- Databases
- Auth
- Automated tests
Compensation terms are to be announced. Applications will not open until compensation, supervision, and legal review are approved and disclosed. No internship fee is charged.
Legal review of internship terms is still required before this opportunity can accept applications.
Program facts
- Duration
- 2 months
- Level
- Intermediate
- Weekly commitment
- Approximately 15–20 hours per week (subject to final program schedule)
- Delivery
- Online
- Availability
- Coming soon — interest registration available
- Compensation
- Compensation terms to be announced
- Mentor / supervisor
- Mentoring format is subject to program approval before open enrollment.
- Delivery owner
- Assigned before enrollment opens
- Certificate policy
- Completion recognition is subject to published requirements.
Audience, prerequisites, and selection
Audience
- Students and early-career developers
- Career transitioners with some programming background
Prerequisites
- Introductory programming experience
- Willingness to learn Git and web fundamentals
- Ability to commit ~15–20 hours per week
Selection criteria
- Introductory programming experience
- Willingness to use Git and learn web fundamentals
- Availability matching the weekly commitment
- Clear statement of learning goals
Responsibilities
- Define requirements and constraints for the assigned full-stack project
- Design system components, data flow, and API contracts
- Implement primary flows with error handling and input validation
- Write tests for critical paths and document known limitations
- Demonstrate the working MVP and explain design decisions
Topics covered through the project
- Programming fundamentals refreshfoundational
- Git and version controlfoundational
- Frontend development basicsfoundational
- Backend APIsfoundational
- Databasesfoundational
- Authentication and authorizationadvanced
- Input validation and error handlingadvanced
- Testingadvanced
- Application security basicsadvanced
- Deployment and documentationadvanced
Learning outcomes
- Ship a small full-stack app with auth and validated APIs
- Write automated tests for critical paths
- Explain architecture and security choices in writing
Project specification
Build a supervised full-stack application with authentication, validated APIs, tests, and documentation.
- Problem statement · Illustrative
- Users need a small authenticated application that stores structured data and exposes a validated API for the primary workflow.
- Primary user workflow · Illustrative
- Register or sign in → create or update a core record → retrieve it through a validated API → see confirmation in the interface.
- Functional scope · Illustrative
- Authentication basics, CRUD for one primary resource, input validation, error responses, and automated tests for critical paths.
- Technical components · Illustrative
- Frontend views, backend API, database persistence, auth layer, validation, and test suite.
- Data requirements · Illustrative
- A simple schema for the primary resource. No production customer data.
- Testing expectations · Illustrative
- Auth happy path, validation rejection for invalid payloads, and at least one authorization or error-path check.
- Known limitations · Illustrative
- Not a complete product platform. Advanced multi-tenant isolation, payment systems, and large-scale performance work are out of scope.
- What counts as completion · Illustrative
- Working MVP, milestone evidence, tests for critical flows, documentation, and a demonstration of architecture decisions.
Examples
- Build a full-stack application with authentication, database integration, API validation, and automated tests
Deliverables
- Working full-stack MVP
- Milestone demos against published rubrics
- Automated tests for critical flows
- Technical 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.
Evaluation criteria
How work is reviewed — clarity of decisions matters as much as a working MVP.
- Milestone demos
- Code review against published criteria
- Test coverage of critical flows
- Technical documentation
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
Ready to build something real?
Choose a pathway, review a program, and register interest when enrollment opens.