AI and Your Career
Will AI replace your role — and how do you become the person it makes more valuable? The AI-era career layer for engineers and professionals: what gets cheap, what becomes the moat, the new stack, and a 90-day plan per role, plus the tool-literacy handbooks, interview prep, and salary data.
Handbooks 31
AI for Lawyers
The practical middle ground for legal professionals: where AI genuinely helps (first drafts, brief summaries, review triage), the three non-negotiable rules — confidentiality, verify every citation, you sign it you own it — five workflow recipes with exact prompts, a spot-the-danger judgment exercise, and the five questions to ask any AI vendor. No coding required.
AI for Doctors
The practical middle ground for clinicians: where AI genuinely helps (notes from dictation, discharge instructions, prior auths, literature summaries), the three non-negotiable rules — PHI needs a BAA, verify everything clinical, the chart is yours — five workflow recipes with exact prompts, a spot-the-danger judgment exercise, and the six questions to ask any clinical AI vendor. No coding required.
AI for Civil Engineers
The practical middle ground for civil and structural engineers: where AI genuinely helps (observation reports, RFI responses, meeting minutes, plain-language explanations), the three non-negotiable rules — the adopted code is the authority, calculations get checked independently, your stamp is yours — five workflow recipes with exact prompts, a spot-the-danger judgment exercise, and the vendor questions that matter. No coding required.
The Salary Negotiation Handbook
The expected-value case for always countering an offer. A polite counter is accepted with some probability p and otherwise the employer just holds the original (they essentially never rescind over a reasonable ask), so EV = p·counter + (1−p)·original beats accepting for any p>0 — heads you win, tails you break even. Your BATNA (best alternative) is your real leverage and your accept-floor; improve it before the conversation with competing offers. And a base bump compounds — its lifetime value is a geometric series, ≈$55k for a $10k raise over 5 years at 5%, not $50k. Plus how to actually do it (research, let them anchor, counter in writing, negotiate the whole package and level) and the traps. With worked math and a runnable EV calculator.
The Resume & Portfolio Handbook
Your resume has two readers and the first isn't human. Most applications hit an ATS (applicant tracking system) that scores keyword coverage against the job — coverage = |resume ∩ required| / |required| — and auto-filters anything below a threshold, so a qualified engineer gets rejected on missing keywords. Step one: clear the machine by tailoring keywords in the posting's own words (for skills you have) in a clean single-column format that parses. Step two: win the human with quantified-impact bullets — a bullet with a number ("reduced latency 40%") beats a vague responsibility ("worked on the backend"). Plus what an engineer's portfolio needs (a few working, well-documented projects, curated not exhaustive) and the traps. With worked math (ATS coverage + gate, bullet impact) and a runnable resume scorer.
The Staff Engineer Behaviors Handbook
The hardest promotion in engineering — senior to staff — trips people up because they aim at the wrong target: writing more/better code, when the level is a change in the unit of impact. Senior is measured by own output; staff+ by leverage — the output you create in others (an architecture that unblocks three teams, a standard that speeds everyone, a mentee who levels up). Total impact = own_output + Σ multipliers, a team-wide boost is worth team_size × per_person_boost, and staff-level is the threshold where leverage dominates personal output. Covers Larson's four archetypes (tech lead / architect / solver / right hand), glue work and why it's under-credited, how to operate (work on what matters, write relentlessly, influence without authority, multiply others, stay technically credible), and the traps (hero IC, architecture astronaut, invisible glue). With a worked leverage model and runnable code.
AI for Accountants
The practical middle ground for accounting and tax professionals: where AI genuinely helps (first drafts, document summaries, reconciliation triage, plain-language client explanations), the three non-negotiable rules — client-data confidentiality (incl. IRC §7216), verify every number and authority, you sign it you own it — five workflow recipes with exact prompts, a spot-the-danger judgment exercise, and the five questions to ask any AI vendor. No coding required.
AI for Teachers
The practical middle ground for educators: where AI genuinely helps (lesson plans, differentiating materials into reading levels, first-draft feedback and rubrics, quiz generation, parent emails), the three non-negotiable rules — student-data privacy (FERPA), verify every fact and answer key, you are still the teacher — five workflow recipes with exact prompts, how to handle AI in students' own work (detectors are unreliable), and the questions to ask any AI vendor. No coding required.
AI for Architects
The practical middle ground for architectural practice: where AI genuinely helps (concept ideation, first-draft narratives and specs, document summaries, research starting points, early renderings), the three non-negotiable rules — you stamp it you own it, verify every code/zoning/structural claim against the adopted code, protect confidential client and site data — five workflow recipes with exact prompts, a spot-the-danger judgment exercise, and the questions to ask any AI vendor. No coding required.
AI for Real Estate
The practical middle ground for agents and brokers: where AI genuinely helps (listing descriptions, client follow-ups, market-data summaries, process explanations, social content), the three non-negotiable rules — fair-housing compliance (AI easily generates illegal steering language), verify every fact and number, you are not giving legal/tax/appraisal advice — five workflow recipes with exact prompts, a spot-the-danger judgment exercise, and the questions to ask any AI vendor. No coding required.
AI for Marketers
The practical middle ground for marketers: where AI genuinely helps (first-draft copy, ideation, repurposing one asset into many formats, briefs, research/analytics summaries), the three non-negotiable rules — never publish fabricated claims/stats/testimonials (FTC false-advertising risk), stay on-brand and recognizably human, verify facts and respect IP — five workflow recipes with exact prompts, a spot-the-danger judgment exercise, and the questions to ask any AI vendor. No coding required.
AI for HR
The practical middle ground for HR and recruiting: where AI genuinely helps (job descriptions, first-draft policies, structured interview guides, internal comms, anonymized feedback summaries), the three non-negotiable rules — AI never makes a consequential decision about a person (a human decides), actively guard against discrimination/bias (EEOC + NYC Local Law 144 + EU AI Act high-risk), protect sensitive candidate/employee data — five workflow recipes with exact prompts, a spot-the-danger judgment exercise, and the questions to ask any AI vendor. No coding required.
AI for Financial Analysts
The practical middle ground for financial analysis: where AI genuinely helps (summarizing filings and transcripts, first-draft memos and commentary, structuring/stress-testing model logic, first-pass qualitative research), the three non-negotiable rules — verify every number/calculation/source (models miscalculate and fabricate figures), MNPI and confidential data never touch an unapproved tool (information barriers, securities law), the analysis and recommendation and accountability are yours — five workflow recipes with exact prompts, a spot-the-danger judgment exercise, and the questions to ask any AI vendor. No coding required.
AI for Journalists
The practical middle ground for reporters and editors: where AI genuinely helps (transcription, document/report summaries, headline and structure ideas, research starting points, plain-language explainers), the three non-negotiable rules — verify everything and never publish an unverified fact or quote (models fabricate quotes and sources), protect your sources and confidential material, be transparent and never pass AI text off as reporting (plagiarism/attribution) — five workflow recipes with exact prompts, a spot-the-danger judgment exercise, and the questions to ask any AI vendor. No coding required.
AI for Product Managers
The practical middle ground for PMs: where AI genuinely helps (PRD/spec drafts, synthesizing research you actually gathered, competitive-scan starting points, pressure-testing your reasoning, stakeholder comms), the three non-negotiable rules — never let AI fabricate user data/metrics/findings (it invents plausible insights representing nobody), prioritization and product judgment stay human, protect confidential roadmap and customer data — five workflow recipes with exact prompts, a spot-the-danger judgment exercise, and the questions to ask any AI vendor. No coding required.
AI for Sales
The practical middle ground for sales reps: where AI genuinely helps (personalized outreach from real research, follow-ups, call summaries from your notes, objection prep, CRM drafts), the three non-negotiable rules — never make a false product claim or over-promise (AI invents features/results = misrepresentation that breaks deals and trust), protect prospect data and follow call-recording/consent law, the relationship and discovery and close stay human — five workflow recipes with exact prompts, a spot-the-danger judgment exercise, and the questions to ask any AI vendor. No coding required.
AI-Assisted Interviews
The 2026 technical-interview FORMAT (distinct from the content handbooks): AI is now allowed in the room, so the exam shifts from writing algorithms from memory to working WITH AI — code-comprehension rounds, AI-fluency rubrics, and frontier-lab eval-design rounds. The one equation behind the shift: when the AI is correct with probability p, a reviewing human's value is pure review skill — final = p·(1−p_falsepos) + (1−p)·p_catch — so a skilled reviewer lifts output above the AI alone while a careless one (breaks correct code, catches little) drags it BELOW raw AI (an unskilled AI user is net-negative). The new round types and how to prepare (read/audit/test, not just write). Worked math plus a runnable reviewer-value model.
The AI-Era Backend Engineer
How the backend-engineer job changes in the AI era — and how to be the one who gets more valuable, not less. Boilerplate, CRUD and first-draft tests get cheap; system design, debugging, security judgment and production ownership become the moat. The new stack (reviewing AI code, spec-driven development, evals + cost/latency for LLM features), five AI-augmented workflows, a judgment exercise, and a 90-day plan.
The AI-Era Frontend Engineer
How the frontend-engineer job changes in the AI era — and how to be the one who gets more valuable. Component scaffolding, CSS and markup get cheap; interaction and UX judgment, accessibility, performance and perceived latency, state architecture, and building AI-native interfaces (streaming, chat, copilot) become the moat. The new stack, five AI-augmented workflows, a judgment exercise, and a 90-day plan.
The AI-Era Product Manager
How the product-manager job changes in the AI era — and how to be the PM who gets more valuable. PRDs, research synthesis and comms get cheap; judgment, taste, user truth and accountability become the moat, plus a new stack: evals literacy, the unit economics of AI features, and agent/AI UX. Five AI-augmented workflows, a judgment exercise, and a 90-day plan. The career companion to AI for Product Managers (tool literacy).
The AI-Era DevOps Engineer
How the DevOps / platform-engineer job changes in the AI era. Pipeline YAML, Dockerfiles, boilerplate IaC and scripts get cheap; reliability, incident response, security, cost/FinOps and platform-as-product become the moat — plus a new stack: reviewing AI-generated infrastructure for blast radius, AIOps signal-vs-noise, and golden paths. Five AI-augmented workflows, a judgment exercise, and a 90-day plan.
The AI-Era Data Engineer
How the data-engineer job changes in the AI era. SQL, pipeline glue and connector code get cheap; data modeling, quality and contracts, cost, lineage and the semantic layer become the moat — plus a new high-demand specialty: building the data pipelines that feed AI (RAG ingestion, embeddings, eval datasets). Five AI-augmented workflows, a judgment exercise, and a 90-day plan.
The AI-Era QA Engineer
How the QA / test-engineer job changes in the AI era. Writing test scripts, selectors and boilerplate cases gets cheap; test strategy, exploratory testing, risk-based judgment, and the new discipline of testing AI and nondeterministic systems (evals, not assertEquals) become the moat. Five AI-augmented workflows, a judgment exercise, and a 90-day plan.
The AI-Era Engineering Manager
How the engineering-manager job changes in the AI era. Status reports, summaries and first-draft reviews get cheap; people leadership, technical judgment, hiring and setting direction become the moat — plus a new mandate: leading AI-augmented teams and measuring output, not activity. Five AI-augmented workflows, a judgment exercise, and a 90-day plan.
AI for Designers
A practical handbook on using AI in design: where it genuinely helps (exploring variations, first-draft copy and assets, synthesizing research you gathered) and where it must not decide (taste, brand coherence, accessibility, real user empathy). The three rules, five workflow recipes, a judgment exercise on IP and bias, and how to choose tools. No coding, no hype.
The New Grad in the AI Era
A straight answer to “AI is killing junior roles — what do I even learn?” The junior grind (boilerplate, glue, first-draft tests) is being automated, so the bar shifts to fundamentals, judgment, and working WITH AI earlier — and you need fundamentals more, not less. What to learn now, five moves for your first months, a judgment exercise, and a 90-day plan.
AI for Support Engineers
Support automation is the #1 deployed AI use case, so this role is changing fast. What AI automates (tier-1 tickets, FAQs, routing) versus what becomes valuable (hard troubleshooting, escalation judgment, empathy, and improving the AI itself), the new support stack, and the high-value pivots — agent-ops, AI-support engineering, and forward-deployed engineering. Five moves, a judgment exercise, and a plan.
AI for Data Analysts
Text-to-SQL and auto-dashboards are automating the mechanical half of analysis. What AI automates (writing SQL, basic dashboards, pulling numbers) versus what becomes valuable (asking the right question, judging whether data can be trusted, interpreting results in business context, and defining what the metrics mean), plus the analytics-engineering escape hatch. Five moves, a judgment exercise, and a plan.
AI for Technical Writers
AI drafts docs, generates API reference from code, and answers user questions directly — so fewer people read the docs at all. But the twist most miss: your documentation is now the context layer AI assistants, agents, and RAG systems read from, and an AI that reads wrong or unstructured docs gives confident wrong answers at scale. What AI automates (first drafts, boilerplate, formatting) versus what becomes valuable (information architecture, docs-as-context, docs-as-evals, owning the source of truth), plus the pivots — docs/DX engineering, developer relations, and AI knowledge engineering. Five moves, a judgment exercise, and a plan.
AI for Business Analysts
AI drafts requirements docs, turns meeting notes into user stories, summarizes stakeholder calls, and writes the SQL for your reports. But the hard part of business analysis was never the writing — it was asking the right questions, resolving conflicting requirements, and deciding what is actually worth building. What AI automates (documentation, first-draft stories, process diagrams, basic queries) versus what becomes valuable (problem definition, stakeholder judgment, process redesign, validating that requirements match reality), plus the pivots — analytics engineer, AI product manager, and product owner. Five moves, a judgment exercise, and a plan.
AI for Technical Program Managers
AI writes your status reports, summarizes the meeting, updates the tracker, and drafts the project plan — the reporting layer of program management is being automated. But the job was never the reports; it was driving cross-team execution, killing the risks that matter, and forcing decisions when senior people disagree. What AI automates (status, notes, trackers, first-draft plans) versus what becomes valuable (cross-org coordination, risk judgment, technical depth to challenge estimates, unblocking), how the TPM role differs from product management, and the pivots — engineering manager, product manager, and AI-program leadership. Five moves, a judgment exercise, and a plan.