Airbyte is an open-source data integration engine that helps you consolidate your data in your data warehouses, lakes and databases.

Airbyte

<https://docs.google.com/presentation/d/1LBR0kiwsMLiyQD4YUH8rI0w28J4C8FsXZh2N4gG5GtE/edit?usp=sharing>

So where does engineering stop and analysts start. This is a big problem we are trying to streamline.

This is a great question - I’m not sure if there’s a one size fits all answer as it depends a lot on the culture of the organisation but a couple of things I’ve seen:
• This is most unclear today at the parts that touch eng and data infrastructure, so thinking of data ingestion and maybe ELT/ETL too - Tools like Airbyte are helping put this more in the hands of analysts but engineering is usually still in the picture too. 
• Generally once data is in the warehouse, it enters the data analysts domain and they can take ownership of it from there for the most part (transformations, reverse ETL, BI etc.)
This is probably a huge oversimplification though ^^.
The guiding principle for me is that analysts should be responsible for the context, shape and content of the data and engineering should be responsible for it’s movement and availability.