For some reason, my second thought on the whole idea of someone coming in to a company on a "gig" position (very short-term contract, essentially,) teasing out some meaning in the data they're handed, then flying off to their next "gig," strikes me as the classic "Dilbert" view of a consultant.  Zoom in at managements behest for something, generate a lot of pretty looking reports, then zoom out.

While I don't feel I fall into any of the categories that would most likely work "gig" spots that the article mentioned (Data Architects, Data Scientists) I feel that in order to generate meaningful information about a companies data, you need to have a better feel for where that data came from, what the business purpose of the data is, etc, than you could get on a "gig" time period.

Maybe I'm just a stodgy stick-in-the-mud who's never going to "get it," but I don't see gig jobs being something that's going to be around for a long time, not in any sort of professional field.  I see them as more appropriate to the sort of jobs that tend to be "one and done," say for example landscaping (come in, lay out the landscaping, put it in, collect the check, off to the next,) taxi driving (using your personal car, maybe only weekends to make a couple extra bucks,) etc.  I do feel a lot of the current so-called gig jobs, aren't (Uber, Lyft, that one that picks up your carry-out and brings it to you,) and that's going to get shown in court at some point...

But IT?
Probably not a good fit for "gig" jobs.