Yes, you can simply add another job step to use the DBCC SHRINKFILE statement.
However it is typically recommended that you not shrink the files on a regular basis. Doing so causes the database engine and disk subsystem to do extra work that it doesn’t need to do. If the log has grown to that size there is a reason for that, and the log will probably grow to that size again. Shrink the file after each log backup gives you a false sense of security.