AZTableViewController | easy way to integrate pagination

Your completion handler for jobsNearByFetch returns an array of JobsNearBy, which you put into jobsArray

Then, you have a force cast of jobsArray to JobsNearBy, but it is an array, not a single instance of the object so the downcast fails and because it is a forced downcast your app crashes.

You could fix it by using as! [JobsNearBy], but it is better to change the signature of the completion closure to indicate that it returns [JobsNearBy] instead of Any; then you don't need to downcast anything:

You shouldn't use Any when you can determine what the actual type is. Also, you shouldn't use NSDictionary when working in Swift if you can avoid it. Also, avoid force downcasting and unwrapping whenever possible.

Stylistically the boolean success parameter and a separate failure closure is a bit odd too; you would typically have a single closure that returns an optional Error - If error is nil then the operation was successful. I would have:

func jobsNearByFetch(pageNumber: Int, completion:@escaping ( _ jobsNearByArray:[JobsNearBy]?, error:Error?) -> ()) {

This way you can use a single trailing closure.

You also need to look at your jobsNearByFetch as there are some return paths that don't call a closure.

Finally, you should look at the Codeble protocol as it can eliminate the JSON parsing code altogether.