Hi,
This is not a bug but a limitation due to the nature how the process engine’s persistence works. When you make the query, the timer job has not yet been flushed or committed to the database, because that happens only when the current engine command finishes. So the job query will not be able to find the new job yet.
Cheers,
Thorben
edit: Check out Lookup Timer Due date for a Boundary event from Task Create Listener for a question and solution very similar to your case.