HR and Future of Work Journalist
Publications:
Kaila Caldwell is a freelance journalist contributing to Deel Works, Deel's B2B editorial publication for HR leaders, CHROs, and people managers. She reports on workforce trends, compensation, management, and the future of talent, combining original reporting, expert interviews, and primary data to produce long-form features for business leaders and decision-makers worldwide. Before Deel Works, she spent several years as an editor and journalist covering the future of work, AI, workforce transformation, economics, and sustainable finance. She has lived and worked in the US, France, and Tunisia, and is currently based in Washington, D.C.






I’m reporting a Deel Works feature for HR/people leaders on what happens when employers give AI authority to act inside an employment workflow, rather than simply recommend something for a person to do. I’m seeking an HR, TA, People Ops, HRIS or HR-tech leader at an employer using a real system that can take at least one workflow action without separate human approval every time—for example, rank/advance candidates, trigger assessments or interviews, send candidate communications, update an ATS or initiate another step. Recommendation-only AI, résumé summarizers, job-description generators and general ChatGPT use do not qualify. No vendor spokespeople for this query. The article asks what HR actually delegates, where human authority remains, what evidence survives the decision and who owns the outcome if it is challenged. Please address the questions where you have direct experience: What exact workflow uses the agent, and what can it do without a person approving each action? Which actions remain human-only, and who decided that boundary? At what point does human review occur, and what does the reviewer actually see? Can reviewers reverse the agent’s action, and are overrides recorded? What has the agent already done before a human first looks at the case? What records let HR reconstruct what the agent read, recommended, changed or initiated? Who holds those records—you, the vendor or both? If a candidate challenges an outcome, could HR explain how that specific decision occurred? Who can pause the agent, and who determines whether earlier decisions need to be re-reviewed after a problem? Who inside the organization ultimately owns the resulting employment decision? Did you create or change governance specifically for this agent rather than relying on a general AI policy? What changed? What vendor access or contractual rights—logs, audit rights, retention, model-change notices, incident cooperation—proved important? I’m especially interested in a source who can walk me through one actual workflow from application to agent action to human review, including permissions the company deliberately chose not to automate. Please include your title/company, system or use case, your role in selecting/governing it and what can be discussed on the record.
Deadline: Oct 9th, 2026 12:00 AM ET
•Deel Works
I’m reporting a Deel Works feature for HR/people leaders on what responsibility remains with employers when AI moves from recommending an employment action to acting within authority the company has delegated. Seeking an employment attorney with direct experience involving automated hiring/screening, AI employment discrimination, AEDTs or HR-tech vendors. Please have personally litigated, investigated or advised on an automated employment matter, vendor arrangement or challenged AI-assisted decision. I’m not looking for generic AI-risk commentary. The article examines what existing employment law already requires, what remains unsettled, and what evidence matters if an automated employment decision is challenged. Questions: Does it legally matter whether AI recommends an employment action versus takes it without contemporaneous approval, or is the key issue the employment function/effect? If software ranks, advances or rejects candidates, what obligations remain with the employer? What should HR reasonably take from Mobley v. Workday now, and what would overread the rulings? When could both employer and vendor face scrutiny for different parts of a decision? What makes human review meaningful rather than a rubber stamp? If a candidate challenges an automated rejection, what records would you seek? Which missing records—inputs, criteria, logs, versions, approvals, overrides—create the biggest problem? What should employers require contractually so they can investigate/defend a decision later? If a system may have acted outside approved criteria or affected a protected group disproportionately, what should HR preserve, pause or re-review? Can you give a concrete matter/fact pattern, without naming a client, where oversight, vendor access or decision records mattered? Plaintiff-side and management-side attorneys are both welcome. Please distinguish established law from best practice or unsettled issues, and identify the direct experience supporting your answers. Please include your title, firm, jurisdictions, relevant matter/advisory experience and what you can discuss on the record.
Deadline: Oct 9th, 2026 12:00 AM ET
•Deel Works
I’m reporting a Deel Works feature for HR leaders on how employers turn general AI governance into concrete controls when an AI agent can act inside an employment workflow. Seeking a responsible-AI, AI governance, AI risk or enterprise implementation leader who has personally designed or implemented governance for agentic systems in production. In-house or independent is fine. HR deployments are ideal; other consequential enterprise agents can qualify if you can clearly apply the governance mechanics to HR. Not seeking general AI-ethics commentary. I need firsthand experience translating policy into permissions, approval gates, monitoring, escalation and ownership. Questions: What is materially different about governing an agent that can act versus AI that only generates an output? How should a company define what an agent may recommend, initiate or execute? Who should approve those permissions when the workflow affects hiring/employment? How do you decide which actions require human approval before the action versus monitoring afterward? What makes “human in the loop” meaningful rather than ceremonial? What should the reviewer see and be empowered to do? What must be logged to reconstruct a multi-step agent workflow later? What should trigger alerts, automatic suspension or escalation, and who should have stopping authority? How should permission, model, tool or workflow changes be governed after launch? How should HR, IT, Legal, Compliance, Security and the business divide responsibility? Have you seen general AI policies fail to answer agent-specific questions? What was missing? Can you give a deployment or near miss that changed how you designed controls? Please include the deployments you worked on, your exact role and controls you personally designed or implemented. Firsthand experience will be prioritized over framework-only commentary. The article is for HR/people leaders, so please translate governance concepts into practical employment decisions. I’m especially interested in where written policy and actual system configuration diverge, how companies test that approval/monitoring controls work, and where ownership breaks down.
Deadline: Oct 9th, 2026 12:00 AM ET
•Deel Works
I’m reporting a Deel Works feature for HR/people leaders on whether employers can reconstruct and defend an employment decision after AI materially influences or acts inside the workflow. Seeking an independent algorithmic auditor, AI assurance professional, technical responsible-AI auditor or researcher/practitioner who has personally audited or evaluated automated hiring/employment systems. NYC Local Law 144 experience is useful, but I especially need expertise beyond selection-rate calculations: decision records, provenance, logs, version changes, human review and multi-step/agentic workflows. No vendors promoting their own monitoring product. Please identify actual audits/evaluations you have conducted. Questions: If AI ranks, advances or rejects a candidate, what evidence is needed to reconstruct that decision later? Which records matter most: source data, inputs, instructions, outputs, tool calls, actions, model/version, timestamps, approvals or overrides? What do employers most often fail to retain or cannot obtain from vendors? How does auditing a multi-step agent differ from auditing a model that produces one score? Is the final output enough to explain a challenged decision? What is otherwise missing? How should model, prompt, tool, data-source or permission changes be versioned? Can human review itself be audited? How can you distinguish independent judgment from rubber-stamping? What evidence demonstrates that an agent stayed within authorized boundaries? What should employers require vendors to log, retain and make available? How should audits handle data split across employer and vendor systems? What can a bias audit establish—and what can it NOT establish about a specific challenged decision? Can you give an example where missing records or weak human-review documentation prevented a meaningful audit? Please distinguish regulatory audit requirements from broader technical assurance and explain what cannot reliably be reconstructed after the fact. I’m especially interested in evidence that would matter if an applicant, regulator or court later asked how a specific decision occurred—not merely dashboards used for internal model monitoring.
Deadline: Oct 9th, 2026 12:00 AM ET
•Deel Works
I’m reporting a Deel Works feature for HR leaders on what happens when AI moves from recommending an employment action to taking actions inside a hiring or employment workflow. Seeking a senior product, engineering, AI governance, trust/compliance or legal leader at an HR-tech company whose CURRENT product can autonomously take at least one action—for example, rank/advance candidates, trigger assessments/interviews, send candidate communications, update an ATS or initiate another step without separate human approval each time. This is NOT a product-promotion query. To qualify, state exactly what the product can do autonomously, what it cannot do and your role in designing/governing those capabilities. Generic “AI-powered recruiting” pitches will not be used. Questions: Which workflow actions can your product execute without contemporaneous human approval? Which actions are prohibited or gated, and why? Who sets those boundaries—vendor, customer or both? What does a human reviewer see, and can they inspect evidence and override? What is logged: inputs, instructions, tools, actions, model/version, timestamps, approvals, overrides? Which logs/decision data can the employer export or retain independently? How are model, prompt, tool, permission or workflow changes communicated/versioned? What alerts or automatic stops exist if the agent operates outside expected parameters? If a candidate challenges a decision, what can the employer obtain to reconstruct it? Where does vendor responsibility end and employer responsibility begin? What audit rights, retention commitments, change notices or claims cooperation do customers request? What limitation or governance problem do buyers routinely underestimate? Please answer on the record and include the exact product/use case. I’m especially interested in what customers can verify independently, not only what the vendor sees internally. If capabilities vary by configuration, contract tier or customer setup, say so.
Deadline: Oct 9th, 2026 12:00 AM ET
•Deel Works
No guidelines added yet. Add your pitching preferences to help sources craft the perfect outreach.