Role-to-Topic Preparation Map

Compile the role before studying

A job description is neither a complete curriculum nor a keyword list. It is a noisy statement of outcomes, constraints, and organizational anxieties. Your first task is to turn each sentence into an interviewable capability.

Parse five kinds of signal

Make requirements atomic

“Build reliable AI-enabled enterprise integrations” hides at least eight probes: authentication, webhook verification, idempotency, event ordering, tenant isolation, AI evaluation, observability, and rollout. Split it. For each atomic requirement, record one of four evidence states:

• Demonstrated: a real project and artifact can be explained.
• Practised: a sandbox artifact can be shown, clearly labeled as practice.
• Conceptual: trade-offs are understood but implementation evidence is absent.
• Unknown: neither understanding nor evidence is ready.

Live role status snapshot

The supplied syllabus was prepared from selected official pages on 2026-08-03. The following direct checks were repeated on 2026-08-04. “Active” means the official page exposes a named role and application path. “Changed” means the source remains useful but its URL or target role family has moved. “Unavailable” means the supplied role cannot be verified as an open posting; do not prepare or apply as though it were live.

Choose the correct preparation lane

Use the common foundation—production AI, evaluation, backend reliability, security, and communication—but change the center of gravity. The point is not to imitate the job description. It is to surface the most relevant evidence you actually have.

Qdrant FDE: search depth in a customer room

Emphasize: dense/sparse/hybrid retrieval, HNSW, filters and payload indexes, quantization, relevance metrics, capacity, Kubernetes, migration from another search system, and workshop facilitation. Proof: one Qdrant benchmark with a golden set, recall/quality and p95 latency, plus a deployment and rollback diagram. Likely probe: a customer’s filtered search is slow and relevance degraded after migration—how do you isolate data, query, index, resource, and evaluation causes?

Remote FDE: complete enterprise delivery

Emphasize: discovery, APIs, OAuth/service accounts, webhooks, event delivery, idempotency, messy data, RAG/agents, evaluation, multi-tenancy, observability, change management, and reusable patterns. Proof: an enterprise connector and customer reference architecture with definition of done, threat model, golden set, rollout, and reconciliation. Likely probe: turn an imprecise HR or payroll workflow into a secure production plan and show how success will be measured.

Sourcegraph IC4: opinionated agent engineering

Emphasize: multi-step agent reliability, code retrieval and context packing, eval pragmatism, model selection, caching/distillation decisions, cost/latency budgets, technical direction, mentoring, and stack adaptability. The live application asks for hands-on coding-agent experience and where deterministic code or human judgment belongs. Proof: a traceable multi-step code agent, targeted evals, a cost/latency profile, and a two-minute point of view grounded in a real failure.

Canonical alliances architect: breadth with a workshop spine

Emphasize: Linux troubleshooting, DNS/TCP/TLS, Kubernetes, OpenStack, storage, cloud primitives, automation, PostgreSQL/Kafka/NGINX integration, reference architectures, and partner enablement. Proof: a hybrid-cloud reference architecture and a ten-minute workshop segment that explains failure, operations, and cost to mixed audiences. Likely probe: discover a partner environment, make an architecture defensible, and respond thoughtfully when asked outside your deepest specialty.

Supabase AI Platform Engineer: governed internal agents

The current role is a much sharper target than the syllabus’s generic Supabase row. Emphasize: event-triggered execution, durable state, human review, atomic rollback, full run logs, golden suites, CI gates, permission-enforced risk tiers, Python/GCP/infrastructure as code, MCP/API integrations, and value instrumentation. Proof: a registered-agent platform slice in which a forbidden write is impossible at the credential or tool-schema layer, not merely prohibited in a prompt.

Supabase PostgreSQL alternatives: do not confuse adjacency with fit

The active Postgres Engineer role asks for deep internals, extensions in C and Rust, planner/executor/storage mechanics, WAL/MVCC, managed deployment troubleshooting, and large-scale idempotent rollouts. General PostgreSQL, RLS, and pgvector preparation is not equivalent. Mark such requirements honestly as demonstrated, practised, conceptual, or unknown.

Automattic and Deel: preserve signals, discard stale assumptions

The unavailable Automattic posting remains a useful historical prompt for product-first AI, user-facing scale, full-stack breadth, written application quality, and accountable AI-assisted coding. The unavailable Deel posting historically emphasized Node.js, PostgreSQL, AI API integration, ETL, messy data, and document parsing. Do not quote old eligibility, tenure, salary, or location terms as current facts. If a new role appears, recompile it from zero.

Build one evidence pack, then change the lens

A credible evidence pack is a connected body of work, not eight unrelated toy repositories. One enterprise AI system can yield search, evaluation, agent, integration, reliability, security, architecture, and leadership views.

Score gaps by expected interview loss

Use priority = probability of probe × consequence of weakness × improvement per hour. The arithmetic is a forcing function, not scientific precision. A missing must-have with a likely live exercise ranks above an attractive adjacent technology. Eligibility failures rank before preparation: no amount of study fixes an impossible location or schedule constraint.

Numbers without invention

For every real story, prepare the measurement definition, source, time window, baseline, and your contribution. Useful dimensions include corpus or event volume, active users/tenants, quality by slice, p50/p95/p99 latency, cost per successful task, error or duplicate rate, recovery time, delivery lead time, adoption, and customer outcome. If the source metric is inaccessible, use a bounded qualitative statement. Do not convert a hypothetical benchmark into career history.

Run a 48-hour application sprint

Once an active role passes eligibility, stop browsing broadly. Produce a role-specific packet with explicit time boxes.

1. Hour 0–1 — capture: save the official URL, check date, title, location, application fields, hiring stages, and the exact text of consequential requirements.
2. Hour 1–2 — compile: split requirements, label must/preferred/context, assign evidence state, and predict interview formats.
3. Hour 2–4 — select: choose three artifacts and four stories; link every selection to a requirement. Drop weak or duplicative material.
4. Hour 4–6 — tailor: reorder resume bullets and portfolio links without changing facts. Mirror the employer’s problem language only where it accurately describes the work.
5. Hour 6–8 — close one gap: practise the highest-value missing drill: a Qdrant diagnosis, FDE discovery, agent eval, Linux troubleshooting, or governance design.
6. Hour 8–10 — simulate: run a resume deep dive, role-specific technical question, architecture case, and concise written response.
7. Before submission — verify: re-open the page, eligibility, requested format, and AI-use policy. Answer application questions in your own voice and obey any explicit restrictions.

The one-page role brief

Role / official URL / checked date / status:
Eligibility: location, overlap, travel, employment constraints
Top outcomes: 1 / 2 / 3
Must-have capabilities:
Three proof artifacts:
Four stories:
Likely technical and behavioral exercises:
Red gaps and honest framing:
Questions for the interviewer:

Syllabus checkpoint: prepare the numbers behind every role story

For each selected artifact or employment story, prepare a disclosure-safe evidence sheet covering data volume, user and tenant scale, quality change, latency before and after, cost change, reliability or failure-rate change, delivery time, team/stakeholder scope, and customer impact. Record the metric definition, baseline, time window, source, attribution, and confidence. If a dimension was not measured, say so and describe what evidence exists; never fill a blank with a plausible number.

These numbers should remain consistent across resume, application form, recruiter screen, portfolio, and technical loop. Rehearse both an executive statement (“what changed and why it mattered”) and an engineering drill-down (“how measured, what else changed, what failed, and what your contribution was”).

Interview playbook

Answer role-fit questions by joining role evidence to personal evidence without pretending they are identical.

Requirement → Evidence → Judgment → Relevance → Gap

1. Requirement: paraphrase the employer’s real outcome.
2. Evidence: give one truthful project, artifact, or practice example.
3. Judgment: explain the consequential trade-off or failure handled.
4. Relevance: connect it specifically to this environment.
5. Gap: name any meaningful difference and how you would de-risk it.

Role-specific openings

• Qdrant: lead with relevance and performance evidence, then customer delivery.
• Remote: lead with an ambiguous enterprise outcome owned through rollout.
• Sourcegraph: lead with an opinionated agent decision backed by eval, cost, and failure evidence.
• Canonical: lead with breadth, troubleshooting method, and workshop clarity.
• Supabase AI: lead with runtime/evaluation/governance mechanisms, especially structurally enforced permissions.

Common traps

• Keyword recitation with no project decision or artifact.
• Describing a closed role as active because a cached search result still exists.
• Hiding a stack, tenure, location, or schedule gap until late in the process.
• Changing claims between resume, application form, and interview.
• Preparing every target equally and becoming shallow in all of them.

Question bank

These questions test whether targeting is evidence-based rather than cosmetic.

Proof artifact: the live role compiler

Create a versioned dossier for one active role. It should let another reviewer reproduce why you prioritized certain preparation and whether every application claim is supported.

Steps

1. Capture the official posting as a dated PDF or text snapshot for personal analysis, respecting site terms; record the live URL and check time.
2. Extract atomic requirements into a spreadsheet or Markdown file. Tag outcome/domain/context/behavior/eligibility, must/preferred, and evidence state.
3. Link three artifacts and four stories. For each, record exact personal action, source of any metric, disclosure boundary, and one gap.
4. Generate a one-page role brief, six likely technical probes, three questions for the employer, and a 48-hour preparation queue.
5. Have a reviewer compare resume, application answers, dossier, and spoken story for consistency.

Metrics

• 100% of hard eligibility items explicitly resolved as pass, fail, or recruiter question.
• Every must-have mapped to evidence state; no unmarked blanks.
• At least three high-probability requirements supported by inspectable artifacts.
• Every quantitative claim has source, definition, time window, and attribution note.
• A reviewer can explain the top preparation priority and why in under two minutes.

Deliberate failure injection

Replace the saved posting with a closed-role shell, change a location requirement, and insert one unsupported resume claim. Your workflow should flag missing posting metadata, invalidate the prior eligibility decision, and fail the evidence audit. Then simulate a renamed role with the same URL and require a fresh diff rather than silently trusting the old brief.

What to present

Show the dated source register, requirement matrix, evidence links, one-page brief, change diff, and audit result. In an interview, present only your own evidence—not the internal scoring machinery—unless asked how you prepared.

Chapter review

Targeting is disciplined selectivity. Verify the opening, gate eligibility, translate verbs into capabilities, connect truthful evidence, and spend preparation time where it changes likely interview performance.

Glossary

Atomic requirement

One independently assessable capability or constraint extracted from a broader sentence.

Evidence state

Demonstrated, practised, conceptual, or unknown readiness for a requirement.

Eligibility gate

A location, schedule, legal, travel, or hard-experience condition evaluated before deep preparation.

Role compiler

The process that converts a live job description into evidence, gaps, interview hypotheses, and actions.

Historical signal

A useful topic from a closed or changed role that must not be represented as a current requirement.

Evidence provenance

The source, definition, time window, and attribution behind a claim.

Mastery checklist

• I verify title, description, location, and application path—not merely HTTP status.
• I can compile a role into atomic outcomes, depth, context, behavior, and eligibility.
• I know which of the seven syllabus sources are active, changed, or unavailable as of the check date.
• I can name the three strongest artifacts and four stories for my primary active target.
• I distinguish production evidence, sandbox practice, conceptual knowledge, and unknowns.
• I can state stack, tenure, location, travel, and schedule gaps without distortion.
• I re-check the official page and application instructions immediately before submission.