home.social

#jobsearch β€” Public Fediverse posts

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

  1. Most CVs describe the job. The stronger ones describe what you did in it.


    "Responsible for managing the team inbox" tells a recruiter what was in your job description. "Cleared a backlog of customer queries and set up shared templates so most replies went out the same day" tells them what changed because you were there.


    A few ways to rework your bullet points:


    β€’ Start with a clear verb: led, built, cut, fixed, launched, trained. Use "responsible for" and "helped with" sparingly.

    β€’ Say what changed. Faster, cheaper, fewer errors, more customers, or a process that didn't exist before.

    β€’ Use numbers when you genuinely have them, and never invent them. Team size, budget, volume and turnaround time all count. If you don't have a figure, a plain before-and-after works too.

    β€’ Keep each bullet to a line or two. If one needs a paragraph, it's probably two achievements.

    β€’ Lead each role with the bullets most relevant to the job you're applying for.


    Not every task has a dramatic result, and that's fine. The aim is to show how you work, not to make every line sound like a headline.


    Which part of your experience do you find hardest to put into words on a CV?


    #CVTips#JobSearch#CareerAdvice#Resume

  2. Most CVs describe the job. The stronger ones describe what you did in it.


    "Responsible for managing the team inbox" tells a recruiter what was in your job description. "Cleared a backlog of customer queries and set up shared templates so most replies went out the same day" tells them what changed because you were there.


    A few ways to rework your bullet points:


    β€’ Start with a clear verb: led, built, cut, fixed, launched, trained. Use "responsible for" and "helped with" sparingly.

    β€’ Say what changed. Faster, cheaper, fewer errors, more customers, or a process that didn't exist before.

    β€’ Use numbers when you genuinely have them, and never invent them. Team size, budget, volume and turnaround time all count. If you don't have a figure, a plain before-and-after works too.

    β€’ Keep each bullet to a line or two. If one needs a paragraph, it's probably two achievements.

    β€’ Lead each role with the bullets most relevant to the job you're applying for.


    Not every task has a dramatic result, and that's fine. The aim is to show how you work, not to make every line sound like a headline.


    Which part of your experience do you find hardest to put into words on a CV?


    #CVTips#JobSearch#CareerAdvice#Resume

  3. "What are your salary expectations?" often comes up on the first recruiter call, before you know much about the role. A few ways to handle it without boxing yourself in: β€’ Do your homework first. Look at advertised ranges for similar roles in your area and sector, and ask recruiters or peers what's typical. You want a realistic range, not a guess. β€’ Ask before you answer. "Is there a budgeted range for this role?" is a fair question, and plenty of employers will tell you. β€’ Give a range you'd be genuinely happy at the bottom of. Conversations tend to settle towards the lower number, so if that figure would disappoint you, it's the wrong range. β€’ Think about the whole package. Bonus, pension contributions, holiday, flexibility and training budget can change the picture a lot. β€’ Leave room to revisit. "Based on what I know so far, I'm looking at roughly X–Y, and I'm happy to discuss once I understand the role better" is honest and keeps things open. Salary is a normal business conversation, not a test of how grateful you are for the interview. How do you usually answer the salary expectations question, or is there a part of it you're unsure about? #SalaryNegotiation#JobSearch#CareerAdvice#Careers

  4. Monzo is hiring Credit Model Validation Manager (Machine Learning & NPV Models)

    πŸ”§ #golang #python #aws #gcp #sql #machinelearning
    🌎 Remote; Cardiff, United Kingdom; London, United Kingdom; United Kingdom
    ⏰ Full-time
    🏒 Monzo

    Job details jobsfordevelopers.com/jobs/cre
    #jobalert #jobsearch #hiring

  5. 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

  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 cover letter only helps when it says something your CV can't. Skip it when the application form already asks the same questions, or when the employer clearly says "CV only". Write one when they ask for it, when you're changing field or seniority, or when there's a specific gap you need to explain in one place. If you do write one, keep it short β€” half a page is usually enough β€” and make it about them, not a biography of you: 1. Open with the role and one clear reason you're a fit (a requirement you meet well, or a problem in the brief you can help with). Avoid "I am writing to apply…" 2. Pick two or three proofs from your experience that map to what the job actually needs. Name the outcome, not just the task. 3. Close with availability and a simple next step. No pleading, no "I'd be grateful for the opportunity to discuss…" filler. 4. Match their language lightly. If the advert stresses collaboration or delivery under pressure, echo that with evidence β€” don't paste the whole JD back at them. 5. Proof once out loud. Awkward phrases and typos stand out more in a short letter than in a long CV. A good cover letter is a bridge, not a summary. If it only restates your CV in paragraph form, you're better off without it. When do you bother writing a cover letter β€” and when do you skip it? #JobSearch#CareerAdvice#CoverLetter#CVTips#JobApplications

Share on Mastodon

Enter the server where you have an account.