home.social

#jobsearch — Public Fediverse posts

Live and recent posts from across the Fediverse tagged #jobsearch, aggregated by home.social.

  1. Behavioural interview questions ("Tell me about a time when…") aren't fishing for a polished story. They're checking whether you can explain a real situation clearly: what happened, what you did, and what changed because of it. A simple structure that keeps answers tight: • Situation — one or two sentences of context. Who, where, what was at stake. • Task — your responsibility in that moment (not the whole team's). • Action — what you personally did, step by step. This is the meat; name tools, trade-offs, and decisions. • Result — the outcome, ideally with a concrete measure or lesson. If it went poorly, say what you'd do differently. Common traps: starting centuries ago, saying "we" so much the interviewer can't tell your part, or finishing with "and then it was fine" and no result. Practice out loud with two or three real examples from the last couple of years — delivery under pressure, conflict, a mistake you fixed, influencing without authority. Rehearse the Action and Result hardest; Situation and Task should be short. You don't need theatrical stories. You need clear ones that sound like you. What's the behavioural question you find hardest to answer well — and how do you usually prepare for it? #JobSearch#CareerAdvice#InterviewTips#InterviewPrep#Careers

  2. Behavioural interview questions ("Tell me about a time when…") aren't fishing for a polished story. They're checking whether you can explain a real situation clearly: what happened, what you did, and what changed because of it. A simple structure that keeps answers tight: • Situation — one or two sentences of context. Who, where, what was at stake. • Task — your responsibility in that moment (not the whole team's). • Action — what you personally did, step by step. This is the meat; name tools, trade-offs, and decisions. • Result — the outcome, ideally with a concrete measure or lesson. If it went poorly, say what you'd do differently. Common traps: starting centuries ago, saying "we" so much the interviewer can't tell your part, or finishing with "and then it was fine" and no result. Practice out loud with two or three real examples from the last couple of years — delivery under pressure, conflict, a mistake you fixed, influencing without authority. Rehearse the Action and Result hardest; Situation and Task should be short. You don't need theatrical stories. You need clear ones that sound like you. What's the behavioural question you find hardest to answer well — and how do you usually prepare for it? #JobSearch#CareerAdvice#InterviewTips#InterviewPrep#Careers

  3. I might have to start applying for architecture jobs. Seems like science doesn’t like me 😬 #JobSearch

  4. I might have to start applying for architecture jobs. Seems like science doesn’t like me 😬 #JobSearch

  5. I might have to start applying for architecture jobs. Seems like science doesn’t like me 😬 #JobSearch

  6. I might have to start applying for architecture jobs. Seems like science doesn’t like me 😬 #JobSearch

  7. A job advert is a wishlist, not a checklist. Reading it well saves you hours of applications that were never a fit. Try this when you open a new vacancy: 1. Separate must-haves from preferences. Words like "essential", "required", or "must have" usually mean screening criteria. Soft language ("ideally", "nice to have", "familiarity with") is often flexible. If you miss one hard requirement that is core to the day-to-day work, move on. If you miss a tool they've listed among five others, you may still be in the running. 2. Find the real job under the buzzwords. Strip the adjectives and ask: what would I actually spend Monday on? Delivering projects, supporting customers, writing code, managing people? If you can't answer that in one sentence, the brief is vague — treat that as a signal to dig in the interview, not a reason to invent a story in your CV. 3. Note what they repeat. Themes that show up twice (collaboration, delivery under pressure, stakeholder communication) are what they will score you on. Mirror those with evidence, not by pasting their phrases back. 4. Check the practical bits early. Location, hybrid expectations, salary band (or its absence), visa sponsorship, and closing date. A great-sounding role with a silent salary and "must be in office five days" may not match what you need — better to know before you invest an evening rewriting your CV. 5. Spot red flags without catastrophising. Endless "wear many hats", no mention of the team or manager, and a requirements list that needs three people's experience can mean a stretched role or a poorly written brief. Worth one clarifying question later; not always a hard no. You don't need to meet every line. You do need to know which lines matter. When you're scanning a job description, what do you look at first — and what makes you close the tab? #JobSearch#CareerAdvice#JobApplications#JobDescription#Careers

  8. A job advert is a wishlist, not a checklist. Reading it well saves you hours of applications that were never a fit. Try this when you open a new vacancy: 1. Separate must-haves from preferences. Words like "essential", "required", or "must have" usually mean screening criteria. Soft language ("ideally", "nice to have", "familiarity with") is often flexible. If you miss one hard requirement that is core to the day-to-day work, move on. If you miss a tool they've listed among five others, you may still be in the running. 2. Find the real job under the buzzwords. Strip the adjectives and ask: what would I actually spend Monday on? Delivering projects, supporting customers, writing code, managing people? If you can't answer that in one sentence, the brief is vague — treat that as a signal to dig in the interview, not a reason to invent a story in your CV. 3. Note what they repeat. Themes that show up twice (collaboration, delivery under pressure, stakeholder communication) are what they will score you on. Mirror those with evidence, not by pasting their phrases back. 4. Check the practical bits early. Location, hybrid expectations, salary band (or its absence), visa sponsorship, and closing date. A great-sounding role with a silent salary and "must be in office five days" may not match what you need — better to know before you invest an evening rewriting your CV. 5. Spot red flags without catastrophising. Endless "wear many hats", no mention of the team or manager, and a requirements list that needs three people's experience can mean a stretched role or a poorly written brief. Worth one clarifying question later; not always a hard no. You don't need to meet every line. You do need to know which lines matter. When you're scanning a job description, what do you look at first — and what makes you close the tab? #JobSearch#CareerAdvice#JobApplications#JobDescription#Careers