hey, i'm bibin |

I like to understand why we're building something before I start writing code. If a feature hasn't been fully thought through from the user's perspective, I'll probably slow you down and make you think about it more.

I'm upfront about what I think and I don't sugarcoat technical realities. I expect the same from the people I work with, and I don't get offended when someone is direct with me.

I've worked across deep mobile architectures—from high-frame-rate SwiftUI gesture systems to complex React Native bridging and enterprise-scale SDK integrations. I'm good at asking the right questions and building a rock-solid understanding of how things work under the hood.

On most teams I've worked with, I've had to make architectural decisions that nobody had a clean textbook answer to. I'm used to taking ownership when requirements are ambiguous.

"I keep choosing challenging mobile problems because I like being in rooms where I'm slightly out of my depth. That's where I learn the most, and that's how I approach engineering in my life too."

I do my best work with ambitious teammates, difficult problems, and strong trust. Those things matter to me more than company size or scale. I want the people I work with to feel like hard problems got a little more manageable when we were in the room together.