More logistics than problem‑solving.

Practising without knowing where it was going.

As a student preparing for interviews at both big-tech and local companies, the process often felt indirect. I rarely knew whether to go back to the fundamentals, follow a general problem list, or search for a specific company on LeetCode and hope I was practising the right things.

Even after finding a list, I struggled to follow it consistently. There was no clear end to a session. Some days I would keep going for too long; on others, I would stop before doing enough meaningful work. Without a realistic boundary or a visible sense of progress, the discipline was difficult to sustain.

The problems I struggled with were also the ones most likely to disappear from my practice. When I couldn't find an answer, I would read the solution, feel like I understood it, and move on. What I really needed was for that problem to come back later, when I could test whether I understood the reasoning or had simply recognized the answer.

That is why I started Pebble. You bring the time and do the thinking; Pebble helps decide what deserves your attention today.

Pebble began as something I wanted to use myself. Once I saw that it made my own practice more focused and honest, I wanted to make it available to other people facing the same difficulties. Helping others through what I have learned has always mattered to me. Pebble is one way I can use the skills I have built over the past few years to offer something genuinely useful.

WHERE THE PREP HOUR ACTUALLY WENT

{{ b.label }}

{{ b.logisticsLabel }}{{ b.logisticsMobile }}

{{ b.solvingLabel }}{{ b.solvingMobile }}

When code becomes easier to generate, judgment becomes more valuable.

People say learning data structures and algorithms is pointless now. I think solving these problems is deeply underrated — and more valuable in this era, not less. When a model produces three plausible solutions, the person who can tell which one holds, why it holds, and where it breaks is the one making the decision. Everyone else is copying with confidence.

Being able to juggle between solutions and read them profoundly is the edge — against a lot of code written on a very surface-level understanding.

WHAT I HOPE THIS HELPS BUILD

A quieter kind of confidence.

Starting a first job and feeling unsure of yourself is common. In my own experience, understanding the structures, algorithms and language underneath the work made unfamiliar problems feel a little less intimidating.

I hope Pebble can help others build some of that same steadiness over time — enough to explain a trade-off, ask a better question, or trust their reasoning when the answer is not obvious.