I am stuck into two situations: I designed the wizard attached below for Signup Purpose but inside dashboard user will be "posting job" and post job has few steps as well. So using the same Wizard for job posting is fine or should I introduce new wizard style?
Aim for as few patterns as possible, applied consistently across the application.
Assuming your original design (the Signup wizard) has been tested, and meets the acceptance criteria (success metrics) for your app, you now have a pattern which helps a user:
- navigate a series of meaningful steps and inputs which rely on a specific order (either for implementation purposes/constraints, or to align with a users understanding) to create a new object in the system (an account in the first example you have).
Since you've now established a successful implementation of the Wizard pattern, don't make the user learn another interaction pattern to achieve a similar outcome if possible.