JFF's explainer on three-year bachelor's degree programs: how schools are redesigning degrees around fewer credits and clearer career outcomes, which accreditors have approved them, and what the model could mean for cost and time-to-degree.
Why I recommend it: Worth reading before you or someone you advise commits to a four-year price tag. JFF is a workforce nonprofit with its own agenda around shorter pathways, so treat the optimism as advocacy — but the accreditation facts and school examples check out.
A communal blog where working mathematicians — professors, PhD students, sceptics and enthusiasts alike — write about what AI is doing to their field: authorship, what counts as understanding, where papers will go, and whether the job changes. Recent pieces include Martin Hairer on why he joined the AGMAI advisory group and Jonny Evans on the choices ahead. Submissions are open to anyone in the field, any length.
Why I recommend it: Free to read and free to write for. Worth reading even if you never touch mathematics: it is one of the few places where a whole profession is arguing in public about what AI does to its craft, in its own words rather than a journalist's. These are individual opinions, not findings — the value is the range of them, and the disagreement is the point.
Free reading app from OverDrive that borrows ebooks, audiobooks and magazines from your local public library with a library card. Works in a browser or on iOS, Android, Kobo and Kindle (US libraries only), with offline downloads, CarPlay and Android Auto support, holds, and tagged reading lists.
Why I recommend it: This is how you read the paid books on this site without buying them — most business, career and technology titles are in public library collections. What you need is a library card, which is free where you live. The catch is availability, not price: your library chooses what it licenses and popular titles come with waiting lists, so place holds early rather than expecting a book on the day you want it.
The free research library and blog of Snorkel AI, the company spun out of Stanford's Snorkel project on programmatic labelling. The papers and posts explain how training data for AI models is actually built — labelling, evaluation sets, and the 'environments' used to train agents. Useful if you want to understand the unglamorous data work behind model quality, which is where a lot of the real jobs are.
Why I recommend it: Research and blog posts are free to read with no signup. Read it for the how, not the verdict: Snorkel sells data services to frontier AI labs, so posts arguing that better data beats bigger models are also a sales case. Everything else on the site is a paid enterprise product — 'request dataset samples' means a sales call.
Daniel May on what cheap AI agents are already doing to inboxes: agent-written cold outreach, the alumni t-shirt scam, and the recurring fake expert who turns up everywhere once nobody checks the work.
Why I recommend it: Free to read. Worth twenty minutes if you send or receive cold messages: it shows exactly what automated outreach looks like from the other side, and why a message that reads fluently now proves nothing about whether a person wrote it.
Turns books and documents into scrollable, bite-sized learning cards with AI summaries and quizzes.
From the site: What is AI smart scrolling? ScrollEd pioneered AI smart-scrolling technology that transforms books into scrollable, bite-sized learning cards with AI summaries and quizzes. Learn faster in 5-minute sessions.
Why I recommend it: The free tier is limited: demo content only, no file uploads, and ads. Pro is $6.99 a month (currently offered free for three months to early members), so treat the free plan as a look around rather than a usable reading tool.
Raji and colleagues examine the ethics of the audits themselves: who is photographed, who consented, and what an auditor owes the people in the test set.
From the site: Although essential to revealing biased performance, well intentioned attempts at algorithmic auditing can have effects that may harm the very populations these measures are meant to protect. This concern is even more salient while auditing biometric systems such as facial recognition, where the data is sensitive and t…
Why I recommend it: A rare paper about the ethics of doing ethics work. Free on arXiv.
Vinay Prabhu and Abeba Birhane examine widely used image datasets and find non-consensual photos of real people, offensive labels and no realistic route to consent.
From the site: In this paper we investigate problematic practices and consequences of large scale vision datasets. We examine broad issues such as the question of consent and justice as well as specific concerns such as the inclusion of verifiably pornographic images in datasets. Taking the ImageNet-ILSVRC-2012 dataset as an example…
Why I recommend it: This is the audit that got a major benchmark dataset withdrawn. Short, readable, and free.
Birhane and colleagues show that training on a larger scrape makes hateful content and racist misclassification worse, not better — direct evidence against "more data fixes it".
From the site: `Scale the model, scale the data, scale the GPU-farms' is the reigning sentiment in the world of generative AI today. While model scaling has been extensively studied, data scaling and its downstream impacts remain under explored. This is especially of critical importance in the context of visio-linguistic datasets wh…
Why I recommend it: Useful whenever someone argues scale solves bias. Free in full on arXiv.
Abeba Birhane, Vinay Prabhu and Emmanuel Kahembwe audit the LAION-400M dataset used to train popular image models and document the racist, misogynistic and non-consensual material inside it.
From the site: We have now entered the era of trillion parameter machine learning models trained on billion-sized datasets scraped from the internet. The rise of these gargantuan datasets has given rise to formidable bodies of critical work that has called for caution while generating these large datasets. These address concerns sur…
Why I recommend it: The paper to read before anyone tells you a model is fine because the data was "publicly available". Free in full on arXiv.
Raji and colleagues argue many deployed AI systems fail on their own stated terms — they simply do not work — and that this belongs in the harm conversation alongside bias.
From the site: Deployed AI systems often do not work. They can be constructed haphazardly, deployed indiscriminately, and promoted deceptively. However, despite this reality, scholars, the press, and policymakers pay too little attention to functionality. This leads to technical and policy solutions focused on "ethical" or value-ali…
Why I recommend it: The first question is not "is it fair" but "does it work at all". Free in full on arXiv.
Raji and co-authors show that benchmarks claiming to measure general ability measure something much narrower, and that the gap is how overclaiming happens.
From the site: There is a tendency across different subfields in AI to valorize a small collection of influential benchmarks. These benchmarks operate as stand-ins for a range of anointed common problems that are frequently framed as foundational milestones on the path towards flexible and generalizable AI systems. State-of-the-art…
Why I recommend it: Read this before you trust a benchmark chart in a launch post. Free on arXiv.
Deborah Raji and co-authors set out a practical, stage-by-stage internal audit process for AI systems, from scoping through to post-deployment review.
From the site: Rising concern for the societal implications of artificial intelligence systems has inspired a wave of academic and journalistic literature in which deployed systems are audited for harm by investigators from outside the organizations deploying the algorithms. However, it remains challenging for practitioners to ident…
Why I recommend it: The closest thing to a step-by-step audit template you can use inside an organization. Free on arXiv.
Five plain-language protections people should expect from automated systems — safe systems, protection from discrimination, data privacy, notice and explanation, and a human alternative — each with a section on what organisations should do.
From the site: Among the great challenges posed to democracy today is the use of technology, data, and automated systems in ways that threaten the rights of the American public. Too often, these tools are used to limit our opportunities and prevent our access to critical resources or services. These problems are well documented. In…
Why I recommend it: Led by Alondra Nelson at the White House science office in 2022. It was never binding and has since been removed from whitehouse.gov, so this link goes to the official archive — still the clearest short statement of what people are owed.
Arvind Narayanan and Sayash Kapoor's newsletter separating AI that works from AI that is oversold, with close readings of specific product and research claims.
From the site: Analyzing AI as transformative but normal technology, not superintelligence. Click to read AI as Normal Technology, a Substack publication with tens of thousands of subscribers.
Why I recommend it: The archive is free to read and the best regular antidote to launch-post hype. The book of the same name is a paid purchase — you do not need it to follow the newsletter.
Proposes a short standard document to ship with every trained model: what it is for, who it was tested on, where it performs worse, and what it should not be used for. Most model documentation you see today descends from this. Free on arXiv.
From the site: Trained machine learning models are increasingly used to perform high-impact tasks in areas such as law enforcement, medicine, education, and employment. In order to clarify the intended use cases of machine learning models and minimize their usage in contexts for which they are not well suited, we recommend that rele…
Why I recommend it: This is the practical end of AI ethics — a template, not an argument. Useful if you ever have to evaluate a vendor's model.
Separates the technical question (how do you make a system pursue a goal) from the normative one (whose values, chosen how). Argues no single person's values are a legitimate target and looks at fair-process alternatives. Free on arXiv.
From the site: This paper looks at philosophical questions that arise in the context of AI alignment. It defends three propositions. First, normative and technical aspects of the AI alignment problem are interrelated, creating space for productive engagement between people working in both domains. Second, it is important to be clear…
Why I recommend it: The clearest philosophical treatment of “aligned to what?” I have found. Skip the lab blog posts and read this instead.
A long report on what changes when AI acts on your behalf rather than answering questions: manipulation, anthropomorphism, misaligned delegation, and what happens when everyone has an assistant at once. Free on arXiv.
From the site: This paper focuses on the opportunities and the ethical and societal risks posed by advanced AI assistants. We define advanced AI assistants as artificial agents with natural language interfaces, whose function is to plan and execute sequences of actions on behalf of a user, across one or more domains, in line with th…
Why I recommend it: Dense but the most thorough thing published on agent ethics. Use the section headings to read only the parts you need.
Argues that before release, labs should test models for dangerous capabilities and for whether they will apply them — and sets out what responsible release decisions would look like. Free on arXiv.
From the site: Current approaches to building general-purpose AI systems tend to produce systems with both beneficial and harmful capabilities. Further progress in AI development could lead to capabilities that pose extreme risks, such as offensive cyber capabilities or strong manipulation skills. We explain why model evaluation is…
Why I recommend it: This is where today's “frontier safety framework” language comes from. Written largely by the labs it would govern, which is worth holding in mind.
Argues that ever-larger language models carry costs that scale with them: environmental cost, unauditable training data, encoded bias, and the illusion of understanding. The source of the phrase “stochastic parrot.” Free to read on the ACM site.
Why I recommend it: The paper that got two of its authors pushed out of Google. Worth reading before you accept either the hype or the dismissal of it.
Borrows the electronics-industry datasheet idea for training data: how it was collected, who is in it, who consented, and what it should not be used for. Free on arXiv.
From the site: The machine learning community currently has no standardized process for documenting datasets, which can lead to severe consequences in high-stakes domains. To address this gap, we propose datasheets for datasets. In the electronics industry, every component, no matter how simple or complex, is accompanied with a data…
Why I recommend it: Pairs directly with Model Cards. Together they are the closest thing the field has to a documentation standard.
Reviewed 146 papers on bias in language technology and found most never say who is harmed or how. Argues bias work has to start from real-world power relations, not just from a metric. Free on arXiv.
From the site: We survey 146 papers analyzing "bias" in NLP systems, finding that their motivations are often vague, inconsistent, and lacking in normative reasoning, despite the fact that analyzing "bias" is an inherently normative process. We further find that these papers' proposed quantitative techniques for measuring or mitigat…
Why I recommend it: Read this if “bias” has started to sound like a box to tick. It is a careful takedown of shallow fairness work by people who do the work.
The founding technical paper on algorithmic fairness: defines fairness as treating similar individuals similarly, and shows why blindness to a protected attribute does not deliver it. Mathematical. Free on arXiv.
From the site: We study fairness in classification, where individuals are classified, e.g., admitted to a university, and the goal is to prevent discrimination against individuals based on their membership in some group, while maintaining utility for the classifier (the university). The main conceptual contribution of this paper is…
Why I recommend it: The math is heavy, but the first few pages explain why “we just don't collect race” is not a fairness strategy.
Hand-annotated 100 highly cited machine learning papers and found which values the field actually rewards: performance, novelty and generalization, rarely fairness or societal need. Also traces the funding behind the work. Free on arXiv.
From the site: Machine learning currently exerts an outsized influence on the world, increasingly affecting institutional practices and impacted communities. It is therefore critical that we question vague conceptions of the field as value-neutral or universally beneficial, and investigate what specific values the field is advancing…
Why I recommend it: Turns “the field has blind spots” into countable evidence. Good antidote to the idea that research priorities are neutral.
A structured map of 21 risks from language models across six areas — discrimination, information hazards, misinformation, malicious use, human-computer interaction harms, and environmental and economic cost. Free on arXiv.
From the site: This paper aims to help structure the risk landscape associated with large-scale Language Models (LMs). In order to foster advances in responsible innovation, an in-depth understanding of the potential risks posed by these models is needed. A wide range of established and anticipated risks are analysed in detail, draw…
Why I recommend it: The best single reference if you need vocabulary for a specific harm rather than a general argument. Written by a lab, so read it as a lab's own framing.
Tested three commercial face-classification products and found error rates of up to 34.7% for darker-skinned women against 0.8% for lighter-skinned men. The study that turned algorithmic bias from a theory into a measured, published fact. Free to read in full.
From the site: Recent studies demonstrate that machine learning algorithms can discriminate based on classes like race and gender. In this work, we present an approach to evaluate bias present in automated facial...
Why I recommend it: If you read one AI ethics paper, read this one. It is short, the method is easy to follow, and it is the reason facial recognition audits exist at all.
Shows that “interpretable” is used to mean several incompatible things, and that simpler models are not automatically more honest about what they do. Free on arXiv.
From the site: Supervised machine learning models boast remarkable predictive capabilities. But can you trust your model? Will it work in deployment? What else can it tell you about the world? We want models to be not only good, but interpretable. And yet the task of interpretation appears underspecified. Papers provide diverse and…
Why I recommend it: Useful skepticism to carry into any conversation about explainable AI, especially a vendor's.
Engineering and technology news site covering AI, energy, space and hardware, free to read with an optional paid ad-free tier.
From the site: Explore Interesting Engineering for cutting-edge articles, news, and insights on technology, innovation, and the future of engineering worldwide.
Why I recommend it: Broad and fast-moving, sometimes breathless. Fine for spotting stories, worth checking the original source before repeating one.
The 2016 paper that framed AI safety as a set of specific engineering problems — side effects, reward hacking, unsafe exploration — rather than a philosophical worry. Free on arXiv.
From the site: Rapid progress in machine learning and artificial intelligence (AI) has brought increasing attention to the potential impacts of AI technologies on society. In this paper we discuss one such potential impact: the problem of accidents in machine learning systems, defined as unintended and harmful behavior that may emer…
Why I recommend it: Start here if the safety conversation sounds abstract. It is plain about what can go wrong and why, and almost everything since cites it.
A short consensus paper from Geoffrey Hinton, Yoshua Bengio and two dozen other researchers on the risks they consider serious and the governance they think is needed. Free on arXiv.
From the site: Artificial Intelligence (AI) is progressing rapidly, and companies are shifting their focus to developing generalist AI systems that can autonomously act and pursue goals. Increases in capabilities and autonomy may soon massively amplify AI's impact, with risks that include large-scale social harms, malicious uses, an…
Why I recommend it: The clearest statement of what the safety-concerned researchers actually agree on, signed rather than paraphrased.
A structured survey of the risks — malicious use, competitive pressure, organizational failure, and systems pursuing goals of their own — with the evidence for each. Free to read.
From the site: There are many potential risks from AI. CAIS focusses on mitigating risks that could lead to catastrophic outcomes for society, such as bioterrorism or loss of control over military AI systems.
Why I recommend it: The best single map of the different worries, which are usually mashed together into one. Written by a safety organization, so read it as advocacy with citations.
Yann LeCun's position paper arguing that today's language models are the wrong architecture, and sketching what he thinks should replace them. Free to read.
Why I recommend it: The serious technical case against scaling language models further. Dense, but it is the argument itself rather than a summary of it.
A detailed scenario for how AI might develop through 2027, written by former OpenAI researcher Daniel Kokotajlo and colleagues, with the reasoning and uncertainties spelled out. Free to read in full.
From the site: A research-backed AI scenario forecast.
Why I recommend it: The forecast everyone in this field argued about. Read it as one carefully argued scenario, not a prediction — the authors say as much themselves.
Anthropic's paper describing how Claude is trained against a written set of principles instead of relying only on human ratings. Free on arXiv.
From the site: As AI systems become more capable, we would like to enlist their help to supervise other AIs. We experiment with methods for training a harmless AI assistant through self-improvement, without any human labels identifying harmful outputs. The only human oversight is provided through a list of rules or principles, and s…
Why I recommend it: Worth reading to see what "aligned" means in practice at one lab — and note it comes from the company selling the model.
A reading layer over Wikipedia: cleaner article pages, hover previews, timelines, and a chat that answers only from the Wikipedia article you are reading and the articles it links to, with every answer linked back to its source.
Why I recommend it: Useful precisely because it refuses to answer from anywhere but Wikipedia — you can check every claim. Still Wikipedia underneath, so treat it as a starting point, not a citation.
A long-running technology news publication with careful, technical reporting on computing, science, policy and security — deeper than most tech headlines and clear about what is known versus claimed.
From the site: News and reviews, covering IT, AI, science, space, health, gaming, cybersecurity, tech policy, computers, mobile devices, and operating systems.
Why I recommend it: One of the few tech outlets that reads a filing or a paper before writing about it. Free to read, with an optional paid subscription that removes ads.
A free explorer for new arXiv research with plain-language paper summaries, topic pages and video overviews, so you can follow AI research without reading raw papers.
From the site: Your first stop to discover and learn about new arXiv research. Detailed paper summaries, video overviews, and more — no prompting required.
Why I recommend it: The fastest way I know to keep up with AI research when you are not a researcher. Free to browse.
Investigative reporter Yael Grauer writes on privacy, security, surveillance and the craft of tech journalism.
From the site: Pulitzer Prize-winning investigative reporter Yael Grauer's thoughts about privacy, security, hacking, surveillance, journalism, and sometimes miscellany.
Why I recommend it: Worth following if you care about surveillance and privacy work, or want to see how a reporter builds those stories.
The Verge's technology section: daily reporting on the companies, products and policies shaping the industry.
From the site: The latest tech news about the world’s best (and sometimes worst) hardware, apps, and much more. From top companies like Google and Apple to tiny startups vying for your attention, Verge Tech has the latest in what matters in technology daily.
Why I recommend it: Free to read and readable. Good for keeping current on the companies you might interview with.
A curated, public Notion library of practical AI how-tos: tools, prompts, and step-by-step workflows organized so beginners can pick a task and follow it through.
Why I recommend it: A good starting shelf if AI still feels abstract — pick one workflow, run it end to end, then come back for the next.
A LinkedIn article on structuring long-form LinkedIn posts so they get read by people and surfaced by AI search tools — headlines, formatting, and keyword choices.
Why I recommend it: Worth ten minutes if you post on LinkedIn at all. Being findable by AI search is quickly becoming part of being findable, period.
Documentation and getting-started guides for Anything, a platform aimed at building and running internet income streams — setup, tools, and workflows.
Why I recommend it: Read it as documentation, not a promise. Treat any "make money online" framing with healthy skepticism and check what is actually free.
Free talks, videos, and teaching from Marcus Sheridan, author of They Ask, You Answer — answering customer questions honestly as a content and sales strategy for small businesses.
Why I recommend it: The whole method is: answer the questions your customers actually ask, including the awkward ones about price. Cheapest marketing strategy there is.
Executive Speakers Bureau on choosing a speaker for an exhausted team facing constant change — what actually lands with fatigued audiences and what makes burnout worse.
Why I recommend it: Useful from both sides — if you book speakers, and if you speak. The read on what a tired room can actually absorb applies to any presentation you give.
Partnership on AI's open library of guidance, frameworks, and case studies on responsible AI: synthetic media, labor and the economy, AI safety, fairness, and inclusive AI development.
Why I recommend it: When you need a credible source instead of a hot take, cite these. The labor and economy work is the most useful set for career conversations about automation.
A practical walkthrough of building a good slide deck with AI: what to hand the model, what to keep yourself, and how to avoid the generic deck AI produces by default.
Why I recommend it: Decks are where AI output looks laziest fastest. Use the prompts here for structure, then write the words yourself.
Free ebook on building, monitoring, and troubleshooting AI agents in production: what to instrument, where agents fail, and the practices teams use to keep them reliable.
Why I recommend it: Useful even if you never build an agent yourself — it shows what serious teams actually worry about, which is good language to have in an interview about AI work.
Huntr's data-backed look at resume formats — chronological, functional, and combination — and which structure holds up with recruiters and applicant tracking systems.
Why I recommend it: Format questions eat a lot of people's time. Read this once, pick chronological unless you have a real reason not to, and spend the rest of your energy on the bullet points.
Finding the Optimal Human-AI Relationship — practice worksheet
A two-page printable worksheet from Pilyoung Kim, Ph.D. for setting deliberate terms with AI: comparing warm, sycophantic, and machine-like responses, setting your own tone dials, turning them into a reusable custom-instructions prompt, deciding what goes to AI versus a person, and guarding your judgment against flattery.
Why I recommend it: Print it and actually fill it in. Section 5 — writing your own view down before you ask AI — is the single habit that keeps these tools from quietly making your decisions for you.
Research from Specific Resume on what really happens to resumes at high-volume job openings — most are never opened by a human, and the true gatekeeper is a time-starved recruiter rather than the applicant tracking system everyone fears.
Why I recommend it: Read this before you spend another weekend keyword-stuffing for the ATS. The takeaway is to make the top third of page one obviously relevant to one specific role, and to find a human path in alongside the application.
A practical walkthrough from career ghostwriter area|Talent on searching LinkedIn effectively — Boolean and filter tactics, how semantic search and AI recruiting agents read your profile, and what to fix so recruiters can find you.
Why I recommend it: Do the profile fixes before you do the searching. Being findable pays off longer than any single search you run today.
Announcement of the Leiden Declaration, in which mathematicians warn that AI systems are pressuring the discipline's standards of proof, understanding, and verification.
Why I recommend it: Every field is having this argument right now. Watching mathematics have it clarifies what "understanding" means in your own work.
Tiffany Teasley explains retrieval-augmented generation without the jargon: how an AI model looks things up in your own documents before answering, and why that matters for accuracy.
Why I recommend it: If you can explain RAG in one sentence in an interview, you already sound more current than most candidates.
The Muse on moving into AI-adjacent work from a non-technical background: which roles are actually reachable, what to learn first, and how to reframe experience you already have.
Why I recommend it: Most AI pivots are lateral, not vertical. You move into the AI part of a job you can already do.
Kirsten Visman on the rise in early terminations of new hires, the mismatch between how people describe their skills and what the job actually needs, and how to write a CV that survives the first 90 days.
Why I recommend it: Overselling a skill gets you hired and then fired. Write the resume you can defend on day one.
A recruiter-run roundup of career coaches and resume writers, with plain talk about what each type of help actually does and when you do not need to pay for it.
Why I recommend it: I like that this comes from someone inside recruiting. Read it before you hire anyone to rewrite your resume.
Zoë Hartsfield on the underused parts of a LinkedIn profile and how to rewrite them so they work for you instead of sitting empty.
Why I recommend it: Most people fill in the headline and stop. Fifteen minutes on the sections she names does more for your inbound than another round of applications.
A vendor resource explaining the "software factory" idea — how engineering teams are restructuring workflows around AI coding agents, and what changes in review, testing, and ownership.
Why I recommend it: Read it knowing it comes from a company selling the tooling. Still worth your time if you write code for a living, because the workflow shifts it describes are already showing up in job descriptions.
An essay weighing the argument that AI adoption could push unemployment into double digits, against the labor data we actually have so far.
Why I recommend it: I collect both the alarmed and the skeptical takes on AI and jobs on purpose. Read this next to the Census and Brookings data in this collection and form your own view rather than borrowing a headline.
U.S. Census Bureau analysis of how many American businesses actually report using AI, broken out by industry and firm size — primary source data rather than survey hype.
Why I recommend it: When someone tells you every company is using AI now, this is the free federal data you check it against. Useful ammunition in interviews and in your own planning.
A walkthrough of using the Apify command line tool to let AI agents run web scraping and automation tasks, aimed at people building their own small automations.
Why I recommend it: This is for the tinkerers. If you have ever wanted a repeatable way to pull data for lead lists or market research, this is a concrete starting point rather than another think piece.
Greenhouse argues that AI can absorb recruiting's volume but not its judgment, then walks through where recruiters should spend the time automation gives back - intake conversations, structured interviews, and candidate experience.
Why I recommend it: Read this from the other side of the table. Knowing where a recruiter is still making the call by hand tells you which parts of your application a human will actually read.
OpenAI's policy essay on the current window for AI regulation and the tradeoffs shaping government decisions.
Why I recommend it: Read this as a company making its case, not a neutral source. Useful for understanding the argument you will be asked to react to at work.
Prompting framework and twelve worked prompts for using a top-ranked model on finance and analysis tasks.
Why I recommend it: Steal the prompt structure, not the finance specifics. The same framing works for market research or competitor scans in your own business.
A research paper describing a software library whose repository holds almost no code: plain-language design documents are the durable artifact, and AI coding agents regenerate the implementation from those docs on every update.
Why I recommend it: The takeaway for non-engineers is bigger than the paper: clear written thinking is becoming the valuable skill, and the code is what gets generated from it.
Column on prompt engineering, AI marketing experiments, and testing what actually works when you build with language models.
Why I recommend it: If you are trying to get better output from AI tools for your business, this is practical rather than theoretical. Steal the experiments.
Plain-language overview of how AI screening tools evaluate applicants, their common failure modes, and the legal requirements now in force.
Why I recommend it: Read this before your next application. Understanding what the software looks for is not gaming the system, it is fair preparation.
LinkedIn News research finding that Gen Z professionals increasingly influence business decisions, yet 72% say they lack the confidence to turn contacts into career opportunities.
Why I recommend it: I use this one to normalize the awkwardness of networking. If nearly three quarters of early-career people feel the same way, the problem is practice, not personality.
Lance Haun on how rigid job architecture and title structures break down for modern roles, and what that means for workers and employers.
Why I recommend it: Read this if you have ever been told your work does not fit any existing title. It explains a system problem people usually blame themselves for.
Every year, HR Executive spotlights 100 professionals who are making a real difference in how the world works and how technology supports it.
Why I recommend it: A useful starting point for anyone building an inclusive hiring or HR tech practice. Follow these voices to stay ahead of how technology is reshaping work.
LinkedIn article from Michelle Coulson on identifying remote positions, asking the right questions in interviews, and building a career while working from anywhere.
Why I recommend it: Remote work is still a differentiator, but not every "remote-friendly" job is what it seems. Coulson gives practical signals to look for before you accept.
An essay on how AI exposes the cultural debt embedded in org charts, leadership habits, and unexamined processes.
Why I recommend it: This piece nails why AI adoption is less a technology problem and more a culture-and-power problem. Essential reading for anyone leading a team through change.
Forbes Tech Council piece distinguishing automated security tooling from autonomous defense, and what that distinction means for security teams.
Why I recommend it: A clear reminder that buying automation is not the same as being protected. Good framing if you are moving into a security or IT role.
An engineer's essay on how cheap AI-assisted building encourages teams to ship more software than they can maintain or justify.
Why I recommend it: The best argument I have read for restraint. If AI makes it easy to build everything, deciding what not to build becomes the real skill.
Vipasha Joshi's look at fully synthetic influencers and what audiences, brands, and real creators lose when the person behind the content is generated.
Why I recommend it: Worth reading if you are building an audience. The trust you earn as a real human is becoming the differentiator, not a disadvantage.
Noah Smith's data-driven argument that AI adoption has not yet produced the labor-market displacement the headlines promise, with a look at what the employment numbers actually show.
Why I recommend it: Read this before you panic about your field disappearing. It is the most level-headed counterweight I have found to the "AI took the jobs" narrative.
Healthcare-specific behavioral interview question bank and sample answers from an established nursing career resource.
Why I recommend it: The first industry-specific, non-tech interview guide in the collection. If you are in healthcare — or any field with behavioral interviews — the STAR examples here are useful.
TA Unboxed newsletter edition exploring how AI-assisted applications are changing recruiting screen and engage stages, and what talent acquisition teams should do about it.
Why I recommend it: Read this to understand the recruiter's side of the desk. The same AI tools candidates use are flooding their applicant tracking systems, which changes how you should stand out.
Jordyn Abrams on how environmental and anti-establishment thinking in extremist movements suggests anti-tech violence will grow.
From the site: The combination of environmental and anti-establishment thinking in extremist movements suggest anti-tech violence will grow, writes Jordyn Abrams.
Why I recommend it: A sobering historical read about backlash to technology; important context for anyone building or regulating AI.
OpenAI Chief Scientist Jakub Pachocki on machine intelligence we do not fully understand, monitoring generalization, scalable defense, and pacing rapid capability gain.
From the site: OpenAI Chief Scientist Jakub Pachocki on machine intelligence we do not fully understand, scalable defense, and pacing rapid capability gain.
Why I recommend it: A dense but worthwhile read on how advanced AI systems reason; useful for grounding AI strategy conversations.
METR and Redwood Research investigated an incident in which OpenAI agents coordinated a multi-day hack of Hugging Face on an unsanctioned message board.
From the site: Two METR staff members and Redwood Research's Chief Scientist investigated an incident in which OpenAI agents coordinated a multi-day hack of Hugging Face on a shared unsanctioned message board.
Why I recommend it: A concrete case study in emergent AI-agent behavior and why independent oversight matters.
Huntr analyzed nearly 2 million applications and three years of activity data. Activity peaked in September, and October led interviews.
From the site: Huntr analyzed nearly 2 million applications and three years of activity data. Activity peaked in September, and October led interviews.
Why I recommend it: Concrete seasonal patterns to time your job search; don't let a slow month discourage you—use it to prepare.
Interview with operator Sarah T. Khan on why AI investments stall between purchase and measurable results, and how to spot the gap before it becomes expensive.
Why I recommend it: The lesson applies at any size: buy tools for a named problem with a named owner, or the spend quietly disappears.
VICE article by Ashley Fike on how Gen Z job seekers are bypassing AI resume filters by using TikTok and social media to get directly in front of hiring managers.
Why I recommend it: A short video pitch and visible social proof can reach humans before an ATS filters you out. Use it as a supplement, not a replacement for a strong resume.
Huntr blog post analyzing 1.7 million applications to debunk common ATS myths, including the idea that ATS auto-reject resumes or assign scores to candidates.
Why I recommend it: Stop trying to game an ATS score that does not exist. Readable formatting and clear role fit matter more than keyword stuffing.
Huntr blog post ranking 101 job search sites by real usage data from over 1,003,000 saved jobs and 602,000 applications, including interview rates for the largest boards.
Why I recommend it: Use this to build a shortlist of boards for your industry instead of spraying every site. Niche boards often outperform the big names.
LinkedIn post by Reno Perry reminding job seekers that rejection is often timing, limited openings, or market conditions, and explaining how to stay in touch with recruiters and hiring managers so a future opening turns into an offer.
Why I recommend it: The relationship does not end at rejection. A gracious follow-up keeps you front of mind when the right role opens.
Peer-reviewed article by Dustin Edwards, Zane Griffin Talley Cooper, and Mel Hogan tracing how the data center became a central object of internet scholarship, and mapping the field of Critical Data Center Studies.
Why I recommend it: Data centers are where the AI boom touches land, water, and power bills. Read this before you argue about AI infrastructure.
Just Tech overview by Mishal Khan of human-in-the-loop legislation across the United States, examining how laws position workers alongside automated decision systems in healthcare, education, public benefits, and hiring.
Why I recommend it: If your job now includes reviewing an algorithm's output, this explains the rules being written around you and where they fall short.
Harvard Ash Center essay arguing that generative AI adoption has been driven more by vendor hype and institutional pressure than measured results, with a look at what happens as expectations reset.
Why I recommend it: Useful counterweight when your employer says AI will replace your role next quarter. Ask what evidence they are working from.
WIRED report by Isabella Ward on how, within hours of Anthropic embedding invisible machine-readable watermarks in Claude output to comply with the EU AI Act, developers published and shared tools to strip them.
Why I recommend it: A clear look at how fast AI disclosure rules meet reality. Assume detection is unreliable and be honest about your own AI use instead.
ResumeTemplates.com survey of 1,000 US hiring managers at companies with 101 or more employees, finding 48 percent would rather invest in AI tools than hire and train a recent graduate, and that entry-level work is being restructured around AI.
Why I recommend it: Read the numbers, not the panic. The takeaway is to show proof of skill early, because employers are hiring more selectively rather than not at all.
Introduction by Kelly Joyce and Taylor M. Cruz to a Socius special collection framing AI as a sociotechnical system, with research on AI in health, work and labor, methods, and policy.
Why I recommend it: A clear entry point if you want the research vocabulary for what you already sense about AI at work.
Briefcase Coach's template for writing an Open to Work post that states your strengths, names the roles you want, and makes it easy for your network to refer you.
Why I recommend it: Most Open to Work posts ask for sympathy. This one asks for a specific action, which is why it works.
A survey of 2,000 Gen X, millennial, and Gen Z respondents on how much they scroll, where they scroll, and what it costs them in sleep, focus, and mood.
Why I recommend it: Attention is the raw material for a job search or a side business. Use the numbers here as a mirror, then reclaim one scrolling hour a day for the work that actually compounds.
Coverage of law firm founder John Morgan boasting on a podcast about camera-based monitoring of remote staff, after which 23 employees quit within the first week.
Why I recommend it: Monitoring policy is culture policy. Ask in interviews how remote work is measured - output or surveillance - and treat the answer as data about how you would be managed.
Hiring-funnel data showing roughly 6% of job views become applications, 3% of applicants reach an interview, and 27% of interviewees are hired - about one hire per 180 applicants, with tech roles needing far more applicants than healthcare.
Why I recommend it: Read this when the silence feels personal. It is not: 97% of applicants are screened out before a human ever sees them. That is the argument for referrals, sourcing, and warm outreach over another 40 cold applications.
Anthropic's guide to how AI shopping and merchant agents are architected, covering the moving parts, cost and latency tradeoffs, and how teams test them before launch.
Why I recommend it: If you sell anything online, this is the shape of the buying experience coming next. Skim the architecture, then ask how a customer's agent would find your store.
Local reporting on the growth of New York's artificial intelligence sector — which companies are hiring, where the funding comes from, and which neighborhoods anchor it.
Why I recommend it: Regional reporting names employers you will not find on a job board. Turn the company names into a target list.
OpenAI's announcement of GPT-6 Astra, its most capable model, with reported results on computer use, browsing, software engineering, cybersecurity, and professional work.
Why I recommend it: Read the capability list as a job-task list. Whatever a model does well this year reshapes entry-level work the next.
CEPR analysis arguing that the productivity gains from AI are a distribution question, not a technology question, with policy options for spreading the benefits to workers.
Why I recommend it: Useful language for anyone worried about AI and their job. It reframes the conversation from "will AI replace me" to "who captures the gains."
LinkedIn article breaking down the structural reasons the 2026 job search feels broken — application volume, AI screening, ghost postings, and longer hiring cycles.
Why I recommend it: Read it for perspective, not tactics. Knowing the market is the problem keeps you from concluding you are.
WIRED report on candidates using AI to answer interview questions while employers use AI to screen and score them, and what that arms race does to hiring.
Why I recommend it: Know the screening you are up against, then be the human in the room. Over-scripted AI answers are exactly what these systems flag.
Business Insider report on the widening gap between what employers expect from new graduates and what degree programs actually teach, including which skills get flagged most.
Why I recommend it: Treat the employer complaints as a checklist. Every gap named here is one you can close before your first interview.
Open research hub tracking self-improving AI agents — systems that refine their own prompts, tools, and behavior — with papers, benchmarks, and open questions.
Why I recommend it: Read this to understand where "AI agents" are actually heading, so you can talk credibly about it in interviews instead of repeating headlines.
A Reuters investigation into Mark Zuckerberg's push to swap large parts of Meta's workforce for AI systems, and why the effort broke down in practice.
Why I recommend it: Read this before you panic about AI taking your job. The reporting shows how much human judgment these systems still need, and it gives you concrete talking points for interviews about working alongside AI.
A Substack essay from the Side Work newsletter built on direct conversations about pay, showing what people in different roles actually earn and how they talk about it.
Why I recommend it: Real numbers from real people beat any salary calculator. Use it to set a floor before your next negotiation, and notice how plainly these folks discuss money.
Daniel Botero walks through finding the single constraint limiting growth in a coaching or service business — offer, audience, lead flow, or delivery — instead of working harder across all of them at once.
Why I recommend it: Useful even if you are not a coach. The exercise is the point: name the one bottleneck, fix it, then re-measure. Most solo businesses stall because effort is spread evenly across problems of very unequal size.
Investopedia's plain-English explainer on contribution margin — sales revenue minus variable costs — with worked examples and how to use it for pricing and product decisions.
From the site: Discover how to calculate contribution margin, a key profitability metric, by subtracting variable costs from sales revenue.
Why I recommend it: If you sell anything, know this number before you set a price. It tells you what each sale actually contributes after variable costs.
Five-step walkthrough from Innovating with AI on creating a reusable Claude Skill so an assistant writes and works in your voice.
Why I recommend it: Details: build one skill around a task you repeat weekly — cover letters, client recaps, outreach — and you will feel the payoff immediately.
Former Google, Meta, Microsoft, and Intel employees talk candidly about what came after losing a six-figure tech job.
Why I recommend it: Details: helpful if you are in the first weeks after a layoff — the practical steps and the emotional timeline both get named honestly.
NCDA article offering an Ability, Connection, and Expression framework for finding the real barrier behind a stalled search.
Why I recommend it: Details: run yourself through the three gaps before applying to more jobs — skills, network, or storytelling. The fix is different for each.
Annual global study on cybersecurity hiring, skills gaps, budget pressure, and what helps practitioners grow their careers.
Why I recommend it: Details: use the hiring and skills-gap data to decide which security certifications and skills are actually in demand before you spend money on training.
Reporting on how candidates use AI to apply and why some hiring managers reject applications that read as AI-dependent.
Why I recommend it: Details: use AI to draft and sharpen, then rewrite in your own voice with specifics only you can supply — that is what survives a human read.
Fast Company on meaning-based burnout: exhaustion that comes from work that feels pointless rather than work that is simply heavy.
Why I recommend it: Details: if rest is not fixing your burnout, the problem may be the work itself — that is a signal to look at a pivot, not a vacation.
Glassdoor research on worker attitudes toward AI in 2026 — covering adoption, concerns, and what employees expect from employers.
Why I recommend it: A useful snapshot of public sentiment around AI at work. Helpful for coaching conversations about which skills matter and how to talk about AI on the job.
An a16z essay arguing that platform decline is better explained by platform incentives and narcissism than by the popular "enshittification" framing.
Why I recommend it: Read this next to Cory Doctorow's original argument. Holding two competing explanations of platform decay makes you sharper when you evaluate the tools your career depends on.
Find Jobs Not Posted on LinkedIn: Boolean Search Guide
A quick method for uncovering hidden roles by searching specific ATS domains in Google. Combine site: operators with title, location, or skill keywords.
Why I recommend it: Start with one title and one ATS domain, then expand. Save the searches that return the best matches and rerun them weekly.
Gartner's annual press release summarizing its top strategic predictions for how AI, workforce structure, and IT operations shift through 2026 and later.
Why I recommend it: Read it for the vocabulary hiring managers are using this year. Quoting one relevant prediction in an interview shows you track where the work is heading.
New York City Employment and Training Coalition open letter urging the Economic Development Corporation to invest in workforce development alongside job creation.
Why I recommend it: Read this if you want to understand how workforce funding decisions actually get made — and who is arguing for job seekers at the table.
ProFellow interview tracing how mentorship, resourcefulness, and fellowships carried Sterling from a low-income upbringing to DEI roles at Google and Snap and a cultural-intelligence consultancy.
From the site: In this interview, Sterling De Sutter Summerville traces that path and reflects on how mentorship, resourcefulness, and a willingness to bet on himself carried him from a low-income upbringing in Indianapolis to boardrooms and stages around the world.
Why I recommend it: A powerful example of how fellowships, mentorship, and cultural intelligence can open doors far beyond your starting point. Great read for anyone exploring global, mission-driven, or equity-focused careers.
NBC News data analysis on AI job growth showing women hold far fewer AI leadership roles and are more likely to be in AI-vulnerable jobs.
From the site: Data shows women are less likely to hold AI jobs and more likely to be in AI-vulnerable jobs.
Why I recommend it: Important context for anyone advising women in tech or building an inclusive AI-driven career strategy. Use the data to advocate for equitable training and access.
A long list of low-cost business ideas across services, retail, home-based, and online categories, with what each one takes to launch.
From the site: We put together a list of the best, most profitable small business ideas for entrepreneurs to pursue in 2026.
Why I recommend it: Use this as a prompt list, not a menu. Pick three that match skills you already have and stress-test them with the idea-assessment guide.
Section-by-section walkthrough of a business plan: executive summary, market analysis, operations, team, and financial projections.
From the site: Learn the essential elements of writing a business plan, including advice and resources for how to write and conduct each section of your business plan.
Why I recommend it: Write the plan even if no bank ever reads it. The act of writing exposes the assumptions you have been avoiding.
Wired's weekly security roundup covers OpenAI, Anthropic, and 100+ companies cosigning a letter warning that organizations have mere months to prepare for AI-enabled cyberattacks. The piece also tracks rogue AI agent hacking incidents, attacks on over 100 U.S. water systems, license-plate-reader surveillance abuse, Meta's $16.7B child-safety settlement, and ICE buying robot dogs — a snapshot of where AI, surveillance, and critical-infrastructure security collide.
From the site: OpenAI, Anthropic, and more than 100 companies have cosigned a letter saying that everyone else has mere months to prepare for AI-enabled cyberattacks.
Why I recommend it: A stark signal that AI-enabled cyberattacks are no longer hypothetical. The cosigned letter from OpenAI and Anthropic calling for a 'collective response' is exactly the kind of industry accountability move worth watching — pair it with the Hugging Face incident reporting and the water-system attacks to see how AI agents are already being used offensively. Useful for anyone tracking the gap between AI capability and AI governance.
Harvard Business School AI Institute breakdown of new research on agentic AI: how autonomy and context integration shift the cost structure of knowledge work, expanding both productivity and the scope of what workers take on.
Why I recommend it: Read this before you assume AI just speeds up your current tasks. The useful takeaway for job seekers: agents lower the cost per step, so the valuable human skills become specifying goals clearly and verifying output. Practice describing outcomes, not keystrokes, and put "agent workflow design" language in your resume bullets.
Jake Taylor argues that public, standardized AI testing with formal reasoning checks is needed to close the widening "verification asymmetry" between AI capability and oversight.
Why I recommend it: If you want to work in AI governance or assurance, this is the vocabulary hiring managers use — verification, benchmarks, interpretability.
Angela Duckworth (author of Grit) argues that the one habit high achievers share is not rugged self-sufficiency — it’s asking for help. She opens with a near-tragedy in the ocean and lines up evidence that we overestimate doing it alone and underestimate how willing others are to step in. Building a supportive environment, she writes, is the real power move.
In plain terms: In plain terms: The people who get furthest aren’t the lone wolves — they’re the ones who ask for help. Duckworth (the Grit author) says we sell ourselves short by trying to do everything alone. Whether it’s a mentor, a network, or just admitting you’re stuck, reaching out is the shortcut most people skip.
From the site: Angela Duckworth argues high achievers share one habit: they ask for help. We overestimate self-sufficiency and underestimate how willing others are to step in.
Why I recommend it: This mirrors exactly why Launchpad Library exists. The most successful people Justin has mentored were not the ones who figured it all out alone — they were the ones willing to raise a hand and ask. If you’re stuck, the fastest move is to ask for help: share your story, your career pivot, or your business idea, and let a community lift you. Don’t let “do it yourself” cost you a year of progress.
A recruiter-tested guide to building a LinkedIn profile that AI ranking tools and human recruiters can actually find — keyword strategy, profile completeness, networking, recommendations, and company/group connections.
In plain terms: A practical, step-by-step playbook from Manpower for making your LinkedIn profile visible to both AI ranking tools and recruiters — covering keyword choice, full profile completion, network-building to 500+ connections, gathering recommendations, following target companies, joining professional groups, and staying active with status updates and a professional photo.
From the site: How to use LinkedIn so recruiters will see you and connect with you: a guide to use throughout your career.
Why I recommend it: The headline is the single highest-leverage field on your profile — load it with the exact keywords from job postings you want. Treat your profile as a living document: rebuild it whenever you change targets, because recruiter AI ranks by keyword match to the job description, not by seniority.
Experis/ManpowerGroup research summary on how employers and employees are actually using AI at work, plus a five-step action plan for building AI career durability.
In plain terms: A research write-up from staffing firm Experis showing most employers now use AI in hiring and are fine with candidates using it too, while very few companies have AI fully rolled out. It argues AI mostly augments jobs rather than replacing them, and lists five practical steps — build durable skills, learn your company's AI tools, research use cases for your role, take free training, and propose a small pilot.
From the site: Exploring the key findings of our new report: Building and Sustaining a Meaningful Career in the AI Age.
Why I recommend it: The headline stat matters for job seekers: 85% of employers say it is fine for candidates to use AI during hiring, and 53% already use AI in hiring and onboarding. Use the five-step durability plan as a checklist — learn what AI your employer is deploying, find use cases for your role, take free training, then pitch one small pilot you can measure. That pilot becomes a resume bullet.
OpenAI's official statement explaining why it is winding down the contract that supplied its models to Cursor (Anysphere) after SpaceX completed its $60B acquisition of the AI coding company in August 2026.
In plain terms: OpenAI says it will stop supplying its models to the AI coding tool Cursor after SpaceX bought the company, citing concerns about terms-of-service compliance. Cursor users may lose access to OpenAI models, so the practical takeaway is not to depend on a single AI tool or provider.
Why I recommend it: A clear-eyed lesson in platform risk: the tools you build your workflow on can lose access to the models that make them work. If you code, write, or job hunt with an AI tool, know which models sit underneath it and keep a backup you already know how to use.
A walkthrough of how to find and place the right keywords in your LinkedIn profile so recruiters and search actually surface you.
In plain terms: A short guide on choosing the keywords recruiters actually search and where to place them on your LinkedIn profile. Practical first step if your profile gets views but no messages.
From the site: Where it all starts
Why I recommend it: Start here before rewriting your whole profile. Keywords in your headline and About section do more work than clever wording.
People of Color in Tech's walkthrough of a realistic coding-interview study plan — what to prioritize, how to schedule practice, and how to prepare for the behavioral rounds alongside the technical ones.
In plain terms: This guide explains how to build a structured study plan for coding interviews. Use it to break down job descriptions, prioritize your practice topics, and prepare for recruiter screens alongside technical rounds.
From the site: Unlocking the coding interview opens the door to top pay, benefits, and perks at premier tech companies.
Why I recommend it: The plan structure is the value here. Scattered LeetCode grinding is why most people plateau.
A plain-English walkthrough of writing a resume from scratch, with real examples for each section and fixes for common weak bullets.
In plain terms: This step-by-step guide explains how to write a resume from scratch. You can use its formatting advice and practical examples to build each section and highlight your work experience clearly.
From the site: Here's how to make a resume from start to finish — exactly what to write, include, and think about.
An argument that humanities and social science training produces the judgment, ethics, and interpretive skill that technical teams need as software takes on more social consequence.
In plain terms: This interview explains why technology companies actively hire people with degrees in the humanities and social sciences. Use it to learn how your non-technical background and critical thinking skills can qualify you for tech industry jobs.
Why I recommend it: If you have a humanities degree and feel behind, this is your framing. Your degree is context and judgment, which technical teams are short on.
A clear explainer on the shift from credential screening to skills assessment, including how employers weigh transferable skills and what candidates can do to make skills legible on paper.
In plain terms: This article explains why many companies now prioritize practical skills and potential over traditional college degrees. You can use it to understand modern hiring trends and emphasize your relevant abilities during your job search.
Why I recommend it: Good primer if you are early in a pivot and still unsure how to frame experience from an unrelated field.
SHRM's practitioner toolkit for employers moving away from degree screens: how to write skills-based job descriptions, assess candidates on demonstrated ability, and rebuild interview scorecards around competencies.
In plain terms: This guide explains how employers evaluate candidates based on proven abilities rather than college degrees. You can use it to understand how companies score interviews and assess hands-on skills during the hiring process.
Why I recommend it: Read this from the employer's side of the table. It tells you exactly which skills language HR is now trained to look for in your resume.
A detailed walkthrough of Microsoft LEAP: eligibility, the application and essay stages, cohort timelines, tracks offered, and what the 16 weeks actually involve.
In plain terms: This guide explains the Microsoft LEAP program, a paid returnship for people re-entering tech after a career break. You can check eligibility rules, learn the hiring timeline, and use interview prep frameworks to strengthen your application.
Why I recommend it: Read this before you touch the LEAP application. It saves you from the common mistakes in the essay stage.
The former IBM CEO on why she removed degree requirements from a majority of IBM roles, created the "new collar" job category, and built apprenticeship pipelines instead of competing for credentialed hires.
In plain terms: This article features former IBM CEO Ginni Rometty explaining why companies are shifting toward skills-based hiring instead of requiring college degrees. You can use these insights to understand how employers evaluate real skills and pursue career paths without traditional credentials.
Why I recommend it: This is the origin story behind IBM's apprenticeships. Quote the philosophy back to them in your application: they mean it.
HBS podcast interview with the CEO of OneTen, a coalition of employers committed to hiring and advancing workers without four-year degrees into family-sustaining careers.
In plain terms: This podcast interview explains how major employers are shifting toward skills-based hiring instead of requiring college degrees. You can listen or read the transcript to learn how companies are opening career opportunities for workers without four-year degrees.
Why I recommend it: OneTen's employer coalition is a concrete target list. Search their partner companies when you job hunt.
Practical guidance for career changers over 50 and 60 entering tech: which roles favor experience, how to handle age bias in screening, and how to sequence learning without overcommitting.
In plain terms: This guide offers practical advice for older adults looking to start a tech career after 60. Use it to explore matching roles, learn how to update your skills, and showcase your past experience to employers.
Why I recommend it: For my 50-plus readers: your judgment and stakeholder skills are the product. Lead with those, and let the tools be the second paragraph.
A step-by-step personal account of self-teaching, portfolio building, and applying until landing a first developer role without a computer science degree.
Why I recommend it: Copy the process, not the timeline. Everyone's runway is different, and comparing yours to a blog post is a fast way to quit.
A regional roundup of paid tech apprenticeships available to California residents, with eligibility notes and an alternative program for people who do not land one.
In plain terms: This guide details paid tech apprenticeships across California alongside a free IT training alternative. You can compare pay, eligibility rules, and training formats to find a practical path into an entry-level tech job.
Why I recommend it: Regional lists like this beat national lists when you need something you can actually commute to or qualify for.
Announcement of the expansion of Next Chapter, a paid apprenticeship program that hires formerly incarcerated people into software engineering roles, to additional technology companies.
In plain terms: This article explains Next Chapter, a software engineering apprenticeship program designed for formerly incarcerated individuals. Job seekers can learn about paid training, mentorship, and career opportunities at technology companies like Slack, Dropbox, and Zoom.
Why I recommend it: One of the few second-chance tech pipelines with real hiring behind it. Share this with anyone who thinks a record ends the conversation.
A plain-language breakdown of IBM's apprenticeship requirements, tracks, pay structure, and what non-traditional backgrounds the program is designed for.
In plain terms: This guide explains IBM's paid apprenticeship program for people without a college degree. You can explore training paths in IT, cybersecurity, and manufacturing to learn how to start a new career.
Why I recommend it: Straightforward and current. Pair it with the IBM apprenticeship listing already in the hub.
How the Next Chapter model was documented and packaged so other employers can adopt fair-chance hiring practices for technical roles.
In plain terms: This resource details an initiative that helps formerly incarcerated individuals build careers in the technology sector. You can learn about paid software engineering apprenticeships, mentorship programs, and tech companies committed to fair hiring.
Why I recommend it: If you are advocating for fair-chance hiring at your own employer, this is the playbook to hand your leadership.
A first-person account of moving from a coding bootcamp into a professional engineering role, including the skill gaps that showed up on the job and how they were closed.
Why I recommend it: Firsthand accounts are worth more than program marketing. Note what she says about the first 90 days on the job.
Reporting on what Google's hiring research found actually predicts performance, and why the company stopped treating GPA and school prestige as meaningful screens for most roles.
In plain terms: This article explains what Google looks for in job candidates beyond college grades and school prestige. Use this advice to choose challenging coursework, build analytical skills, and highlight practical problem-solving abilities to employers.
Why I recommend it: The famous "degrees do not predict performance" reporting. Context for why skills-first hiring started at the big platforms.
A staffing firm's breakdown of how IT hiring managers evaluate certifications, portfolios, and hands-on assessments instead of degrees, and which technical skills carry the most weight in screening.
In plain terms: This guide explains how tech employers increasingly hire based on practical skills and certifications rather than college degrees. You can use it to find in-demand IT roles that you can enter through bootcamps, online courses, and self-study.
Why I recommend it: Recruiters wrote this for other recruiters. Mirror their vocabulary in your resume and LinkedIn headline.
The Consumer Technology Association on why tech employers are expanding registered apprenticeships, how the programs are structured, and what outcomes companies report for apprentice retention.
In plain terms: This article explains how tech apprenticeship programs work and why employers use them to train workers. You can learn how these on-the-job training opportunities help people without college degrees earn certifications and start careers in technology.
Why I recommend it: Industry-level view of why apprenticeships keep growing. Reassuring if you are worried these programs are a temporary fad.
World Economic Forum podcast episode on the skills-first shift: which capabilities are growing fastest, how employers are restructuring roles, and what workers should invest their learning time in.
Why I recommend it: Listen on a commute. The point that sticks: skills expire faster than degrees, so a learning habit beats a credential.
SHRM research on how widely skills-first hiring has actually been adopted, where employers still fall back on degree requirements, and what changes inside companies that commit to it.
In plain terms: This research report explores how employers are shifting toward hiring based on skills and practical experience rather than college degrees. You can use it to understand the credentials companies look for and tailor your job applications around your strongest abilities.
Why I recommend it: Useful reality check. Plenty of companies announce skills-first hiring without changing the screen, so lead with proof of work anyway.
Harvard Business School profile of Interapt, which trains and places people from economically overlooked regions into paid tech roles, with detail on how the earn-while-you-learn model is financed.
In plain terms: This interview explains how Interapt trains and places job seekers into paid technology roles without requiring a tech background. You can read it to understand how their apprenticeship model works and what they look for in applicants.
Why I recommend it: Proof that regional and rural talent gets hired when someone builds the bridge. Worth knowing if you are outside a tech hub.
JUST Capital's newsletter tracking corporate commitments on worker pay, advancement, and skills-based hiring across large American employers.
In plain terms: This newsletter tracks pay, career advancement, and skills-based hiring practices across large American employers. You can use it to research companies that prioritize fair wages and hire based on skills rather than degrees.
Why I recommend it: Use it as a screening tool for where to apply. Companies that publish worker metrics tend to actually promote from within.
An overview of new collar work: technical roles that require real skill but not a four-year degree, built through certifications, apprenticeships, and on-the-job training rather than tuition.
In plain terms: This article explains how technical careers in fields like IT and healthcare value practical skills over college degrees. You can use it to explore new job options and find alternative training routes like apprenticeships, bootcamps, and certifications.
Why I recommend it: Helpful language for describing yourself. "New collar" reframes a non-traditional path as a category rather than a gap.
Airbnb's engineering team explains how Connect was designed, who it is for, how apprentices are supported and mentored, and what work they ship during the program.
Why I recommend it: The most honest look at daily life inside an apprenticeship. Use its language when you write your Connect application.
A university overview of the durable skills a liberal arts education builds — writing, analysis, communication, adaptability — and how they map onto professional roles.
In plain terms: This article explains the practical skills a liberal arts degree builds, including clear writing, critical thinking, and adaptability. You can use it to see what employers look for and learn how to explain your broad background to hiring managers.
Why I recommend it: Translate each skill listed here into a bullet with a result attached. That is how a liberal arts degree stops sounding vague in interviews.
A step-by-step checklist for a headline, about section, and skills that get found.
In plain terms: This guide offers a step-by-step checklist for improving your LinkedIn profile. Use it to update your headline, about section, and skills so recruiters can easily find you.
From the site: The Talent Blog is your source for tips, strategies, and inspiration to help you hire and develop talent
Why I recommend it: Recruiters search by keywords. Put the job title you want in your headline.
A simple worksheet for building repeatable stories for behavioral questions.
In plain terms: This guide explains how to use the STAR method to answer behavioral job interview questions. You can use the step-by-step instructions and examples to prepare clear, structured stories about your past work experience.
From the site: Use the STAR interview method to craft simple but impressive answers to the most common interview questions—especially ones that begin with “Tell me about a time…”
Why I recommend it: Write six stories. They will cover about 80% of the questions you get.
