Salesforce interviews reward people who can explain why they would build something a certain way, not just recite definitions. Whether you are aiming for an admin, developer, consultant or Agentforce-focused role, the same pattern shows up: a few fundamentals, a scenario question or two, and a conversation about trade-offs. This guide covers the roles, the skills worth building, the questions that come up most, and a practical way to prepare. Which Salesforce Role Fits You? Role What you do Interviewers look for Administrator Configure the org: objects, fields, security, flows, reports, user support. Data model, security model, Flow, and clear communication with business users. Developer Build custom logic and UI with Apex, Lightning Web Components and integrations. Apex, triggers, governor limits, SOQL, testing, LWC basics, integration patterns. Consultant / Business Analyst Turn business needs into a Salesforce solution and guide delivery. Requirements gathering, solution tr...
In my previous post I summarized Anthropic's AI-Native SDLC Playbook , which explains how to redesign the software lifecycle once AI agents can write code faster than your process can absorb it. This post is the practical follow-up: how to actually apply it to a web development project, step by step , with files you can copy into your own repo. Throughout this post I'll use one running example: a Next.js + TypeScript e-commerce app that needs a new "Wishlist" feature. The same steps work for React + Node, Vue, Laravel, Django, or any other web stack. Only the commands change. The workflow at a glance Each stage ends by committing a file, and the next stage starts by reading it: Plan → docs/intent/wishlist.md (what and why) Design → docs/specs/wishlist.md (how) Build → code + tests (guided by CLAUDE.md and Skills) Test → passing tests + CI evals Deploy → PR with AI review findings → human approval → CI/CD Maintain...