Hacker News new | past | comments | ask | show | jobs | submit login

What kind of analytics are you talking about? Is it for your clients to use, or to measure your own engineers' performance, or is it product telemetry, or etc etc etc?



I added more information above to clarify, thank you for asking. We're building an EdTech platform. The objectives for the job are:

- faster development

- happier junior devs: they demand more guidance in the given area

- better product, measured by usage, referrals and learning progress


OK, your updated description is

> 1) give users an overview of and feedback about their activity, 2) create effective and evidence-based interventions, and 3) improve learning outcomes and engagement.

...which is product telemetry; on the technical side you want someone who knows how to use GTM or mixpanel or (any of dozens of other competitor tools) to track what users are doing in your app, and on the analytics side you want someone who knows how to interpret that data and create meaningful interventions or product changes as a result

The first part is relatively simple, any developer can figure out how to install one of these tools and start logging events. The second part probably needs an education SME who can take that data and do something meaningful with it, or a strong product lead (who would look at it more from a features-and-workflows point of view than from an educator point of view, different paths to maybe similar results).

Neither of those people would be who you'd want involved in deciding where to store the data or how to access or process it; that's more in the database admin realm.

Your list of objectives here, though: > - faster development > - happier junior devs: they demand more guidance in the given area > - better product, measured by usage, referrals and learning progress

The first two are completely unrelated to the above: the first is more about measuring cycle time, velocity, all that fun scrum/agile stuff; the second is ensuring that your junior devs have good mentors and managers. The third one is more of a restatement of the product telemetry goals.

Longwinded way of agreeing with many of the other responses you're getting: the reason you're having a tough time coming up with a reasonable job title is that you're describing at least four unrelated jobs.

(I'm not currently in edtech but have a long history there, and some in a couple of those unrelated roles; happy to discuss further if you like, I admit partially because I'm curious to see what new startups are doing in that space ;)




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: