Bilguuntugs

Computer Science student · Product-oriented builder · Open to internships

Software that feelsconsidered, not assembled.

I build practical software with product thinking and a strong eye for clarity.

I care about products where interface, workflow, and implementation feel coherent.

01

Student tools with cleaner workflows

02

Calm, useful AI interfaces

03

Practical software with polish

About

A builder who cares about the structure behind the screen.

The interesting part of software is not just the code path. It is how the decisions around layout, language, interaction, and implementation combine into something that feels right.

I tend to start from real problems, repetitive workflows, and clunky communication patterns, then shape software that handles them with clarity.

Right now I care most about becoming the kind of builder who can take an idea from rough concept to something real, useful, and polished. Long term, I want to work where AI and product development meet.

Currently exploring

  • AI product design
  • System design fundamentals
  • Cloud deployment workflows

Open to

  • Internships
  • Collaboration
  • Meaningful product work

01

Start from friction

I look for repetitive, awkward, or overcomplicated workflows first, then design around what would make them feel obvious.

02

Make the interface carry weight

Good products should explain themselves through hierarchy, pacing, and interaction patterns instead of dense instructions.

03

Build for real use

I care less about flashy demos and more about whether the product would still feel strong after the fifth or fiftieth use.

Selected work

Work framed like products, not just repos.

The strongest signal on a portfolio is whether the projects feel scoped, useful, and thoughtfully presented. These are the ones that best represent how I think.

Student productivity platform

Study Flow

A student workflow product instead of a pile of disconnected tools.

Study Flow combines a Pomodoro timer, note-taking, task management, deadline tracking, and an AI assistant panel into one product. The goal was to make studying feel more continuous and less fragmented.

Challenge

Students constantly switch between timers, notes apps, task lists, and reminders, which makes studying feel more fragmented than it should.

Approach

I combined planning, focus, and execution into one dashboard so the workflow feels continuous instead of scattered.

Why it matters

This project best represents how I think across product scope, UI structure, and full-stack implementation at the same time.

Next.js · TypeScript · Prisma · Zustand · Tailwind CSS · SQLite

Study Flow

Tasks

Focus

Notes

Study dashboard

Daily flow

Focus block

25:00

Session

Deadlines

Database report02
Systems quiz03
Presentation draft04

AI-assisted communication tool

Message Reply

A faster response workflow without flattening personality.

Message Reply focuses on one narrow but common problem: rewriting similar replies again and again. The product is intentionally small, with the experience centered on speed, clarity, and editability.

Challenge

A lot of daily messaging is repetitive, but manual rewriting still takes attention and time every single time.

Approach

I focused the experience around a quick input-to-suggestion flow so the value shows up immediately and the interface stays lightweight.

Why it matters

This project shows how I think about AI as workflow support: useful, focused, and respectful of the user's own voice.

Kotlin · Android · Gradle · AI-assisted UX

Message Reply

Inbox

Draft

Suggested reply

Editable

SendEditRetry

Editorial content explorer

Astronomy APOD Explorer

An editorial interface for a dense public archive.

Astronomy APOD Explorer rethinks how a rich archive is browsed. Instead of forcing the user through a dated experience, it reframes the content with calmer hierarchy, clearer navigation, and more editorial pacing.

Challenge

The source archive is rich, but the browsing experience feels dated and makes discovery less inviting than the content deserves.

Approach

I simplified the flow around date selection, stronger content framing, and restrained motion so the imagery stays central.

Why it matters

This project shows my interest in turning dense or awkward information spaces into interfaces that feel much easier to explore.

React · TypeScript · NASA APOD API · Framer Motion

Astronomy APOD Explorer

Astronomy Picture of the Day

Date navigation

2026
Feb 21
Archive
Today

Reading rhythm

Profile

Still early, but already opinionated about quality.

I am in my second year of Computer Science, but the standard I am aiming for is already clear: useful products, disciplined implementation, and interfaces that feel composed rather than improvised.

Education

BSc in Computer Science (Undergraduate)

Xi'an Jiaotong-Liverpool University (XJTLU)

2024 - Present

Currently in my second year
Studying Computer Science with an AI focus

Working toward

Better judgment across product, interface, and implementation so I can contribute meaningfully to teams that care about craft.

Interface Systems

React · Next.js · TypeScript · Interaction design

I design and build interfaces that feel structured, clear, and intentional across desktop and mobile.

Application Logic

Node.js · REST APIs · Prisma · Full-stack product flows

I build APIs and data models that stay understandable, reliable, and practical for real product workflows.

Workflow & Delivery

Git/GitHub · Vercel · CI fundamentals · Iteration loops

I care about versioning, deployment, and iteration speed because polish is not just visual, it is operational too.

Contact

If the work feels aligned, I would be glad to talk.

I am looking for internships, collaborations, and teams that care about thoughtful product work. The easiest paths are below.

If you are building something useful, thoughtful, or a little ambitious, I would be glad to talk.

Best current way to reach me: GitHub or email.

I am most energized by products that reduce friction without losing personality. That usually means thinking through the interface, the workflow, and the implementation together instead of treating them as separate steps.