Strangely, I think almost the opposite - I think it'll take a lot of "scripting language" tasks, but not much of the system programmers jobs.
Coming from a scripting language background, Go feels like a step forward in performance, without many of the headaches of C++ or Java.
But speaking to people who write C++ for a living, they see little or no use for go for them, as they need either the performance or flexibility of a lower level language like C++ - that's why they haven't moved to an alternative a long time ago.
Be sure to do the same jobs you would do in Python, keep track of how long it takes, and measure the difference - otherwise you are optimizing prematurely with snake oil.
I'm pretty sure doing the same job twice and measuring the time taken each time is a guarantee that whatever you do, it'll take twice as long and bore you to death...
Coming from a scripting language background, Go feels like a step forward in performance, without many of the headaches of C++ or Java.
But speaking to people who write C++ for a living, they see little or no use for go for them, as they need either the performance or flexibility of a lower level language like C++ - that's why they haven't moved to an alternative a long time ago.