About the Creator

Independent Builder ITER, SOA University

Mrinall Samal builds campus software with product taste and engineering discipline.

B.Tech CSE student working across interface systems, backend architecture, and the details that make software feel trustworthy.

ITERasn hub is the clearest expression of that work so far: a student platform shaped end to end, from public-facing identity and responsive UI to APIs, data flow, analytics, and AI-assisted tools. The goal is not to make something flashy. It is to make something clear, fast, and credible.

Current direction

Refining student software into a product experience that feels deliberate instead of improvised.

Product lens

Translating student workflows into interfaces that feel clear, premium, and usable.

Execution

Comfortable moving from page structure and motion systems into APIs, auth, and data flow.

Priority

Making every screen feel intentional, from wide desktops to narrow mobile devices.

Quick map

A cleaner way to scan the work, focus, and collaboration fit.

Start with the key signals below, then jump straight to the part of the page that matters to you.

Strength UI systems, backend delivery, and responsive polish
Best fit Internships, product teams, and frontend-heavy software builds
Current goal Make ITERasn hub feel dependable on every screen size

Approach

Built around clarity, systems thinking, and restraint.

The most interesting part of software is where product decisions and engineering decisions start affecting each other.

Most academic software solves the function and forgets the experience. My work sits in that gap: translating cluttered student workflows into interfaces that are easier to understand, easier to trust, and easier to come back to.

At ITER, the classroom sharpens the fundamentals. Outside it, hands-on product building forces better decisions around structure, state, data, responsiveness, and maintainability. That combination is what makes these projects valuable to me.

What I care about most is building something coherent, where the visual layer, interaction design, and backend logic all feel like parts of the same system instead of disconnected pieces.

01

Clarity over noise

Reduce friction, tighten hierarchy, and keep the interface useful under real student workloads.

02

Systems over one-offs

Reusable patterns, cleaner structure, and decisions that scale beyond a single screen or feature.

03

Polish with purpose

Motion, surfaces, and copy should reinforce trust, not compensate for weak product thinking.

Academic Path

Formal training, applied through real product work.

A foundation in computer science, reinforced by building outside the syllabus.

01

B.Tech in Computer Science and Engineering

2024 - 2028

ITER, SOA University, Bhubaneswar

Focused on algorithms, data structures, web technologies, databases, and software engineering while building live product experience alongside the degree.

Full-stack development Database systems Software engineering
02

Higher Secondary Education

2021 - 2023

Science Stream with Computer Science

Built the base in mathematics, analytical thinking, and computing that now supports product development and problem solving.

Mathematics Computer science Problem solving

Capabilities

A builder's stack, not a checkbox list.

Each area combines tools with the kind of decisions required to ship a usable product.

Frontend systems

Interfaces with hierarchy, motion, and responsive discipline.

HTML, CSS, JavaScript Core

Landing pages, dashboards, responsive layout systems, and component polish.

React and component thinking Applied

Structured UI work with reusable patterns and maintainable interaction logic.

Motion and presentation GSAP

Animation used to improve rhythm, orientation, and perceived quality.

Backend architecture

APIs, auth flows, data models, and the plumbing behind the experience.

Node.js and Express Primary

Service design, route architecture, middleware, and feature delivery.

PostgreSQL and MySQL Production-minded

Schema thinking, data flow, and backend decisions shaped around real use cases.

Authentication and integrations Reliable

JWT, role-based access, external services, and feature coordination across layers.

Product delivery

From code to deployment, with enough rigor to keep shipping cleanly.

Git, GitHub, VS Code Daily

Versioned workflows, issue-solving, and steady iteration across the stack.

PWA and mobile behavior Shipping

Offline-minded thinking, installation flows, and touch-friendly interfaces.

Deployment stack Render, Firebase, Docker

Pragmatic infrastructure choices that support fast iteration without unnecessary weight.

Selected Work

One flagship product, supported by focused systems work.

The emphasis is on building real surfaces and tightening the details that make them feel finished.

Interface direction

Public-facing brand and landing systems

Designing the visual layer so the product has a stronger point of view, clearer hierarchy, and less of the interchangeable look common in generic student platforms.

Visual systems Responsive layout Motion design
Delivery layer

Mobile-first and platform behavior

Extending the product with PWA thinking, responsive patterns, and production-minded delivery so the experience stays useful beyond a single screen size.

PWA Touch UX Deployment

Stack Notes

Pragmatic tooling, chosen to keep the product moving.

The stack favors speed of iteration, maintainability, and enough depth to support a growing platform.

Why this stack

Lean enough to move fast, deep enough to support real product complexity.

ITERasn hub uses practical technologies that support multi-role logic, real-time capability, structured data, and a responsive experience without adding unnecessary weight.

Node.js Express.js PostgreSQL JavaScript HTML5/CSS3 Socket.IO JWT GSAP Chart.js PWA Bcrypt Git Vercel Render

What it enables

01 Multi-role experiences with shared product consistency
02 Structured academic data, analytics, and content flows
03 Responsive delivery across desktop, tablet, and mobile
04 Real-time and AI-assisted features layered into the platform
Project context

Student-built, independent, and intentionally experimental.

ITERasn hub is an educational project and is not an official ITER or SOA University product. Any demo content or simulated data is used to prototype features and showcase engineering work.