AI SKILLS BY ROLE

AI skills for software engineers

Most engineers now write code with an AI assistant. Speed is no longer the signal. What matters is whether they read what the AI wrote, test the edge cases it skipped and notice when a suggestion is plausible, compiles and is still wrong.

How AI shows up in the work

Where software engineers use AI every day, and where it goes wrong.

01

Writing code

Generating functions, tests and boilerplate. The risk is code that passes the happy path and fails in production.

02

Reviewing and debugging

Explaining unfamiliar code and proposing fixes. AI often fixes the symptom, not the cause.

03

Design and trade-offs

Exploring approaches and libraries. Strong engineers check versions, licences and whether the API really exists.

What strong AI use looks like

The habits that separate a capable software engineer from one who copies the answer.

Interview questions that test AI skills

Ask for a specific example each time. Vague answers are a signal in themselves.

  1. 01
    Tell me about a bug an AI assistant introduced into your code. How did you find it?What it reveals: Real experience and verification habits.
  2. 02
    How do you review an AI-generated pull request from a teammate?What it reveals: Standards for code they did not write.
  3. 03
    When do you turn the assistant off?What it reveals: Judgment about where AI slows thinking down.
  4. 04
    The AI suggests a library function you have not seen. What do you do before using it?What it reveals: Checking for hallucinated or deprecated APIs.
  5. 05
    An AI fix makes the failing test pass. How do you know the bug is really fixed?What it reveals: Root-cause reasoning.
  6. 06
    What would you never paste into an AI assistant?What it reveals: Security awareness: secrets, customer data, proprietary code policies.
  7. 07
    How do you make sure tests written by AI actually test something?What it reveals: Critical thinking about coverage.
  8. 08
    Explain a design decision in your last project that you made against the AI's suggestion.What it reveals: Ownership and independent reasoning.

A sample task with an AI mistake to catch

Questions show what candidates say. A task shows what they do when the AI is confidently wrong.

The situation

A payments endpoint occasionally charges customers twice. The AI colleague proposes adding a retry with a longer timeout and says the issue is network latency.

What the AI got wrong

Retries make it worse: the endpoint is not idempotent, so a slow response followed by a retry creates a second charge.

What a strong candidate does

Asks what happens when the first call succeeds slowly, spots the missing idempotency key and proposes it instead of the retry.

Red flags

Signs a candidate depends on AI rather than working with it.

Answerr measures this for you.

These tools are free. Our main work is measuring how well people work with AI, so employers can hire on evidence and teams can build the skill. Hiring? See AI interview questions by role.

01

AI capability

How well a person works with AI on real work, measured across Judgment, Reasoning, Critical thinking, Questioning and Adaptability.

What AI capability is
02

AI in hiring

Candidates work a real task from the role alongside Marcus, an AI colleague who is sometimes wrong. You see who checked, who questioned and who just accepted.

Try the hiring demo
03

AIQ™

A verifiable score for how you work with AI, with the evidence behind every rating. Teams use it to measure and build AI capability. Your first one is free.

How AIQ is measured

Questions, answered.

Using AI assistants to write, test and review code while reading what they produce, testing edge cases, verifying suggested APIs and owning the design decisions.

See how your software engineer candidates work with AI.

Each candidate works a task from your role alongside an AI colleague. You get an AIQ™ score with the evidence behind every rating.