# Eric's thoughts on a Motif role

Overall, I see myself playing full-stack developer with a focus on analytics and customer touchpoints.

I've listed a few ideas for projects that I could take on and drive forward. I recognize I'd be playing on the team: aligning with the group, doing a bunch of engineering myself, and pulling in expertise & more resources where applicable.

There is a decent amount of breadth to these projects. I don't have much of a bias for certain projects over others – just a desire to plug in where I can be most valuable.

### Projects

Engineering – immediate needs, probably:

- Add ability to save configurations/views
- Add ability to save specific metrics
- Add dynamic sampling. Expose cost/speed vs accuracy tradeoff to the user. Compute a barometer for accuracy

Engineering – analytics features:

- “Autometrics” for sequences, data profiling, data quality metrics
- Cycle detection, pattern recognition, sequence clustering
- Event type grouping to reduce cardinality
- Create “recipes” — pre-baked views & metrics for given domains. Assuming there’s an elegant way to map customer event types to recipe event types
- AutoML to predict sequence progression. See if a model’s feature importance can reveal reasons for follow-on events

Engineering – other:

- Instrument the app with logging; set up Amplitude/Mixpanel/Posthog to learn more about the competitors (h/t Theron)
- Support more data warehouses
- Productize an onboarding flow

Sales & marketing:

- Give demos and do user interviews, help iterate towards the best use cases
- Write docs, tutorials, case studies, content marketing
- Play ‘solutions architect’ – help potential customers think through their data infrastructure & BI stack. If needed, do data engineering consulting work for customers to make their data Motif-ready (while data prep is not a part of the product)
- Customer support/success. Consult on customer projects