Day 1 of 30 on building a career that matches what you care about.
Find out who they are this week. Follow them. Read what they have written or built. Then, after a few weeks or months of being genuinely connected to their work, send a short connection request or leave a comment or a question.
That is the move. The rest of this post is why it beats the thing most people do instead, and how to actually run it.
A cover letter now takes about thirty seconds to produce. So hiring managers in the impact sector are opening files that read almost identically. Same structure. Same enthusiasm. Same line about being passionate about systemic change.
AI slop, sent in good faith. Most of the people sending it are serious about the work and have no idea their application looks like every other one in the stack.
Everything in a standard application has been mass-produced, and the people reading them know it. That is the part applicants underestimate. The reader is not fooled. They are just tired.
A question that proves you read someone's work cannot be mass-produced. Neither can six months of following what a team actually ships. Those are the two things left that still carry a signal.
Most career searches start with a title. Program Manager. Policy Analyst. Director of Partnerships. That search returns thousands of listings and no way to choose between them.
Start with the problem instead. Clean water in informal settlements. Refugee education. AI governance. Supply chain accountability. Whatever still holds your attention when you are tired at the end of a day.
The problem narrows the field faster than any title filter. It also gives you something real to say when you eventually write to someone, because you are not asking about a role, you are asking about work you have been paying attention to.
Five is enough. More than five and you will not follow any of them closely enough for it to matter.
The job board is a better directory than most people treat it as. Scroll the PCDN.Global job board by issue rather than by application and you will see which organizations are hiring on your problem right now, which means which organizations have budget and urgency on it. The listings usually name the team and sometimes the person the role reports to. That is your starting list.
From there: read what those people have published. Look at what their organization shipped in the last year, not what its about page claims. Find the talks, the papers, the annual reports, the posts where they disagree with someone in their own field. Disagreements are where you learn what a person actually thinks.
This is slow. It is supposed to be. The slowness is the whole point.
Not immediately. Following someone for a week and then writing to them produces the same email everyone else sends.
After a few weeks or months of genuinely paying attention, you will have a specific question. Something only that person could answer, because it comes from something they wrote or built that you actually read. That question is the message.
Keep it short. Name the thing you read. Ask the one question. Leave it there.
Two things not to send. Do not ask to pick their brain, which asks for an unbounded amount of someone's time and signals that you have no specific question. Do not ask if they are hiring, which turns a conversation into a transaction before it starts.
Most will not reply. That is the normal outcome and it is not a referendum on you or on the question.
One or two will. In coaching more than 200 people through career transitions across more than 20 countries, the conversations that changed things almost always came from that one or two, not from the portal. A reply from someone who does the work gets you context no listing contains: what the role is really about, what the team is struggling with, who else to talk to, and often a heads-up weeks before a job is posted.
Compare that to the application. Faster to send, worse odds, and no information comes back either way.
I use AI constantly for this. It is good at the research layer. Finding who works on a problem, pulling together what an organization published last year, summarizing a long report so you know whether to read it properly, tightening a message before you send it.
The free PCDN AI for Impact Career Platform does some of this, including an AI career coach and salary benchmarks, with no signup.
What AI cannot do is care about the problem for you. It will write you a confident paragraph about refugee education whether or not you have thought about refugee education for five minutes. The person reading can tell the difference, which is exactly why the mass-produced application stopped working.
One of these every day for a month. Some will be blog posts like this one. Some will be videos. Some will be a single image with one idea on it. The format and the design will vary, because a career is not one kind of problem.
I co-draft them with Boardy, an AI connector, and edit every one myself. It seemed honest to say that in a series partly about not sounding like a machine. Boardy works simply: you tell it what you are working on, it figures out who you should meet, and it makes the introduction. It is free to use. I interviewed Boardy on the Social Change Career Podcast in early 2025.
Let us know your career questions here. I will answer as many as I can. The ones that would help the most people become a Craig & Careers video, a PCDN blog post, a LinkedIn post, or something similar.
