What Siri’s Upgrade And This Week’s Layoff Data Mean For You

Apple shipped a free AI assistant to every recent iPhone and Mac this week, GitHub Copilot began pulling Jira tickets into the editor, job seekers are teaching themselves AI faster than employers train them, and layoff trackers now name AI as a stated reason for cuts. Each change moves the bar on what you’re expected to already know.

Your phone just got an AI upgrade

Your phone just got an AI upgrade because Apple’s Siri beta, released with iOS 27 on September 14, 2026, turns the assistant already on your device into a tool that drafts emails and manages calendar entries without opening a separate app, according to Apple Newsroom. It also reads what’s on your screen and answers questions about it. Apple calls the update \”profoundly more capable and personal,\” per the same announcement, and that description comes from Apple, not an independent reviewer. Treat the beta label literally. Test it on low-stakes tasks, like drafting an internal note or checking a calendar clash, before you hand it anything client-facing.

Copilot now chases your tickets

Copilot now chases your tickets because GitHub added Jira integration and scheduled recurring agents to Copilot this week, according to the GitHub Changelog published September 10, 2026. Developers can assign Copilot ongoing background work and pull Jira tickets straight into the IDE, cutting manual ticket triage and status updates, per the same changelog. The tasks this removes are the ones nobody enjoyed anyway: copying ticket numbers and writing status updates. What it doesn’t remove is judgment, like deciding which ticket is worth doing first and catching when the agent solved the wrong problem. If your manager asks how a ticket got closed overnight, be ready to explain the agent’s role plainly, the way I’ve laid out in how to explain AI-assisted work to a boss who doesn’t trust it.

Why do job seekers now outlearn employers?

Why do job seekers now outlearn employers? Because 47 percent of them are teaching themselves AI skills on their own time while employer-led AI training has stayed flat, according to ICIMS data published September 10, 2026. The same report counts roughly 30 applicants for every open role right now. Put those two numbers together and waiting for your company to run an AI training session stops looking like patience and starts looking like a bet you’re likely to lose. I’ve written before about why employers are starting to list AI skills as a requirement rather than a bonus in why employers now require AI skills and what to do, and this week’s ICIMS numbers are the clearest evidence yet that the requirement is arriving faster than most training budgets.

Do AI layoffs prove AI did it?

Do AI layoffs prove AI did it? Not on their own. SkillSyncer’s tracker, updated September 15, 2026, found that nearly half of 2026 layoffs now cite AI as a factor. That’s a count of public statements companies chose to make, not a controlled study of what caused each cut. A company can cite AI because it’s true, or because it’s a cleaner story than admitting it overhired or missed a forecast. The tracker also can’t count layoffs nobody announced. What it does establish is that AI has become a stated, public reason for cuts often enough that job seekers in customer support and QA can’t treat it as a fringe risk anymore. I covered what the first wave of this data meant in what half of 2026’s AI layoffs mean for your job, and this update moves the number closer to half.

Four AI moves, ranked by cost of ignoring them

Four things changed this week in how AI touches your job, ranked by what skipping each one costs you.

1. Not building an AI habit before you job hunt. With roughly 30 applicants per opening and 47 percent of job seekers already self-teaching AI, per ICIMS, arriving at an interview without one puts you behind candidates who already have one.
2. Staying in a role built entirely around tasks AI already automates. With nearly half of 2026 layoffs citing AI as a factor, according to SkillSyncer, this is the riskiest place to sit still right now.
3. Skipping Copilot’s new scheduled agents if you’re a developer. GitHub’s changelog shows recurring background work and Jira pulls are live now, and teammates who adopt it first will look faster on shared tickets.
4. Not trying Siri’s beta on one real task. Apple’s new assistant is free on devices many professionals already own, so skipping it costs nothing to fix.

What should you do about it this week?

What should you do about it this week? Act on one thing, not everything at once. If you’re job hunting, spend thirty minutes with a free AI tool on an actual task from your target role, not a toy example, so you have something specific to describe in an interview. If you’re in a role that touches customer support or QA, write down the parts of your job that need judgment a current tool can’t replicate, and make that judgment visible to your manager. If you’re a developer, turn on one of Copilot’s new scheduled agents for a routine, low-risk task and watch what it gets wrong before you trust it with anything bigger.

You are helping me evaluate whether an AI assistant (like Siri on iOS 27) is ready to help with my actual job, not a demo task. Here is the real task: [paste a real email you need to write, or a real scheduling situation]. Draft it the way I would send it, in my voice, using only the details I give you. Do not invent details I haven't given you, including names or dates. After drafting, tell me specifically what you're unsure about or what you'd need me to confirm before this goes out. If my instructions are unclear, ask me before you draft anything.

Act as a career coach helping a job seeker close an AI skills gap in the next 30 days, with no budget for paid courses. My current role is [your role], my target role is [target role], and here is what I currently know about AI tools: [describe honestly, even if it's 'almost nothing']. Give me a week-by-week plan using only free tools and resources, with one specific, checkable task per week, not something vague like 'learn prompt engineering.' Ask me clarifying questions about my schedule and target role before you build the plan.

Help me write a short, honest explanation for my manager of how I used AI on a specific piece of work: [describe the task and what the AI tool did]. The explanation should say plainly what the tool did versus what I did, and why I trust the result enough to send it, based on what I checked beforehand. Keep it to one paragraph, in plain language, with no jargon and no exaggeration of the tool's role. If you think my explanation overstates or understates what the AI did, tell me directly.

Act as a blunt hiring manager who has read ten thousand resumes, not a career coach. I will paste my full resume and the job description I want. Rewrite the whole resume for that role, section by section, in this order: summary, experience, skills, education. Rules: every experience line leads with impact, not duty. Use bracketed placeholders like [8 percent] for any number I did not give you, and list at the end every placeholder I need to replace with a real figure. Keep it to one page of text. Plain formatting only, no tables or columns, so screening software can parse it. After the rewrite, tell me the three weakest claims that need evidence before I send this anywhere. My resume: [paste resume]. The role: [paste job description].