How to know if that job will crush your soul 🔗 **Source:** [How to know if that job will crush your soul](https://www.anildash.com/2026/01/12/will-that-job-crush-your-soul/) > [!note]+ Document Notes > tags: [career, work, tech] > author: Anil Dash > source: anildash.com > reference: [https://www.anildash.com/2026/01/12/will-that-job-crush-your-soul/] > date created: 2026-01-14 10:30 > > # 🏷️ Title: How to know if that job will crush your soul > <!-- deep-read:sections start --> ## 🧭 Table of Contents - [📝 Summary](#-summary) - [📖 Main Content](#-main-content) - [🗒️ Notes](#️-notes) - [📚 References](#-references) - [🗣️ Paraphrase](#️-paraphrase) - [📰 Newsletter](#-newsletter) - [✅ Action Items](#-action-items) - [🧪 Hypotheses](#-hypotheses) - [📊 Methodology](#-methodology) - [❓ Questions](#-questions) - [🔮 Future Research](#-future-research) - [💡 Implications](#-implications) - [🧠 Learning Styles Assessment](#-learning-styles-assessment) - [📊 Accessibility Assessment](#-accessibility-assessment) - [🌍 DEIB Assessment](#-deib-assessment) - [✅ Logical Validity](#-logical-validity) - [🛡️ DARVO Analysis](#-darvo-analysis) - [🎯 Conclusion](#-conclusion) ### 🔗 References - Anil Dash — “How to know if that job will crush your soul” (https://www.anildash.com/2026/01/12/will-that-job-crush-your-soul/) ## 📝 Summary - What happened. - Dash offers seven questions to evaluate whether a prospective job will harm your well‑being or align with your values. - Why it matters. - Many workers feel exploited or stuck; a simple evaluative framework can prevent “soul‑crushing” roles. - Key stakeholders. - Tech and knowledge workers, hiring managers, leaders shaping org culture. - Risks and tradeoffs. - In a tough market, holding high standards may reduce immediate options but improves long‑term outcomes. - Bottom line. - Systematically assess impact, money, assumptions, culture, learning, and compensation to choose healthier jobs. ## 📖 Main Content - Dash frames the piece as timeless advice for evaluating roles, especially in tech. He introduces seven questions for judging whether a job will “crush your soul.” - 1) “If what you do succeeds, will the world be better?” You should be proud of the organization’s success and its effect on people you care about and those with the least power. - 2) “Whose money do they have to take to stay in business?” Understand where revenue really comes from, whether they’re profitable, and how ownership and investors shape incentives. - 3) “What do you have to believe to think that they’re going to succeed?” Every org rests on assumptions about markets, competition, and even political stability. You’re judging whether those assumptions are realistic and whether leaders show systemic self‑awareness. - 4) “What’s the lived experience of the workers there whom you trust? Do you have evidence of leaders making hard choices to do the right thing?” Informal backchannels and real stories about leadership using power responsibly are key culture signals, especially when they’re not PR‑amplified. - 5) “What were you wrong about?” A healthy org can admit mistakes and evolve with new information. Ask this directly in interviews and note how people answer. - 6) “Does your actual compensation take care of what you need for all of your current goals and needs — from day one?” Focus on concrete offer details (after taxes), not vague future promises, to ensure you can meet real‑life obligations. - 7) “Is the role you’re being hired into one where you can credibly advance, and where there’s sufficient resources for success?” Probe for specific career paths, clear expectations, needed skills, and whether the company will invest in your growth; otherwise the role may be a dead end. - Dash closes by acknowledging stacked‑against‑you job markets but argues that “pockets of relative sanity” and good leaders exist. Using these questions systematically helps you find better working worlds. ### 🗒️ Notes - The article complements a previous discussion of “How the hell are you supposed to have a career in tech in 2026?” by offering a more timeless checklist. - The aim is aspiration: these questions help you reach roles where you can “do your best work,” have impact, and live your values, even if no job scores perfectly. - Impact question: If the org meets its goals, will its success improve the world? Would people you love respect your choice? Would marginalized folks see you as someone who cares about consequences? - Money question: Distinguish between customers and investors; both shape behavior, but they’re not the same. In nonprofits, similarly ask who must be kept happy for the institution to survive. - Assumptions question: Examine hidden beliefs about competition, market share, legal stability, and corruption. A lack of realism or resilience is a red flag. - Worker‑experience question: Seek trusted insiders’ accounts of working conditions and leadership behavior. Look for concrete stories of leaders taking care of workers/customers or advocating for responsibility, especially ones you find organically. - Learning/change question: “What were you wrong about?” reveals whether leaders can update beliefs and practices, which predicts adaptability. - Compensation question: Guard against wishful hearing. Ignore talk of future raises/equity until written; focus on whether day‑one pay meets your actual needs. - Advancement/resources question: Ask how your career could progress, what skills you’d need, and whether the company will fund time, training, and support. Vague or politicized paths may signal a ceiling. - Overall, Dash encourages being systematic and holding high standards to locate healthier teams, even inside imperfect organizations. ## 📚 References - Anil Dash — “How to know if that job will crush your soul” https://www.anildash.com/2026/01/12/will-that-job-crush-your-soul/ ## 🗣️ Paraphrase - Paragraph A paraphrase. - Dash introduces a set of seven questions he’s refined over years to help people decide whether a prospective job is aligned with their values or likely to be harmful. - Paragraph B paraphrase. - He argues that while not everyone can find an ideal workplace, using these questions raises your standards and improves your chances of finding roles where you can do meaningful, sustainable work. ## 📰 Newsletter Looking for a healthier tech career path in 2026? Anil Dash’s “How to know if that job will crush your soul” offers seven sharp questions to evaluate roles beyond perks and stack choices. WordPress builders, product folks, and agency owners can adapt these to vet clients, employers, and even internal projects: who funds this work, who it serves, and whether leadership can admit mistakes. Pair it with your next job spec or RFP review and treat it as a culture‑first checklist. Helpful links: - Article: https://www.anildash.com/2026/01/12/will-that-job-crush-your-soul/ - WP Career resources: https://learn.wordpress.org/ - Remote‑work culture guide: https://github.com/basecamp/handbook ## ✅ Action Items #### DevRel - Create a “healthy employer checklist” talk mapping the seven questions to developer job searches and conference hiring booths. - Add a section in docs/example repos about aligning contributions with projects that have positive impact and transparent funding. - Run office hours helping community devs interpret offers (comp, advancement paths, resources). - Publish a blog series on evaluating open‑source‑focused roles for realistic expectations and support. - Survey your dev community about their biggest cultural red flags and integrate into advocacy priorities. #### OSPO - Add culture/impact review questions (modeled on Dash’s seven) to intake for new upstream and vendor relationships. - Include “who funds this?” and “who benefits?” prompts in contribution and dependency policies. - Integrate adaptability (“what were we wrong about?”) into governance charters and retrospectives. - Require clear owner and funding mappings in SBOM and inventory registries. - Develop training for engineers on assessing org incentives before taking on strategic upstream roles. #### Community - Host meetups or panels on recognizing “soul‑crushing” jobs vs. sustainable tech careers. - Offer mentorship circles where maintainers share candid stories about leadership making hard choices for the right reasons. - Publish checklists for contributors and sponsors about expectations, boundaries, and support. - Run cross‑project tabletop exercises on what happens when funding or assumptions suddenly change. #### WordPress - Core: Encourage proposals to explicitly state user impact, funding source, and long‑term maintenance plans. - Core Performance: Tie perf goals to real user experience improvements and document tradeoffs transparently. - Core AI: Apply the “will the world be better?” test to AI‑powered features and their data pipelines. - **Core Program Team:** Bake Dash‑style reflection questions into release retros and team charters. - Mobile: Document sustainable roadmaps that avoid over‑promising beyond team resources. - Playground: Use Playground to simulate realistic job tasks for training and workshops on evaluating roles. - Community: Provide meetup kits about ethical careers, including scripts for group discussions. - Training: Build a course module on evaluating job offers and freelance engagements for health and sustainability. - Marketing: Highlight stories of teams that changed course after realizing they were “wrong about” something impactful. - Support: Track and mitigate burnout signs among volunteers; clarify boundaries of what support teams can realistically do. - Design: Add content patterns that foreground impact, constraints, and future‑change assumptions. - Documentation: Include “assumptions and constraints” sections in major docs pages. - Photos / TV / Polyglots / Accessibility / Meta / CLI / Hosting / Tide / Openverse / Themes / Plugins: - Emphasize transparent governance, realistic commitments, and clear advancement paths for contributors and maintainers. #### The WPOCC - Programs: Offer fellowships for maintainers emphasizing healthy work design and financial stability. - Projects: Run governance clinics on admitting mistakes and course‑correcting. - Funding experiments: Pilot grants that reward ethical choices (e.g., refusing harmful sponsors) and transparent assumptions. ### FAIR - Technical independence: Document where funding and infra dependencies might bias decision‑making. - Policies and covenants: Include “exit ramps” when assumptions about funders or platforms fail. - Productized governance artifacts: Turn Dash’s questions into reusable scorecards for project evaluation. ## 🧪 Hypotheses - H1: Job seekers who use Dash’s seven questions will report higher job satisfaction after 12 months than those who do not. - H2: Organizations whose leaders can clearly answer “What were you wrong about?” experience fewer harmful failures during crises. - H3: Transparent revenue sources correlate with higher worker trust and lower perceived “soul‑crushing” risk. - H4: Clear career‑progression descriptions at hiring time reduce later perceptions of roles as dead ends. - H5: Workers who verify compensation realism (vs. promises) are less likely to feel economically trapped. ### 📊 Methodology - Longitudinal survey of job seekers, randomly assigning some to receive a simplified seven‑question checklist. - Organizational case studies comparing crisis responses where leadership admits errors vs. denies them. - Cross‑sectional survey of employees on revenue transparency, trust, and burnout indicators. - HR data analysis linking documented career paths to retention and satisfaction metrics. - Financial‑wellbeing survey of workers comparing those who modeled after‑tax pay vs. those who relied on verbal promises. ### ❓ Questions - How many job seekers actually feel empowered to walk away from misaligned offers in weak markets? - Can organizations institutionalize “we were wrong” practices without harming perceived authority? - What minimal transparency about funding sources meaningfully changes worker decisions? - How do marginalized workers weigh “impact on the world” against immediate survival needs? ### 🔮 Future Research - Develop validated scales to measure “soul‑crushing job risk.” - Study differences across regions and industries in applying these questions. - Explore how freelance/contract workers adapt the framework to client selection. - Investigate whether open‑source communities use similar implicit heuristics. ### 💡 Implications - Practice: Career coaches and bootcamps can train students on these seven questions. - Policy: Labor organizations might adapt them into checklists for employer standards. - Security: Understanding funders and assumptions clarifies threat models and risk appetite. - Education: Integrate this framework into CS and design curricula around professional ethics. - Funding models: Philanthropy and VC could require explicit assumption mapping in proposals. ### 🧠 Learning Styles Assessment - Reading level estimate: Flesch–Kincaid Grade ≈ 9–10 (conversational but conceptually reflective). #### 👀 Visual learners - Present: Clear headings, bullet lists of questions. - Improve: Simple diagrams showing relationships between impact, funding, assumptions, and worker experience. #### 🔊 Aural learners - Present: None inherent. - Improve: 3–5 minute audio narration or podcast segment discussing the seven questions. #### 🗣️ Verbal learners - Present: Plain‑language explanations, rhetorical questions, narrative examples. - Improve: More analogies and short case vignettes showing good vs. bad orgs. #### 🧩 Kinesthetic learners - Present: Implied action (apply questions to your own offers). - Improve: Worksheets where readers fill in answers for real or hypothetical jobs. #### 🧠 Logical learners - Present: Structured list of seven diagnostic questions. - Improve: Flowcharts for go/no‑go decisions based on answers. #### 🧑‍🤝‍🧑 Social learners - Present: Encouragement to consult trusted workers/backchannels. - Improve: Group discussion guides and peer‑reviewed offer‑evaluation sessions. #### 🧘‍♀️ Solitary learners - Present: Reflective questions suitable for journaling. - Improve: Printable self‑assessment form with scoring rubric. #### 🌿 Naturalistic learners - Present: Limited explicit environment tie‑ins. - Improve: Examples involving environmental and social impact of tech work. ### 📊 Accessibility Assessment #### Screen reader semantics - Present: Likely standard HTML headings and paragraphs from a blog. - Improve: Confirm proper heading hierarchy and descriptive page title. #### Keyboard navigation - Present: Typical blog navigation likely keyboard‑friendly. - Improve: Ensure visible focus states and skip‑to‑content link. #### Contrast and readability - Present: Depends on the site theme; likely adequate but unverified. - Improve: Check color contrast, line length, and spacing against WCAG 2.2 AA. #### Text resizing and reflow - Present: Responsive design likely; text should reflow on smaller screens. - Improve: Test at 200% zoom and with prefers‑reduced‑motion enabled. #### Media and captions - Present: Primarily text; no reliance on media. - Improve: If images or embeds exist, ensure alt text and transcripts as needed. #### Forms and interactions - Present: Minimal or none on a simple article page. - Improve: If comments/forms exist, ensure labels, error messages, and adequate hit targets. #### Standards reference - Map improvements to WCAG 2.2 AA criteria for text alternatives, adaptable content, and operable interfaces. ### 🌍 DEIB Assessment #### Cultural breadth - Present: Tech‑centric, US‑ish context, but broadly applicable ideas. - Improve: Include more global examples and constraints faced by non‑US workers. #### Inclusive language - Present: Generally neutral and inclusive; no obvious slurs or stereotypes. - Improve: More explicit acknowledgement of class, race, immigration, and disability constraints. #### Neurodiversity support - Present: Chunked content and clear structure. - Improve: Add summaries, key‑point callouts, and predictable pattern markers. #### Representation - Present: Focus on roles and institutions, not individuals. - Improve: Include stories from a wider range of identities and career paths. #### Psychological safety - Present: Validates feelings of unease about jobs; names “soul‑crushing” experiences. - Improve: Offer links to support resources (unions, counseling, legal aid) where relevant. ### ✅ Logical Validity #### Strong reasoning - Inductive reasoning: Dash uses common patterns (investor vs. customer incentives, hidden assumptions) to generalize about org behavior. - Causal reasoning: He argues that unrealistic assumptions and opaque funding causally contribute to harmful cultures, which is plausible and widely supported by case histories. #### Fallacies - Some survivorship bias risk: Advice is drawn from tech/professional circles that may not reflect all labor markets; acknowledging structural constraints more explicitly would strengthen it. #### Tone of voice - Tone: conversational, pragmatic, slightly wry, empathetic toward workers. - He balances realism (“deck is stacked against you”) with hopeful pragmatism (“pockets of relative sanity”). ### 🛡️ DARVO Analysis - Deny: No denial of harm; he openly names “soul‑crushing” jobs and stacked decks. - Attack: No attack on workers; mild critique is directed at opaque or irresponsible organizations. - Reverse victim/offender: He does not recast powerful orgs as victims; if anything, he re‑centers worker perspective and autonomy. ## 🎯 Conclusion Dash provides a compact framework of seven questions to help you evaluate prospective jobs for impact, incentives, culture, compensation, and growth. In imperfect markets, you may not get perfect answers, but systematically asking these questions increases your odds of avoiding roles that undermine your well‑being and values. Next steps: turn the questions into your own checklist, use them in interviews and backchannel conversations, and revisit them whenever you consider a career move. ## 🧱 Refactor Appendix (append after 🎯 Conclusion) ### 📚 Literature Split Pad - Purpose: Stage Konik CEE units that become per-source Literature notes. - Split level: **H3**. - Include verbatim quotes under 25 words and a [view highlight] link. ### [H1] 5–10-word present-tense claim > [!quote] [How to know if that job will crush your soul](https://www.anildash.com/2026/01/12/will-that-job-crush-your-soul/) by [[Anil Dash]] via [[anildash.com]]. Published 2026-01-12. > “They're a short list of questions that help you judge whether a job that you’re considering is going to crush your soul or not.” Two lines: context and use. Cite data if relevant. [view highlight](https://www.anildash.com/2026/01/12/will-that-job-crush-your-soul/#H1) #xref #articleseed ID:rw_[MISSING] ### [H2] 5–10-word present-tense claim > [!quote] [How to know if that job will crush your soul](https://www.anildash.com/2026/01/12/will-that-job-crush-your-soul/) > “If what you do succeeds, will the world be better?” Two lines: context and use. [view highlight](https://www.anildash.com/2026/01/12/will-that-job-crush-your-soul/#H2) #xref ID:rw_[MISSING] --- ### 🔖 Atomic Split Pad (Zettel Candidates) - Purpose: Promote reusable claims into Atomic notes. - Split level: **H4**. - Each item: one idea, present tense, specific, testable. #### [Z1] Healthy jobs align impact and incentives - Scope/condition in one line. - Pointer to page/time or dataset. - Links: [[Healthy-Work]] [[Organizational-Incentives]] #### [Z2] Transparent funding predicts better org behavior - Scope/condition in one line. - Pointer to page/time or dataset. - Links: [[Funding-Models]] [[Org-Trust]] --- ### ✏️ Fleeting Queue (Extract by Selection) - Purpose: Capture quick actions or sparks for Fleeting notes. - Extraction: **Select one line** → “Refactor: Extract selection to new note (content only).” - Keep each line short and self-contained. - [F1] Turn Dash’s seven questions into a one-page printable job-offer checklist — context/https://www.anildash.com/2026/01/12/will-that-job-crush-your-soul/ #fleeting #inbox - [F2] Draft an interview-question script based on “What were you wrong about?” — context/https://www.anildash.com/2026/01/12/will-that-job-crush-your-soul/ #fleeting #inbox - [F3] Create a comparative matrix for multiple offers using the seven-question framework — context/https://www.anildash.com/2026/01/12/will-that-job-crush-your-soul/ #fleeting #inbox --- <!-- deep-read:sections end -->