I'm Kiran. I think deeply and build practically.

I like understanding how complicated things actually work, sitting with a problem until it starts to make sense, and then building something honest around it. My resume covers the job. This page is closer to what it's like to talk to me.

Based in: Texas, working across time zones
Currently: AI GTM Engineer, Workera
Learning: French, systems design and architecture

How I work

How I think through a messy problem.

01
Listen
interviews, calls, replies
02
Model
shape the real problem
03
Build
smallest useful version
04
Measure
honest before flattering
05
Compound
loop back, faster

01
Listen
interviews, calls, replies
02
Model
shape the real problem
03
Build
smallest useful version
04
Measure
honest before flattering
05
Compound
loop back, faster

Where I do my best work.

A lot of it is about the people in the room. I'm at my best around teams that are curious, honest, and okay with sitting in the mess for a bit before jumping to a solution.

Right fit

+Teams that enjoy experimenting and treat being wrong as part of the work.
+Leaders who want evidence behind a decision, not just confidence.
+Small teams taking on ambitious problems with more curiosity than headcount.
+People who share ideas openly and give feedback without dressing it up.
+Groups that care as much about how they work together as what they ship.

Probably not

·Rooms where the loudest opinion always wins.
·Teams that need the answer by Monday and don't want to hear questions first.
·Places where feedback is polite but never honest.
·Environments that treat curiosity as a distraction from execution.
·Anywhere the work is meant to look impressive more than be useful.

What keeps me going.

Curiosity.

I like understanding how things actually work. One question usually leads to five more, and I am happiest when I am somewhere in the middle of figuring them out.

Getting the details right.

I tend to notice when something feels slightly off, unclear, or unfinished. I like going back through the small things because they usually shape how the whole thing works.

Saying what I actually think.

I value direct conversations, especially when something feels off. Clear disagreement is usually more useful than everyone politely moving in the wrong direction.

Progress I can see.

I like being able to look back and see that something is clearer, better, or more useful than it was before. Even small signs of progress keep me engaged.

Getting better at something.

I like the slow, visible progress that comes from staying with something. A new skill, a difficult hike, or a problem that finally starts making sense. Seeing myself improve keeps me interested.

Having something to look forward to.

A trip, a new place, a project I care about, or even a really good meal. I like having something ahead of me that makes the ordinary weeks feel a little more exciting.

After the small talk

Questions people actually ask.

Q.01

What do you mean when you say you build systems?

I mean the parts of growth work that happen behind the scenes: how accounts are researched and scored, how leads are routed, how outreach gets triggered, and how teams know what to act on. Sometimes I build the workflow from scratch. Sometimes I fix what is already there.

Q.02

Are you a marketer or an engineer?

A little difficult to categorize, honestly. I started in marketing, moved into analytics, and learned to build because I kept running into problems that campaigns alone could not solve. These days, I usually work across all three.

Q.03

How technical are you?

Technical enough to design the system, work with APIs and data, read and debug code, and build the first version myself. I also know when something needs a stronger engineer. That distinction matters.

Q.04

How did you end up in GTM engineering?

Gradually. I became more interested in the machinery underneath the campaign: where the data came from, how leads were scored, why teams were repeating the same work, and how the whole system could run better. Eventually, that became most of my job.

Q.05

Why are you so interested in AI?

It has changed how quickly I can move from an idea to something real. I use it constantly, while staying careful about where it is unreliable, overconfident, or unnecessary. Figuring out where it genuinely improves the work is the interesting part.

Off the clock