
Using AI Is No Longer Enough: Prove the Value You Deliver
A practical guide for senior engineers, researchers, developers, data scientists and technical leaders preparing for interviews, internal promotions, senior technical appointments or broader leadership responsibility.
By Dai Jones, Founder & Lead Consultant, Eich Dyn Career Services · Written
A practical Eich Dyn guide for senior engineers, researchers, developers, data scientists and technical leaders.
The shift in expectations: “I use AI” describes an activity. “I used AI to improve a process, validate an engineering decision, reduce avoidable effort and release capacity — with controls and measurable results” demonstrates capability.
1. Why I wrote this guide
Throughout my career in engineering and leadership, I have seen the same distinction make a difference to career progression: the strongest people can explain not only what they know, but what they have changed and why it mattered.
AI makes that distinction sharper. Access to a chatbot, coding assistant or research tool is no longer, by itself, convincing evidence of value. The important questions are what problem you chose, whether AI was an appropriate solution, what improvement you delivered, what you checked, and which decisions required your own professional judgement.
I wrote this guide because talented engineers and technical specialists can undersell themselves at precisely the moment they need to demonstrate commercial and leadership impact. A candidate may say, “I use AI every day,” while missing a far more powerful account of reduced development time, stronger evidence, better test coverage, improved research quality or a controlled decision process.
For professionals working towards a new role or an internal promotion through Career OS™ MOVE and PROPEL, this is an opportunity to build a portfolio of demonstrated AI-enabled contribution. The following examples are designed to help you identify that evidence in your own work — not to encourage exaggerated claims or the unsafe deployment of AI.

2. Executive summary
- AI familiarity is increasingly relevant, but use alone is a weak differentiator. Hiring and skills research points to growing demand for AI capability; how widespread that expectation is varies by employer, role and sector. LinkedIn (2025); World Economic Forum (2025).
- The evidence standard is changing. A 16 October 2026 study of Anthropic's own workforce found that interviewers referred to candidates' AI-tool experience much more frequently and increasingly discussed autonomy and judgement. This is an early signal from one AI-intensive company, not proof of an equivalent shift at all UK engineering employers. Anthropic (2026).
- Senior contribution spans six value types: efficiency, research, assistance tools, agents, evidence and assurance, and reasoning and decision support. The strongest examples combine technical skill with problem selection, adoption, evaluation and human accountability.
- A claim needs a baseline and a check. Explain the before-and-after process, throughput or quality, the costs of human review, the limitations and the resulting benefit. Where value has not yet been measured, call it a pilot or hypothesis.
- Regulated sectors raise the bar. In healthcare, defence, automotive and aerospace, traceability, controlled data, validation and meaningful human oversight may matter more than raw speed. NIST AI RMF; UK Government AI Playbook.
The career question to prepare for: “Show me a problem where you used AI responsibly to deliver an outcome that would have been harder, slower or less robust without it.”
3. What the research actually tells us
The Anthropic signal: hiring language is moving
Anthropic's research, How employment is changing at Anthropic, published on 16 October 2026, combined internal employment and output records, AI usage, communications, calendars, thousands of hiring scorecards and 17 employee interviews. Its findings include:
| Signal within Anthropic | Earlier observation | Later observation | What this means for a candidate |
|---|---|---|---|
| Technical hiring assessments mentioning AI-tool experience | About 5% in 2024 | About 15% in 2026 — 3× | Prepare a concrete use-case story, not a tool list. |
| Non-technical hiring assessments mentioning AI-tool experience | About 7% in 2024 | About 28% in 2026 — 4× | AI-enabled improvement is extending beyond specialist technical jobs. |
| Junior technical hires as a share of technical hiring | 27% in the earlier comparison | 9% in 2026 | Demonstrating autonomy, learning and delivery may be increasingly important; this is not a universal prediction for graduate jobs. |
| Monthly cross-department moves by employees with at least one year's service | 2025 baseline | 50% more likely in 2026 | Internal mobility and the ability to redeploy skills may become more valuable. |
Source: Anthropic, “How employment is changing at Anthropic” (2026). The first two rows are approximate proportions reported in the paper, with 2026 values corresponding to its stated tripling and quadrupling. The mobility comparison is a relative likelihood, not a 50-percentage-point change.
The study also reports increased discussion of autonomy and judgement in technical hiring assessments and a declining relative share of discussion about technical domain expertise. It does not show that specialist engineering knowledge has become unnecessary, or that hiring managers across every industry now use the same criteria.
Wider signals — with limits
| Source | What it supports | What it does not establish |
|---|---|---|
| LinkedIn, Skills on the Rise (2025) | AI literacy and large-language-model proficiency were among fast-growing skill areas in its analysis. | That an AI project is compulsory for every vacancy. |
| World Economic Forum, Future of Jobs (2025) | Surveyed employers expected AI and big-data skills to grow quickly; analytical thinking and leadership remained important. | That human judgement or established domain competence are being replaced. |
| Microsoft, Work Trend Index (2025) | In its global survey, 46% of leaders reported their organisation used agents to fully automate workflows or business processes. | That 46% of all organisations have verified, mature agent deployments; the figure is leader self-report. |
| Skills England, Defence Sector Assessment (2026) | Identifies growing needs in defence for model validation, data stewardship, secure human–AI collaboration and judgement. | That sensitive defence activities can be transferred to unapproved AI services. |
My interpretation: AI competence is moving closer to the front of the discussion for many senior technical careers. The differentiator is credible, responsible delivery. Employers will still assess the fundamentals: technical depth, safety, collaboration, leadership, communication and sound reasoning.

4. The six types of AI value employers can assess
| Value type | What an employer wants to understand | Evidence that carries weight | Weak version of the claim |
|---|---|---|---|
| 1. Efficiency and throughput | Did you remove waste or increase useful capacity? | Before/after cycle time, rework, throughput, review effort and total cost. | “AI made me faster.” |
| 2. Research and discovery | Did you improve the range, speed, rigour or reproducibility of investigation? | Search protocol, source coverage, comparison matrix, hypothesis quality, reproduced results. | “AI summarised papers for me.” |
| 3. Assistance tools | Did you create a dependable tool that helps colleagues perform a defined task? | User adoption, tested answer accuracy, maintained knowledge sources, time saved and escalation route. | “I built a chatbot.” |
| 4. Agents and workflow orchestration | Did you design, supervise or deploy a bounded multi-step process? | Scope, permissions, logs, exception rate, human approval gates, monitored output and recovery. | “I have agents working for me.” |
| 5. Evidence, quality and assurance | Did you improve traceability, test coverage, documentation or auditability? | Linked requirements and tests, reproducible checks, defect capture, error rate and sign-off record. | “AI wrote the report.” |
| 6. Reasoning and decisions | Did AI expand the options while you exercised better judgement? | Assumptions, alternatives, sensitivity analysis, counter-evidence, decision rationale and result. | “AI recommended the answer.” |
These types overlap. A well-governed research agent might speed up a literature review, maintain a referenced evidence register and present alternatives for an engineer to assess. Do not force a complex agent into a task that a simple script, retrieval search or standard software feature would do more safely.
For the following tables, every example is illustrative, not a claim that a named organisation has implemented it or achieved a stated saving. Measures are suggested evaluation criteria, not promised results.
5. Industry use-case library
5.1 Data analytics, data science, AI and machine learning
Relevant roles: Head of Data Science, Lead Data Engineer, Principal ML Engineer, AI Research Scientist, Analytics Engineering Manager.
| Improvement | Typical senior-level use case | What you could measure | Critical judgement or control |
|---|---|---|---|
| Efficiency | Build a governed assistant to generate first-pass SQL transformations and unit tests from approved schema documentation, reducing repetitive pipeline engineering. | Development and review hours; accepted tests; production defects. | Engineer reviews logic, query performance, access controls and data lineage. |
| Research | Use AI to map competing approaches to time-series forecasting or causal inference, then reproduce shortlisted methods on a common benchmark. | Papers screened; experiments reproduced; baseline-relative performance; research cycle time. | Researcher challenges assumptions, leakage, generalisability and statistical significance. |
| Assistance tool | Create a data-catalogue-grounded analytics assistant that explains metric definitions, permitted joins and known data caveats to analysts. | Verified-answer accuracy; adoption; analyst support requests; unresolved questions. | Restrict access by data entitlement, cite canonical definitions and escalate ambiguous queries. |
| Agent | Orchestrate a monitored agent that detects schema drift, drafts a proposed data-quality change and opens a review ticket without independently changing production tables. | Mean time to detection; true/false alerts; time to triage; rollback incidents. | Human approves schema and production changes; all actions are logged. |
| Evidence / assurance | Automate preparation of model cards, data version manifests, reproducibility checks and evaluation summaries for each release candidate. | Completeness of records; repeatability; missing-evidence rate; review cycle time. | Independent sign-off verifies datasets, subgroup tests and limitations. |
| Reasoning / decision | Run AI-assisted scenario analyses on model accuracy, latency, fairness, infrastructure cost and maintenance burden before choosing a deployment architecture. | Quality of option comparison; forecast-versus-actual cost; post-release performance. | Technical lead weighs trade-offs against product, legal and risk requirements. |
What distinguishes a senior candidate: They can explain why the chosen evaluation was meaningful, what failed, and how they prevented a favourable benchmark from becoming a misleading business claim. NIST evaluation and risk management.
5.2 Clean energy, renewables, electricity networks and storage
Relevant roles: Principal Power Systems Engineer, Energy Research Lead, Battery Systems Engineer, Asset Performance Manager, Renewable Energy Developer.
| Improvement | Typical senior-level use case | What you could measure | Critical judgement or control |
|---|---|---|---|
| Efficiency | Combine weather, asset and historical generation data to shorten the recurring work of producing solar or wind forecast packs. | Preparation hours; forecast error; avoidable manual corrections. | Engineer verifies data quality, seasonal conditions and operational constraints. |
| Research | Assist a battery team in mapping public degradation studies to competing thermal-management hypotheses, with references and methods traceable to the original papers. | Relevant-source coverage; replication success; research time; experiments prioritised. | Scientist checks test conditions, chemistry differences and unsupported extrapolations. |
| Assistance tool | Build a controlled engineering knowledge assistant over approved grid-connection studies, design standards and project lessons learnt. | Time to locate evidence; answer accuracy; onboarding effort; citation completeness. | Version-control source documents; block unsupported advice and preserve design authority. |
| Agent | Use a bounded agent to collect wind-turbine condition-monitoring alerts, request relevant maintenance records and prepare a human-reviewed inspection queue. | Alert precision; triage time; avoided repeat work; missed critical alarms. | No autonomous plant-control or maintenance-deferral decision. |
| Evidence / assurance | Link renewable project assumptions, emissions factors, equipment tests and grid-compliance evidence to the version used in an investment case. | Missing citations; audit preparation time; assumption revision count. | Validate source dates, metering data, calculation units and claims. |
| Reasoning / decision | Compare battery storage sizing options against demand forecasts, price scenarios, degradation, resilience and safety constraints. | Robustness across scenarios; model error; financial sensitivity; decision revisions. | Qualified engineer and investment authority decide; independent models check critical outputs. |
The IEA's *Energy and AI* analysis (2025) and *Modernising Grids in the Age of Electricity* (2026) document AI opportunities in forecasting, maintenance, monitoring and network planning. Those reports also underline the dependence on data quality, recoverable errors and operational safeguards.
5.3 Defence, security engineering and dual-use technology
Relevant roles: Principal Systems Engineer, Defence Research Scientist, Software Assurance Lead, Engineering Programme Director, Secure Data Engineering Lead.
| Improvement | Typical senior-level use case | What you could measure | Critical judgement or control |
|---|---|---|---|
| Efficiency | Within an authorised environment, draft mappings between non-classified programme requirements, design documents and verification activities for engineer review. | Traceability preparation time; missing links found; reviewer rework. | Confirm classification, approved environment, document provenance and system owner approval. |
| Research | Compare published, unclassified research on resilient communications testing or reliability engineering, tagging strength of evidence and gaps. | Source coverage; reproducibility; unsupported claims caught; review effort. | Do not upload controlled technical data; specialists inspect source methods. |
| Assistance tool | Deploy a permissions-aware assistant for approved maintenance procedures and non-sensitive engineering standards, citing exact document revisions. | Correct-source retrieval; technician support time; unsafe answers caught. | Entitlement checks, controlled change process and explicit escalation to authorised personnel. |
| Agent | In a segregated test environment, have an agent assemble authorised regression-test results and flag failed cases for an independent assurance team. | Test-report latency; missed failures; false flags; audit-log completeness. | Agent cannot approve tests, alter acceptance criteria or command operational systems. |
| Evidence / assurance | Produce a reviewed verification matrix connecting equipment requirements to evidence, unresolved anomalies and formal acceptance status. | Evidence coverage; unclosed anomalies; quality-review cycle time. | Engineering authority retains certification, safety and security decisions. |
| Reasoning / decision | Develop a logistics or maintenance resilience options paper comparing spare-part risk, obsolescence, supplier lead time and life-cycle cost. | Assumption sensitivity; supply disruptions anticipated; decision traceability. | Programme leaders validate sources, constraints and security implications. |
The UK's 2026 Defence Sector Skills Needs Assessment explicitly identifies demand for secure AI practice, verification, data stewardship and human judgement. Defence-specific rules, contractual conditions and information classifications take precedence over convenience. None of these examples authorises use of public AI with restricted information or autonomous operational decisions.
5.4 Digital healthcare, medical technology and connected products
Relevant roles: Digital Health Product Director, Clinical Data Scientist, Medical Software Engineering Lead, Human Factors Researcher, Health AI Product Manager.
| Improvement | Typical senior-level use case | What you could measure | Critical judgement or control |
|---|---|---|---|
| Efficiency | Analyse appropriately de-identified, consented product-usability notes to draft themes and testable product improvements for researcher verification. | Thematic coding time; agreement with human coding; themes missed; revision effort. | Protect personal data; assess representativeness and remove unsupported conclusions. |
| Research | Build a reproducible, source-linked evidence map of clinical studies relevant to a device feature, including study design, limitations and conflicting findings. | Search coverage; screening agreement; reference accuracy; time to evidence synthesis. | Clinician/researcher checks eligibility criteria, bias and clinical relevance. |
| Assistance tool | Create a product-support assistant restricted to approved instructions for use, maintenance guidance and escalation processes. | Correct-answer rate; hand-off accuracy; support resolution time; harmful-answer count. | No unapproved diagnosis or treatment advice; route clinical concerns to qualified staff. |
| Agent | Let a monitored agent classify incoming device-quality reports and prepare draft vigilance case files for a trained safety team's review. | Triage time; categorisation agreement; missed serious events; backlog. | Humans determine reportability, causality and actions; secure records and audit trail. |
| Evidence / assurance | Assemble traceable model-validation packages covering intended use, data provenance, performance across relevant patient groups and software versions. | Evidence completeness; subgroup performance; repeatability; review findings. | Clinical safety, quality and regulatory professionals review the claims and limitations. |
| Reasoning / decision | Compare alternative feature releases against clinical benefit, accessibility, model uncertainty, false-alert burden and safety risk. | User/clinical outcomes; false positives and negatives; equity measures; post-release monitoring. | Human product, clinical and regulatory authorities make release decisions. |
Regulatory boundary: Depending on its intended purpose and functionality, healthcare software may qualify as a medical device. The UK's MHRA guidance on software applications explains the regulatory distinction. Compliance and clinical evidence must be assessed for the specific product and market; a demonstration chatbot is not equivalent to a cleared clinical system.
5.5 Automotive, mobility and advanced manufacturing
Relevant roles: Chief Engineer, Senior Vehicle Systems Engineer, ADAS Validation Lead, Battery Research Engineer, Manufacturing Engineering Director.
| Improvement | Typical senior-level use case | What you could measure | Critical judgement or control |
|---|---|---|---|
| Efficiency | Cluster test-track and proving-ground issue logs into likely subsystem themes and draft repeatable defect-triage reports. | Engineering triage hours; duplicate reports; missed critical issues; closure time. | Domain specialist confirms root cause and does not treat correlation as diagnosis. |
| Research | Compare open literature on cell ageing, thermal propagation or lightweight materials to identify evidence gaps before physical testing. | Relevant studies verified; tests avoided or prioritised; hypothesis quality; cycle time. | Engineer checks test boundary conditions and does not extrapolate beyond evidence. |
| Assistance tool | Build a revision-aware assistant for internal system requirements, diagnostic procedures and past lessons learnt, with document citations. | Search time; accepted answers; incorrect-version incidents; new-starter ramp-up. | Configuration management and access rights must match the engineering baseline. |
| Agent | Orchestrate approved, sandboxed simulation batches for design variants, then produce a review queue of outliers and incomplete runs. | Valid runs per engineer-day; compute cost; failure detection; reproducibility. | Engineer approves inputs, boundary conditions, acceptance gates and further physical tests. |
| Evidence / assurance | Generate a traceability view from safety requirements through HIL/SIL tests, calibration versions and unresolved deviations. | Requirements coverage; unreviewed failures; evidence compilation time. | Independent verification; cybersecurity and software-update controls where applicable. |
| Reasoning / decision | Prepare a battery-pack trade-off comparing thermal performance, mass, cost, durability, manufacturability and failure behaviour. | Option sensitivity; prediction-versus-test discrepancy; decision-cycle time. | Chief engineer owns system-level trade-offs and safety margins. |
Automotive engineering has established safety, software-update and cybersecurity requirements. The UNECE WP.29 reference documents include automated-driving validation guidance and UN Regulations 155 and 156. An AI-assisted artefact must fit the relevant approved engineering and assurance process, not bypass it.
5.6 Aerospace, aviation and space systems
Relevant roles: Principal Aerothermal Engineer, Aerospace R&D Lead, Flight-Test Data Engineer, Systems Certification Lead, Software Verification Manager.
| Improvement | Typical senior-level use case | What you could measure | Critical judgement or control |
|---|---|---|---|
| Efficiency | Prepare first-pass reductions of ground-test telemetry and structured anomalies, preserving raw-data references and calculation scripts. | Data-reduction time; reconciled anomalies; rework; discrepancy rate. | Qualified engineer verifies calibration, filtering, units and physical plausibility. |
| Research | Build a cited comparison of public fatigue, creep or high-temperature material studies and map them to a proposed test matrix. | Search completeness; applicability exclusions; experiments improved; review time. | Scientist inspects specimen conditions, uncertainty and validity ranges. |
| Assistance tool | Deploy a controlled design-knowledge assistant referencing approved materials allowables, internal methods and current document revisions. | Source accuracy; retrieval time; incorrect-revision events; user confidence. | No substitution for approved engineering data or design authority. |
| Agent | Use an isolated, permissions-limited agent to run predefined verification checks on non-flight test artefacts and compile exception reports. | Tests reviewed; false negatives; exception handling time; repeatability. | No independent airworthiness sign-off, flight-control authority or unapproved software release. |
| Evidence / assurance | Assemble a draft requirements-to-verification matrix linking test reports, configuration, non-conformances and acceptance evidence. | Missing links; audit findings; evidence retrieval time; unresolved issues. | Formal configuration, independent verification and certification procedures remain in force. |
| Reasoning / decision | Explore thermal, mass, durability and manufacturability trade-offs across engine or airframe design options using AI-assisted scenario comparison. | Model-to-test agreement; sensitivity to assumptions; review quality; rework avoided. | Engineering specialists own physics, margin policy and approval decisions. |
The EASA AI Roadmap 2.0 emphasises a human-centred approach to aviation AI, while EASA's November 2025 regulatory proposal addresses assurance, human factors and ethics. A productivity improvement in an aerospace workflow is not evidence that an AI system is suitable for a safety-critical function.
Reading the six tables by role
| Your position | Strongest contribution to foreground | Evidence an interviewer may probe |
|---|---|---|
| Senior engineer / technical specialist | Better engineering decisions, verified analyses, test quality, time-to-solution. | Boundary conditions, failure modes, comparison with established methods, independent review. |
| Researcher / principal scientist | Better questions, deeper synthesis, reproducible experiments and well-characterised uncertainty. | Source traceability, experimental design, negative findings and methodological rigour. |
| Developer / software / data engineer | Dependable tools, secure automation, adoption, monitoring and maintainability. | Test coverage, failure handling, architecture decisions, operational metrics and costs. |
| Head of function / programme / technical leader | Capacity unlocked, stronger governance, team capability, investment decisions and managed risk. | Team adoption, sustained value, change management, accountability and cost-benefit review. |

6. How to prove an AI contribution
Use the P.R.O.V.E. framework below to prepare a credible example. This is an Eich Dyn coaching structure for organising evidence, not an external accreditation or published industry standard.
| Element | What to record | Questions to answer |
|---|---|---|
| P — Problem and baseline | Task, original process, constraints, time, defects, cost or quality. | What was the difficulty? How did you know it mattered? What was the comparison? |
| R — Responsibility and reasoning | Your role, option selection, decisions and colleagues involved. | Why was AI suitable? What alternatives did you reject? What remained your decision? |
| O — Operation and orchestration | Inputs, models/tools, workflow, permissions, users, integration and operating costs. | What actually ran? What did it and did it not do? Could others use it? |
| V — Verification and safeguards | Benchmarks, independent checks, provenance, error handling, review, privacy and security. | How did you detect bad outputs? What could fail? Who approved it? |
| E — Effect and evidence | Before/after results, net time or cost, quality, adoption, limits and lessons. | What changed? What proof can you show? Was it sustained? |
An evidence register you can maintain
| Field | Example of an appropriate record |
|---|---|
| Workstream and period | “Engineering fault-triage pilot, Q2–Q3” |
| Status | Proposed / trialled / validated / adopted / scaled — select the actual stage. |
| Baseline | Dated sampling method and a representative period or control group. |
| Intervention | Approved tool, data boundary, workflow change and human effort. |
| Outcome | Measured cycle time, quality, research coverage, accepted output or decision quality. |
| Costs | Build time, licence and compute cost, review hours, corrections and maintenance. |
| Assurance | Test set, accuracy checks, sensitivity analysis, audit trail, security and owner approval. |
| Your contribution | Exactly what you designed, decided, implemented, validated or led. |
| Demonstrable artefact | Redacted workflow, approved screenshot, test plan, dashboard, evaluation log or reference. |
| Limitations | Where it failed, where it was not used, and what remains unproven. |
Measure net value, not just gross speed. For example, if drafting becomes quicker but review, rework and integration increase, the headline time saving is misleading. Where feasible, calculate:
Net hours released = baseline total hours − (AI-assisted work + human review + rework + operating overhead)
For a recurring process, also state the observation period, sample size, variation, quality threshold and whether released time was genuinely redirected to valuable work. Avoid presenting one exceptional demonstration as a sustained productivity improvement. For safety or clinical tasks, meeting the quality/safety gate is a precondition, not a benefit you can trade away for speed.

7. How to discuss AI in interviews and promotions
Turn a generic statement into credible evidence
| Weak statement | Stronger, evidence-ready framing |
|---|---|
| “I use ChatGPT to speed up my work.” | “I selected a recurring engineering task, established a baseline, tested an AI-assisted method and compared the net processing and review effort before deciding whether to adopt it.” |
| “I used AI for research.” | “I used AI to expand the initial literature search, then checked original sources, assessed conflicting evidence and designed follow-up experiments around the gaps.” |
| “I built an AI agent.” | “I developed a bounded workflow with defined data access, audit logs and human approval. We tested error cases before using it and monitored how often it needed intervention.” |
| “AI identified the best design.” | “AI helped us explore options. I challenged the assumptions and compared them with validated physics, tests and risk thresholds before recommending a design.” |
A 90-second interview answer: use this structure
“We had a recurring [business or engineering problem]. Its original baseline was [measured effort, delay or quality issue]. I was accountable for [your responsibility]. I tested [AI-enabled method] because [reasoned choice], with [specific verification and information safeguards]. The result over [time period and sample] was [validated outcome], after accounting for [review and operating costs]. My judgement was most important when [trade-off, exception or difficult decision]. We then [adopted, restricted, revised or rejected] the approach.”
If the result is still a trial, say so. A strong answer can be about rejecting an unsafe or ineffective deployment after sound evaluation. **Senior judgement includes knowing when not to use AI.**
CV, LinkedIn and promotion examples
Adapt these structures only when they truthfully describe your own contribution:
- CV achievement: “Led an AI-assisted [workflow] pilot across [scope], reducing net [process measure] by [verified amount] over [period], while maintaining [quality/safety gate] and introducing [review/control].”
- Research achievement: “Designed a traceable AI-supported evidence review and experimental prioritisation process, covering [sources/experiments], with [independent checks] and [resulting decision].”
- Leadership / promotion evidence: “Established governance and team training for [AI-supported process]; monitored [adoption, exception rate, quality and value], and redeployed capacity towards [higher-value work].”
Eight questions to rehearse
- What important problem did you choose to improve, and why?
- Why did AI add value over conventional automation or a better manual process?
- What exactly did you contribute versus the tool and your colleagues?
- What was the baseline, and how was improvement measured?
- What were the failure modes, and how did you find incorrect outputs?
- How did you protect confidential information, intellectual property and personal data?
- What decision remained human, and what contrary evidence did you consider?
- What happened after the pilot — adoption, monitoring, scaling, redesign or rejection?
An informal readiness scale — not a hiring prediction
| Level | Evidence available | Coaching priority |
|---|---|---|
| 0 — Awareness | Knows AI terminology but has no relevant example. | Identify one appropriate work problem. |
| 1 — Practitioner | Uses an approved tool on individual tasks. | Record quality checks and a baseline. |
| 2 — Experimenter | Has a bounded pilot and early comparison data. | Improve evaluation and articulate personal judgement. |
| 3 — Proven contributor | Can show a validated outcome, costs, controls and lessons. | Prepare a concise interview story and supporting artefact. |
| 4 — Leader / scaler | Has led adoption, risk controls and sustained team-level value. | Connect the result to strategy, capability development and organisational impact. |
This scale is a self-assessment aid devised for this guide; it is not a validated psychometric score, industry benchmark or employer selection criterion. An excellent senior specialist may demonstrate Level 3 in a narrow high-risk task more convincingly than a poorly controlled Level 4 claim.

8. Your 90-day AI evidence-building plan
| Period | Action | Tangible output | Gate before proceeding |
|---|---|---|---|
| Days 1–15: Select | Identify three recurring problems; score each for business importance, data sensitivity, feasibility and measurability. Select one bounded candidate. | Problem statement, accountable owner and baseline plan. | Use is permitted; purpose, data and decision boundary are clear. |
| Days 16–30: Baseline | Measure current performance and define quality, safety, security and acceptance criteria before applying AI. | Baseline log, evaluation set and risk record. | Relevant stakeholders approve the comparison and controls. |
| Days 31–60: Pilot | Build or configure the smallest workable assistant, analytical workflow or agent; evaluate representative and adverse cases. | Pilot demonstration, test results, costs and exception log. | Any critical failure blocks deployment; revise or stop. |
| Days 61–75: Validate | Compare against baseline, have a colleague review results and quantify net effects. | Before/after evidence and limitations, with named sign-off. | Claims are supported and do not exceed the sample or use case. |
| Days 76–90: Communicate | Decide whether to adopt, extend or reject; prepare a redacted one-page case study and a two-minute interview answer. | P.R.O.V.E. case, CV bullet and promotion evidence. | You have permission to disclose the example, and no confidential details are exposed. |
For professionals between roles: Use a public dataset, permitted open-source repository or fully synthetic engineering scenario. Explicitly label it portfolio demonstration, not an employer deployment. You can still show excellent problem framing, reproducible methods, testing and judgement without inventing commercial outcomes.

9. What good judgement looks like
AI should make skilled professionals more capable and better informed — not less accountable. The cross-sector NIST AI Risk Management Framework calls for testing, documentation, ongoing monitoring and consideration of limitations, while the UK Government AI Playbook stresses proportionate controls and meaningful human oversight.
Apply these six checks to every case study:
- Permission and data boundaries: Did the organisation allow this AI system and this data? Were access rights, intellectual property, personal information and contractual restrictions respected?
- Evidence integrity: Were important claims checked against primary documents, raw data, repeatable calculations or independent tests?
- Human decision authority: Who could review, override, halt, reject or approve the work, particularly for safety- or rights-affecting decisions?
- Robustness: What happened with incomplete information, unusual operating conditions, model mistakes and changing data?
- Proportionate value: Was the net gain meaningful after licence cost, computing, engineering review, maintenance and residual risk?
- Honest attribution: Did you distinguish your contribution, your team's work, the AI output and any unrelated process redesign?
Red flags that weaken a senior candidate's credibility
- Giving an inflated “percentage productivity gain” without explaining the baseline, sample or verification.
- Equating prompt quality with engineering, scientific or clinical validity.
- Claiming an agent is “autonomous” while concealing manual intervention, exceptions or unapproved permissions.
- Presenting generated citations, unsupported numbers or synthetic examples as real project evidence.
- Sharing identifiable, classified, confidential or proprietary information in a portfolio or with an unapproved AI provider.
- Treating AI deployment itself as success when the wiser outcome may have been to improve the process, use conventional automation or stop the pilot.
Final message: At a promotion panel or an interview, your competitive advantage is not that you can use AI. It is that you can choose a worthwhile problem, combine AI with domain expertise, demonstrate a trustworthy outcome, and take responsibility for the judgement behind it.
A final coaching exercise
Before your next interview or promotion discussion, complete these three sentences:
- “The most important problem I improved with AI was…”
- “The evidence of value — including the checks and limitations — is…”
- “The judgement that only I or my team could responsibly provide was…”
If these answers are specific, measurable and defensible, you are no longer merely declaring AI literacy. You are demonstrating professional impact.
FAQ
Is "I use AI" still a strong enough answer in a technical interview or promotion discussion?
No. "I use AI" describes an activity, not a capability. Employers increasingly want a concrete example: the problem you chose, why AI was an appropriate solution, what improved, what you checked, and which decisions required your own professional judgement.
What are the six types of AI value employers can assess?
Efficiency and throughput; research and discovery; assistance tools; agents and workflow orchestration; evidence, quality and assurance; and reasoning and decision support. The strongest examples combine technical skill with problem selection, adoption, evaluation and human accountability.
How do I prove an AI contribution rather than just claim it?
Use the P.R.O.V.E. structure: Problem and baseline, Responsibility and reasoning, Operation and orchestration, Verification and safeguards, and Effect and evidence. A credible claim needs a measured baseline, net results after review and operating costs, and an honest statement of limitations.
What if my AI project is only a pilot, or was rejected?
Say so. Where value has not yet been measured, call it a pilot or a hypothesis. A strong senior answer can be about rejecting an unsafe or ineffective deployment after sound evaluation — good judgement includes knowing when not to use AI.
Does AI evidence matter differently in regulated sectors such as healthcare, defence, automotive or aerospace?
Yes. In regulated sectors, traceability, controlled data, validation and meaningful human oversight may matter more than raw speed, and sector rules, information classifications and approved engineering processes take precedence over convenience.
10. Sources and evidence notes
The references below support the direction of change, sector context and governance principles. The 36 use cases in this guide are author-designed illustrative applications, not observed case studies from these sources. No illustrative metric is presented as an achieved industry result.
| Source | Date | Relevance |
|---|---|---|
| Anthropic — *How employment is changing at Anthropic* | 16 Oct 2026 | Primary internal study of hiring language, work, AI-agent use and mobility at one AI-intensive company. |
| LinkedIn — *Skills on the Rise in 2025* | 26 Mar 2025 | AI literacy and related skill trends; platform-specific analysis. |
| World Economic Forum — *Future of Jobs Report 2025*, Skills Outlook | 2025 | Survey-based expectations for AI/big-data, analytical thinking and leadership skills. |
| Microsoft — *2025 Work Trend Index* | 23 Apr 2025 | Global survey and company telemetry about human–AI/agent work; not audited cross-industry deployment rates. |
| NIST — AI Risk Management Framework: Core | Framework resource | Measurement, validation, uncertainty, safety and accountability. |
| NIST — Generative AI Profile, NIST AI 600-1 | 26 Jul 2024, subsequently updated | Generative-AI-specific risks and evaluation considerations. |
| UK Government — AI Playbook | 10 Feb 2025 | Human control, data protection, assurance and accountability. |
| International Energy Agency — *Energy and AI* | 2025 | Opportunities and limits in energy-system optimisation, maintenance and forecasting. |
| International Energy Agency — *Modernising Grids in the Age of Electricity*, AI-enhanced solutions | 21 Sep 2026 | Grid forecasting, sensing, prioritisation and risk-aware adoption. |
| Skills England — *Sector Skills Needs Assessment: Defence* | 6 Oct 2026 | UK defence AI skills, model validation, security, assurance and human judgement. |
| MHRA — *Medical devices: software applications* | Current guidance, accessed Oct 2026 | UK context for software that may qualify as a medical device. |
| UNECE — WP.29 reference documents | Ongoing | Automotive safety-validation, cybersecurity and software-update reference material. |
| EASA — *Artificial Intelligence Roadmap* | Roadmap 2.0, 2023; programme updates | Human-centred approach and assurance context in aviation. |
| EASA — Regulatory proposal on AI in aviation | 10 Nov 2025 | Developing aviation assurance, human-factors and ethics guidance. |
Evidence interpretation and date: Prepared on 24 October 2026 using sources available at that date. Anthropic's figures are internal observational findings from a rapidly growing US AI company; differences in hiring mix, firm growth, systems and methods limit causal and external conclusions. Other surveys report respondent views and expectations, not guaranteed employer behaviour. Sector guidance should be checked for subsequent revisions before deployment or publication, particularly for regulated activity.
About Eich Dyn: This educational guide supports preparation for career progression and technical leadership discussions. It is not legal, regulatory, safety-certification or clinical advice. Visit Eich Dyn for Career OS™ coaching and resources.
© 2026 Dai Jones / Eich Dyn.
Related reading
Preparing for a panel? How to Demonstrate AI Impact in Your Next Interview turns this evidence into a practical 90-second answer, with three illustrative examples and a preparation checklist.
Career OS™ MOVE Guidebook
The external-move pathway: direction, positioning, evidence, search, interviews and offer decisions — the sequence your AI evidence portfolio plugs into.
Read →Career OS™ PROPEL Guidebook
For internal progression: role positioning, visible outcomes, influence and promotion leverage inside your current organisation.
Read →Interview Consultation for Engineering Managers
Structured preparation for senior technical interviews, including evidence-led answers like the 90-second structure in this guide.
Read →UK Engineering Jobs 2026–2028
Where demand is moving across clean energy, defence and AI — the market context behind the six industry tables.
Read →
