Home / Project Life
● 9 AM – 6 PM · Sprints · Jira · Figma

Life on a real project

Once you're on a project, you work exactly like our engineers do: full working days from 9 to 6, in sprints, building from Jira stories and Figma designs, with your code reviewed and shipped to production.

// a typical project day

9 to 6, like a professional

No "come whenever you like." Projects run on real working hours, real standups and real deadlines, because that's what employers and customers expect.

9:00

Daily standup

15 minutes: what you did yesterday, what you'll do today, what's blocking you.

9:15

Build

Pick up your Jira story, open the Figma design and start coding on your feature branch.

1:00

Lunch break

Recharge.

2:00

Build & pull request

Finish the story, write tests and raise a pull request.

4:30

Code review & QA

Seniors review your PR. You fix comments and review a teammate's code.

5:30

Wrap-up

Update Jira, push your work and note tomorrow's plan.

6:00

Log off

See you at standup.

// how stories are given

Your work arrives as Jira stories

Every project is broken into epics, sprints and stories with story points, exactly like at a product company. This is the board from a real Incred student project: CampusMind, an AI study assistant, built by a team of 4.

SpacesCampusMind: AI Study Assistant (Student Project)
RSPKANMJ
BoardBacklogTimelineReports
CM Sprint 2 · ActiveEpic: E2 Authentication & Users · 17 story points
To Do2
E2: Auth

Profile page

CM-193MJ
E2: Auth

Admin: invite and manage faculty

CM-203AN
In Progress1
E2: Auth

Login with JWT access + refresh tokens

CM-16You5RS
In Review1
E2: Auth

Role-based access control

CM-17PR #423PK
Done1
E2: Auth

Forgot / reset password

CM-18✓ merged3AN
Backlog4 sprints · 4 epics · 21 stories
CM Sprint 1Done6 stories16 pts
▮CM-9Set up MERN monorepo E1: Project Setup & DevOpsDone3RS
▮CM-10Linting, formatting and commit hooks E1: Project Setup & DevOpsDone2PK
▮CM-11Environment config and secrets handling E1: Project Setup & DevOpsDone2AN
▮CM-12MongoDB connection and base models E1: Project Setup & DevOpsDone3MJ
▮CM-13Docker Compose for local development E1: Project Setup & DevOpsDone3PK
▮CM-14Centralised error handling and logging E1: Project Setup & DevOpsDone3RS
CM Sprint 2Active5 stories17 pts
▮CM-16Login with JWT access + refresh tokens E2: Authentication & UsersIn Progress5RS
▮CM-17Role-based access control E2: Authentication & UsersIn Review3PK
▮CM-18Forgot / reset password E2: Authentication & UsersDone3AN
▮CM-19Profile page E2: Authentication & UsersTo Do3MJ
▮CM-20Admin: invite and manage faculty E2: Authentication & UsersTo Do3AN
CM Sprint 3Planned5 stories17 pts
▮CM-21Create and manage courses E3: Courses & Study MaterialTo Do3MJ
▮CM-22Upload study material to S3 E3: Courses & Study MaterialTo Do5PK
▮CM-23Organise material by unit/topic E3: Courses & Study MaterialTo Do3RS
▮CM-24Student course enrolment E3: Courses & Study MaterialTo Do3AN
▮CM-25Browse and preview material E3: Courses & Study MaterialTo Do3MJ
CM Sprint 4Planned5 stories23 pts
▮CM-26Delete / replace a document E4: AI Study AssistantTo Do3AN
▮CM-27Chunk and embed documents (RAG pipeline) E4: AI Study AssistantTo Do5RS
▮CM-28Ask questions over course material E4: AI Study AssistantTo Do5PK
▮CM-29Auto-generate quizzes from notes E4: AI Study AssistantTo Do5MJ
▮CM-30Chat history per student E4: AI Study AssistantTo Do5AN
// inside a story

Every story tells you exactly what "done" means

No vague instructions. Each story has a user story, acceptance criteria, a linked Figma design and a definition of done.

E2: Authentication & Users / CM-16

Login with JWT access + refresh tokens

User story

As a student, I want to log in securely with my email and password, so that my session stays active without logging in again every time.

Acceptance criteria

  • Login form matches the Figma frame "Login – Mobile"
  • On success, API returns a 15-minute access token and a 7-day refresh token
  • Refresh token stored in an httpOnly cookie, never in localStorage
  • Access token auto-refreshes silently before expiry
  • Wrong password shows an inline error; 5 failed attempts lock the account for 10 minutes
  • Unit tests for the auth service; API tests for /login and /refresh

Definition of done

✓ Code reviewed✓ Tests passing in CI✓ Matches FigmaDeployed to stagingDemoed in sprint review
// designs in figma

You build from real Figma designs

Before a sprint starts, every screen is designed in Figma. Developers build pixel-perfect from these frames, just like at a product company.

CampusMind / App Screens v2
▸#▢✎T💬
RSMJShare
Login – Mobile · linked to CM-16
MJ
Use 12px radius on inputs, per design system
Dashboard – Desktop · E3 Courses
DashboardCoursesAI AssistantQuizzesProfile
Good morning,Riya 👋
Search notes, units…
DBMSUnit 3 · Normalization
72% complete
Operating SystemsUnit 2 · Scheduling
45% complete
Computer NetworksUnit 4 · TCP/IP
60% complete
✦ Ask CampusMind anything about your syllabus…Ask
AI Assistant – Mobile · E4 RAG
✦ CampusMind AI DBMS · Unit 3
Explain 2NF with a simple example
A table is in 2NF if it's in 1NF and every non-key column depends on the whole primary key.

Example: in (StudentID, CourseID, StudentName), StudentName depends only on StudentID, so move it to a separate Students table. 📄 Unit3_Notes.pdf · p.12
Give me 3 practice questions
Ask a question…➤
AS
Citations must link to the exact page of the uploaded PDF
// the sprint cycle

Every sprint, the same professional rhythm

01

Sprint planning

Pick stories, estimate story points, commit as a team.

02

Daily standups

15 minutes every morning at 9:00.

03

Build from Figma

Feature branches, clean commits, tests.

04

PR & code review

Every line reviewed by a senior engineer.

05

Ship

CI/CD to staging, then to production.

06

Demo & retro

Show what you built. Improve how you work.

Ready to work on a real project?

Apply for the January 2027 paid internship batch.

Apply now