4 ms·
I almost took a "big data" data scientist job about a year ago with a local company. After talking to a number of their engineers, it became quite clear to me
by donatj 9y ago
I almost took a "big data" data scientist job about a year ago with a local company.
After talking to a number of their engineers, it became quite clear to me that instead of a data scientist, they just badly needed a DBA / someone with ownership and a complete vision of the data structure.
They had no foreign keys, poorly 'designed' indexes, and tons of redundant tables with no rhyme or reason to them.
They'd organically grown their database with hardly any review. They did not have big data, they just had a big mess. And wanted someone else to clean it up.
- flor1s 9y agoMaybe they should have a data warehouse (which is typically denormalized) instead of a database (which should be normalized)?
- donatj 9y agoThey had a data accessibility / source of truth issue. You need to normalize before you denormalize or else you're just spreading the mess into the warehouse.
- adaml_623 9y agoI'll bet they found they got 10 times more applicants for a data scientist role as opposed to a dba/sql/data engineer.
- vazamb 9y agoBut what's to point? You will get a lot of applicants from non-cs backgrounds. Not only will they be unprepared for the job but also most likely very unhappy with their tasks.
- gowld 9y agoThe point is that you can get paid more by calling yourself a data scientist than a DBA, at the moment.