Yes, it's mostly fine for that. Not always ideal, sure.
> let's say, to poll a resource every second and know if a worker has finished
No, you generally shouldn't poll every second. You should POST a subscription and then the other end should POST you a notification.
If you are in a situation where you need to poll instead of subscribing and waiting, then, maybe use HTTP long polling, maybe poll less frequently than every second, maybe use something other than HTTP, but in any case you are in a suboptimal circumstance.
(Of course, whether you should use HTTP as a transport protocol is orthogonal to whether or not you should use a REST architectural style.)
(That's assuming HTTP, which btw is not the only protocol which can implement REST constraints)
Cannot say much about REST constraints outside of HTTP so excuse my ignorance on that. But I think it was clear the parent was referring to HTTP, or most possibly, GET and POST HTTP calls returning JSON.
Rather than retry every second, you retry on timeout.
Transactional CRUD (post a form, submit an email, add to cart) is pretty well adopted and standardized as HTTP, so probably use that (even backend to backend, if the contract fits CRUD resource semantics).
RPC (non-CRUD interactions) or streaming updates (e.g. a spinner in a app representing a pending job) or low latency (chat messages / presence status, etc.) don't really fit to HTTP requests so great (requiring e.g. polling) so you should look at alternatives (probably something proxied over a websocket in the case of a browser front-end app).
I have seen huge benefits, performance being one, communicating using ZMQ (at the cost of complexity and reliability). A worker, running on your computer, consuming data fed through a socket from a broker, running on your server.