What to expect from this page?

Hi, before you begin understanding me, here's what to expect from this page.
This page is not built to tell you about my hobbies, my achievements or to justify myself as a person.

The motive here is simple, the following content just wants to make it easier for you to evaluate "is this guy worth giving a chance?" by answering questions like "will he be a good fit for the role and team?", "will he be able to understand our company's vision and mission?", "does his mindset align with our work ethic?" etc.

More importantly, it aims to give you an insight into what I bring to the table besides my technical abilities.

How is the above expectation fulfilled?

The page answers a different set of questions instead, chosen specifically to help you evaluate the ones above without me answering them directly. The reason is that it feels vague to simply say "I will work hard for the company" since it's easy to say a sentence like that with no way of actually verifying the intent behind it.

Therefore, instead of answering those questions directly, I have answered another set of questions specifically chosen to make it easier for you to evaluate whether my words and intent feel genuine and to infer the answer to the above questions in your own way.

I chose this approach and the questions below because I felt they will communicate what I want to the best. There's no way to say if this was the right call. Moreover, different individuals have different ways of viewing things so defining a clear method that will convince everyone is a non-trivial task. Therefore, After reading this webpage, it's up to you to decide that "is this a person who will live up to his words?" or "is he just all talk?".

What's something you're still working on about yourself?

I have learned to accept failure fairly easily. What I still struggle with is the frustration that follows a mistake I did not have to make. Losing to a stronger player in chess never bothers me. Blundering away a winning position does.

When I started playing, a blunder like that would send me into a tilt spiral, playing game after game out of rage instead of judgment, and losing most of them. It is a specific kind of frustration, spending half an hour calculating a winning line, only to hang a piece in one careless move.

What has changed is the pause before I react. I have learned to stop, breathe, and actually assess whether the game is still winnable, rather than playing on out of pride. If it is not, resigning and starting fresh beats burning another hour on a lost cause.

What I have not fully solved is the quieter part. I no longer carry one loss into the next game, but some part of me is still annoyed at myself for the mistake itself. The fix, I think, is to stop assigning blame entirely, not to the situation, not to circumstance, not to myself. Just accept what happened and move forward.

What's a strength you didn't earn easily?

I was running to catch a bus to a lecture on campus. I made it. Three stops in, the driver pulled over, it turned out he was on the wrong route, and we had to wait for the correct driver to arrive. Another bus on my route drove straight past us while we waited.

What stuck with me was not the delay. It was what my mind did in the seconds before I ran for that first bus. If I don't catch this bus, I'm late. If I'm late, I miss the lecture. If I miss the lecture, I fall behind on the module. If I fall behind, I do worse in the exam. If I do worse in the exam, my degree suffers. The chain kept going, all the way to imagining a worse career because of one bus.

None of that was a real assessment of the situation. It was fear wearing the costume of planning. I was making a decision to avoid an imagined outcome ten steps down the line, not responding to what was actually in front of me.

Since then, when I catch myself spiraling down a chain like that, I ask one question: so what if it happens? Not to stop caring about the outcome, but to separate what I can actually act on right now from what my mind has already decided to fear. It has not made me fearless. It has made my decisions better.

Tell me about a time something didn't go the way you planned.

The ECG Signal Classification Challenge required sorting heartbeat readings into three categories. At first it looked like a standard machine learning problem, preprocess the signal, train a model. After doing exactly that, I was at my wit's end. Nothing I changed was moving the needle.

I understood early on that simply training a more complex model would not fix this. So I stepped back and asked a more basic question: how does a model actually tell one class apart from another? It needs features that genuinely separate them, and I did not have any that did.

The real gap was not in the model, it was in the data I was feeding it. So I stopped iterating on the model and went looking outside machine learning entirely, reading about how doctors actually read an ECG signal, and academic papers that had tackled similar classification problems on other datasets.

Most of it did not directly apply. But I found something usable, the characteristics of specific signal peaks doctors use to judge whether a heartbeat is healthy. I extracted those peaks from the raw signal and compared them against rough benchmark values I had found. The estimates were imperfect, but they gave the model genuinely new patterns to work with.

That decision to step outside the standard workflow is what turned the project around. I placed 2nd in the ECG classification challenge at UoN.

What do you actually want out of a job right now?

What I want in three words: meaningful, challenging work. At this stage in my career, income, benefits, and leave count are not my priority. That does not mean compensation does not matter, it is just not the first thing I optimise for when evaluating an opportunity. I'd rather understand the role, the problems I'd be solving, and the team first. If there's a strong mutual fit, I'm happy to discuss compensation at that stage. What I am chasing is learning, growth, and trajectory, and the work I do matters more to me than the job title on it. I am young, and I believe prioritizing that now, while I can afford to, will take me far later. Whether the company is an early-stage startup or an established, stable workplace, my priority stays the same: I want to make real impact from day one.

I am ambitious, but I am not naive about how work actually goes. There will be short stretches, onboarding, a quiet season, a gap between projects, where I will not be contributing at full capacity. That is fine, as long as it stays temporary and does not become the norm.

Nothing is permanent, and one day my path and this company's will diverge. What I can offer is how I handle that day when it comes: I will leave the way I worked, professionally, having finished what I owed, and grateful for the trust I was given to try.

Where do you see this going, for you, in the next 5 years?

In five years, I want to be the person a team hands an ambiguous, complex, unsolved problem to, not because I have all the answers, but because I have a track record of finding them. Right now I am building that track record project by project. In five years, I want it built through real production systems, at scale, with real consequences attached to getting it wrong.

Concretely, that means growing from someone who builds and evaluates models into someone who owns the backend these systems run on, latency, failure modes, monitoring, the parts that do not show up in a notebook. I am already leaning that way, most of my projects end in a deployed API, not a metric on a slide.

I also intend to keep sharpening the fundamentals underneath all of this. Solving any serious problem takes real problem-solving, critical thinking, and pattern recognition, and I believe competitive coding is one of the sharpest ways to build those. That is why I am working toward 5-star status on CodeChef, not because interviews ask for it, but because that level of fluency is what it actually takes to solve complex, unseen problems under real-life constraints like optimization and limited time.

None of this is a fixed script. But the direction will not change: more ownership, harder problems, and systems that matter once they are live, not just once they are trained.

Note: Curious about my formal qualifications, achievements, what I do outside my work, or the type of roles I am targeting?

Find that on the About page.