REALjasonansley on Nostr: So I tend to approach “jobs” as roles, not a job. (It’s a mindset shift) Then I ...

So I tend to approach “jobs” as roles, not a job.

(It’s a mindset shift)

Then I ask “what role do I desire” or “can I thrive in”?

This answer comes from what Jim Collins terms the Hedge Hog Concept (venn diagram)
A. What can I be the best in the world at
B. What does the market need
C. What drives the economic engine (of my family) (what can I make money doing by providing more value than I’m being paid)

Now…when it comes to brass tacks so to speak, I like CVs more than Resumes.

CVs tend to show “what have you done lately” and in terms of projects and results

Resumes show work history (which I don’t care about when I’m hiring team members)

And that leads me to the role concept vs job. If you just want a paycheck then apply for and take any job but if you want to be on a team you need to think in terms of roles.

These days lots of AI is used to pre-filter applicants.

There are actually a few decent ChapGPT “gpts” that are like head hunters and help you craft job application specific CVs that get you filtered up and through instead of down and away.

I’ve attached an image of a few tools you can lean into in your job search

Also attached is a long list of the most common interview questions.

That being said, when I’m applying for a role, I like to ask as many if not more questions of the interviewer than they do of me. And I’m looking to connect based upon values (ie culture of the company) vs a “job” or “position”/title/paycheck.

PS
What type of role were you working in and what are your skills?