Alperen Guntekin

How I got here

I started as a software engineer: React, React Native, TypeScript, some backend work, the usual generalist path. Building Shotlingo is where that turned into something narrower. It's a real product with real users, so most of the work stopped being "ship the feature" and became "check whether the feature did anything": whether a change actually moved a number, and whether the number I was looking at was even the right one to trust.

That checking is most of what I do now: less building growth features, more building and auditing the measurement underneath them: the same engineering, pointed at a different question. "Growth engineer" is the label for that shift, not a rebrand.

What I believe about app measurement

Most app teams are optimising against numbers they cannot trust, and almost nobody checks first. The tooling encourages it. Every dashboard renders a confident figure, none of them agree, and there is no error state for "this number is wrong", only a number.

So the work usually starts one step earlier than people expect. Before asking which paywall converts better, it is worth knowing whether your revenue reporting agrees with itself, whether the same user is one user in every system, and whether a test can detect the effect you are looking for at your traffic. Those are boring questions with checkable answers, and skipping them is how teams spend a quarter acting on a difference that was a reporting artefact.

The second thing: most of the advice in this space is not wrong so much as unfounded. "Run the test for two weeks." "Five hundred conversions per variant." Those are not derived from anything. They are not functions of your baseline, the effect you want to detect, or your funnel shape. A vendor publishing a round number instead of a calculation is telling you they would rather you ran the test than ran it properly.

I do not think this is a hard problem so much as an unglamorous one. Measurement work does not demo well and it does not make a good screenshot. It is also the thing that decides whether everything downstream of it means anything.

What I don't do, and who this isn't for

• I don't run paid acquisition, design creative, or manage ad accounts. I build and check the infrastructure that tells you whether what you're already doing is working, not the campaigns themselves.
• I don't have case studies, testimonials, or a client list to show you, because none of that exists yet. What does exist (the product, the shipped apps, the datasets) is listed at /projects.
• I work alone, on one paid engagement at a time, two clients at most. There's no team to hand you off to. The current offer is at /work-with-me.
• If your app is pre-revenue, or you don't have real numbers yet to reconcile, I'm not useful to you right now.