No-fluff playbooks for technical analysts.
Would you rather follow an order?
The list below is newest first. These are ordered, so you can start at part one and work up.
Use agentic coding tools as an analyst who codes: plan mode, permission modes, AGENTS.md and CLAUDE.md, hooks, worktrees, and four jobs with the guardrails.
The observability requirements an analyst writes for a payment API: golden signals, SLOs and error budgets, log fields, metrics, alerts, and Gherkin checks.
Load test a payments API with Grafana k6 v2: write the NFR first, then scenarios, thresholds, and checks, safe idempotency keys, test types, and a CI run.
The Arazzo Specification for analysts: sourceDescriptions, steps, successCriteria, and runtime expressions, with a Stripe payment-to-refund workflow to run.
How to read and review an AsyncAPI 3.0 contract for Kafka: channels, operations, messages, bindings, keys, ordering, and schema registry compatibility.
Payments Canada for analysts: Lynx on ISO 20022, the ACSS batch system, the Real-Time Rail's Q4 2026 launch plan, RPAA supervision, and bilingual data traps.
How CBPR+ replaces MT 199 queries and MT 192 recalls: camt.110 and camt.111 investigations, camt.056 and camt.029, Case Management, dates, and tests.
FedNow vs RTP for analysts: ISO 20022 messages, the $10 million limits, settlement, request for payment, fraud controls, and the test cases that matter.
Regulation (EU) 2023/1113, the EU travel rule: required payer and payee data, the pacs.008 fields that carry it, missing information handling, crypto, tests.
How analysts write LLM evals: a golden set from acceptance criteria, code graders vs LLM-as-judge, pass thresholds as release criteria, and regression in CI.
Moving interbank MT101 to CBPR+ pain.001 under the Payment Initiation Relay rulebook: the deferred dates, MT101 to pain.001 mapping, addresses, and test cases.
MT940/950 to camt.053, MT942 to camt.052, MT900/910 to camt.054: the Nov 2027 and Nov 2028 CBPR+ dates, field mapping, reconciliation impact, and a test plan.
Open banking APIs for bank analysts: AIS vs PIS, the consent lifecycle, SCA, FAPI 2.0, PSD3, UK, US 1033, and Canada status, plus the test cases that matter.
What changed from OpenAPI 3.0 to 3.1 and 3.2, from nullable to type arrays, webhooks, QUERY and streaming, and what to check when a provider upgrades.
Read OpenTelemetry traces like an analyst: spans, attributes, the traceparent header, trace_id vs UETR, and finding the slow span in Jaeger, Tempo, or Datadog.
Payment hub architecture for analysts: channels, canonical model, validation, screening, routing to SEPA, Instant, CBPR+ and RTGS, repair queues, and booking.
Postman CLI vs Newman in CI: install and run commands, JUnit reports, spec linting, where results go, GitHub Actions YAML, and the git-native Bruno CLI.
Fuzz an API from its OpenAPI contract with Schemathesis 4: run command, checks, negative and stateful tests, JUnit in CI, and triaging findings into defects.
SEPA Direct Debit Core and B2B for analysts: mandates, pain.008 and pacs.003, sequence types, D-1 timelines, R-transactions, reason codes, and a test matrix.
How to specify an MCP server for your own API: which operations become tools, schemas, OAuth scopes, approval for writes, audit, injection risk, and tests.
How the SWIFT gpi Tracker works for analysts: the UETR, ACSP with G000 to G004, ACCC and RJCT, the update channels and API, Stop and Recall, and what to test.
UK Faster Payments for analysts: ISO 20022 status, what replaced the NPA, Confirmation of Payee, and the PSR's APP fraud reimbursement rules as data and tests.
How analysts use AI to onboard faster: check the approved tool first, then build a glossary, grounded message explainers, session notes, and a questions list.
A 90 day onboarding plan for technical analysts in four phases: orient, map, contribute, own. What to produce each week, with a banking ISO 20022 example.
How a new analyst asks better questions: map who knows what, run first-week 1:1s, use the checked-X-think-Z format, batch questions, and keep a questions log.
How a business analyst onboards in a new team: map stakeholders, walk the as-is process, learn the business vocabulary, and unblock one real decision by day 60.
Developer analyst onboarding: week one access, reading the repo with AI, tracing a pain.001 by its identifiers through logs and SQL, and a root cause note.
How a functional analyst onboards: read the spec against the usage guideline and real messages, build a rules inventory, and ship one corrected mapping row.
How a new analyst gives useful feedback: keep an observation log, raise risk now and the rest at day 30, use evidence and SBI, and share drafts at 30%.
How an analyst runs a 90 day onboarding review: a scored self-assessment, the evidence to bring, a retrospective, and the guide you leave the next joiner.
How a QA analyst onboards: map the environments, inventory test data, read the inherited suite for real coverage, and name three gaps before the next release.
How a new analyst reads a team's documentation: the reading order, a trust register, checking pages against code, logs, and data, and Confluence search tactics.
Systems analyst onboarding: follow one payment across channel, hub, screening, gateway, and ledger, then build the context diagram and interface catalogue.
Restarting an analyst career in Canada, the UK, the EU, or the US: why the first role is often a level down, how local proof wins it back, and pay per market.
Every analyst career move on one map: switching in, going more or less technical, moving up, and earning more, with timelines, pay deltas, and real cases.
Analyst contract rates in 2026 for the US, Canada, UK, and eurozone, the structures (1099, CCPC, IR35, portage), and the floor-rate math behind real take-home.
Rewrite your CV for an analyst role change: bullets as artifact plus outcome plus number, before and after pairs, ATS rules, and CV norms in four markets.
How employer type shapes analyst pay: banks, Big Four and boutique consultancies, outsourcers, SaaS, fintech, and public sector on pay, bonus, and security.
A 60 day plan for analysts after a layoff or career break: explain the gap in one sentence, refresh skills, reconnect, bridge with a contract, hold your pay.
Head of business analysis or principal analyst? What each does all day, pay in four markets, how to trial management, and how to create a principal track.
How to build an analyst portfolio when your real work is confidential: 3 to 5 pieces, public or synthetic data, the right pieces per role, and a 5 minute pitch.
Realistic 2026 analyst pay by role and level in the US, Canada, UK, and Eurozone: BA, technical BA, QA, SDET, data, architecture, product, and contract rates.
How analysts negotiate an offer or a raise: word-for-word scripts, an evidence file with numbers, timing, non-salary items, and US, Canada, UK, and EU norms.
How analysts become analytics engineers: dbt, SQL, Git, tests, and modelling in 6 to 12 months, realistic 2026 pay in four markets, and a portfolio spec.
Technical analyst to forward deployed engineer, solutions engineer, or implementation consultant: what each does, 2026 pay, skills that transfer, and the gap.
Technical analyst to software developer in 2026: junior hiring is tight and AI compresses junior coding, so go internal and use your domain. Pay, plan, cases.
Senior systems analyst to solutions architect pays 15 to 25 percent more, usually after 8 to 12 years. The ADRs, NFRs, cloud cert, and design reviews it takes.
Is business analysis safe from AI? Which BA tasks AI already does, which it cannot, the roles most exposed, and the five career moves that hedge, with 2026 pay.
Which analyst certifications are worth it in 2026: CBAP, CCBA, ISTQB, PSPO, SAFe, cloud, data, and domain credentials ranked by career return for each role.
BA to delivery manager, project manager, or scrum master: what transfers, what is new, pay in four markets, and why delivery manager is the durable target.
Most BAs reach product manager through product owner. What changes, what it pays in four markets, the skills to add, and a six month plan with artifacts.
A business analyst career change at 40 or 50 works when you target your own domain and enter at mid band: the roles that value experience, ageism, and money.
Switching into business analysis from teaching, nursing, retail, or support: the real timeline, first-role pay by country, the pay cut, and the tech kit.
Data analyst to business analyst: what transfers, what you must learn, realistic 2026 pay in four markets, three composite cases, and a six month plan.
Moving from software developer to business analyst: the real pay cut, why technical BA or systems analyst is the better target, what transfers, and a plan.
The domains that pay business analysts most in 2026, from payments and capital markets to ERP and healthcare IT: why each pays, the premium, how to break in.
How to become a technical business analyst: SQL, APIs, logs, and scripting in six months on your project, one artifact a month, and a 10 to 20 percent pay jump.
An internal move is the cheapest analyst career change: 3 to 9 months, usually no pay cut. The step plan, the move proposal, and how to ask for a regrade.
How career changers pass analyst interviews: scripts for why the switch and no experience, the seven common case exercises, STAR stories, and the pay question.
What changes from junior to mid, senior, and lead business analyst: scope, trust, the artifacts that prove each level, 2026 pay bands, and a promotion case.
Less technical roles for analysts, developers, and QA: business architect, change lead, consultant. Pay in four markets, who each suits, and how to pivot.
How to move from operations, production support, or the service desk into a business analyst or technical BA role: what transfers, the plan, and real pay.
Project manager to business analyst, or BA to PM: what each role owns, what each must learn, pay at the same level, signs of the wrong seat, and real cases.
Manual QA to SDET pays 25 to 40 percent more at the same level. The stack to learn, a 6 to 12 month plan with artifacts, the AI angle, and three real moves.
How QA testers become business analysts: what transfers, the elicitation and scope gap, a six month plan, real cases, and the typical 10 to 25 percent raise.
Proactive developers find the problem before the ticket and coach juniors who generate more than they can judge. The habits, templates, and formats that work.
When AI generates code in seconds, a developer's value moves to proving it works: testing, review, quality, release notes, demos, proactivity, and coaching.
AI writes tests that mirror the code, bugs included. Derive tests from the requirement, add property and contract tests, prove the suite with mutation testing.
How developers write release notes per audience and run demos that end in a decision, with templates, a worked payments example, and where AI drafting helps.
Reviewing AI-generated code: the failure modes to hunt for, the review order that finds them, what CI should automate, and a PR template that makes it fast.
Stripe's PaymentIntents API scored on a 12-check contract review: 22 of 24, plus the idempotency, webhook, versioning, and lifecycle findings teams must own.
How analysts use AI to draw and maintain Mermaid, BPMN, and sequence diagrams: the context pack, the house style file, the review loop, and the git workflow.
Run a requirements workshop with an AI note taker: generate the agenda from the system, drive a question bank, and diff the transcript against the spec.
How to read a diagram you were handed with AI: extract actors, flows and rules, find the missing branches, and reconcile the picture with contract and code.
A repeatable review that finds edge cases missing from your specification: nine lenses, one prompt each, run as a script before requirements are signed off.
How analysts use AI to produce real BPMN 2.0 XML, not flowchart approximations: the element subset that matters, the prompt, validation, and maintenance.
Generate a Mermaid sequence diagram from a Bruno or Postman collection run: the trace script, the Postman CLI or newman JSON export, the prompt, and CI wiring.
Turn manual Kafka checks into an automated Postman collection: produce and consume over REST Proxy, poll with backoff, assert schema and ordering, run in CI.
Wire an assistant to Jira, Confluence, Xray, and Datadog with scoped tokens and MCP: read safely, publish idempotently, keep every write reviewable in git.
A practitioner reference for Mermaid: sequence, flowchart, state, ER, C4 context, and gantt diagrams, with copy-paste syntax and where each one renders.
What retrieval-augmented generation is, the eight stages where it fails, the requirements an analyst writes for each, and a golden-set harness that proves it.
Write business and functional requirements as YAML with stable ids, validate them with a schema, and render the BRD and FRD humans read from the same source.
A working pipeline from workshop transcript to signed UAT result for every requirement: eight stages, three machine-readable formats, and four CI gates.
Turn correlated Splunk or Datadog logs into an accurate Mermaid sequence diagram with AI. The queries, the export shape, the prompt, and the verification step.
Write a test strategy that makes decisions, turn conditions into an executable suite, run it in CI with Xray and Datadog, and generate coverage proof.
Document use cases as structured data, generate Gherkin UAT scenarios from them, keep the requirement id on every scenario, and produce the sign-off pack.
How the whole AI analyst stack fits into a real week, the 90-day build order, what to measure, how to lead adoption on your team, and what to put on your CV.
Turn an OpenAPI contract into a Bruno or Postman collection with real assertions, generate the chaining scripts, and put the whole suite behind a CI gate.
Stop pasting documents into every prompt. Build a project context pack once: glossary, contracts, data dictionary, rules, examples, and retrieval for them.
The beginner's start for analysts using AI: four first wins (sharper questions, stakeholder emails, meeting follow-ups, vague tickets) and review discipline.
The rules of engagement for AI in a regulated delivery team: what data never leaves, how to mask it, tool tiers by blast radius, and the audit trail you keep.
Point AI at the repo and answer what no document can: where a rule really lives, what a status actually means, what a pull request changes for the business.
Turn a Teams or Zoom transcript into decisions, actions, requirements, and tickets, with consent handled, contradictions surfaced, and nothing invented.
Use AI to write the SQL you can verify, define metrics that survive scrutiny, build the dashboard nobody had time for, and automate the weekly delivery pack.
Point an AI assistant at your Obsidian vault so fourteen months of notes answer questions directly, and structure the vault so answers stay traceable.
Build a complete test plan with AI in seven steps: risk, scope, conditions, cases, data, environments, and a traceability matrix proving nothing is uncovered.
The write side of an AI connection: what to automate, what never to, the approval pattern, the dedicated account, and keeping generated tickets human owned.
How pain.001 batching works: the three-level structure, BatchBooking, how a batch becomes statement entries, and what happens when one payment fails.
How a camt.053 is structured: balance types, entries, entry details, bank transaction codes, and the references that match a statement line to a payment.
DbtrAgt, CdtrAgt, IntrmyAgt1, InstgAgt, InstdAgt: the agent fields in a pacs.008, what each one means at each hop, and which ones change in transit.
The amount fields in a pacs.008: instructed amount, interbank settlement amount, exchange rate, and the rules that decide which number the beneficiary receives.
The charge bearer codes in a pacs.008, what each one obliges every agent in the chain to do, and how ChrgsInf records who actually took what.
How the cover method works: pacs.008 to the beneficiary bank, pacs.009 COV to the correspondents, and why the two must carry identical underlying details.
Purpose code vs category purpose in ISO 20022: who reads each, the codes that change routing and treatment, and why a wrong SALA costs a payroll run.
How remittance information works in ISO 20022: the 140-character unstructured field, the structured block, ISO 11649 RF references, and remittance location.
Which ISO 20022 fields sanctions screening reads, why structured addresses cut false positives, and the screening defects an analyst finds in every migration.
What the Model Context Protocol is, how to connect an assistant to Jira and Confluence safely, and the six read-only questions that pay for the setup in a week.
The decision an analyst actually has to make: which payment rail fits a flow, judged on speed, finality, cost, reach, data, and what happens when it fails.
What changes when high-value payments settle in central bank money: T2's liquidity model, CHAPS enhanced data, Fedwire's cutover, and the analyst implications.
How the SEPA Credit Transfer scheme constrains ISO 20022: SLEV charges, IBAN-only, the 140-character limit, the Latin character set, and the return flows.
How SCT Inst changes payment design: a ten second end-to-end limit, 24/7/365 availability, irrevocability, and the screening and liquidity problems that follow.
How Verification of Payee works: the name and IBAN check, the four possible outcomes, what the payer sees, and the design decisions that make or break it.
Why analysts who send, chain, and script API requests move faster: verified requirements, reproducible defects, faster triage, credible POCs, and a 30-day plan.
How analysts review an API design before build: domain naming, state changes, money and dates, error model, pagination, idempotency, and a worked review.
A plain-language API glossary for analysts: endpoint, payload, headers, tokens, idempotency, webhooks, pagination, and more, each with a real-world example.
How an analyst builds an API proof of concept: the decision it must settle, a two-day spike, mocks from OpenAPI, webhook proof, a scripted demo, and evidence.
Chain API requests in Bruno and Postman: capture values, pre-request and post-response scripts, token refresh, polling, branching, and a Stripe sandbox flow.
The OWASP API Security Top 10 (2023) as test cases analysts can run in Bruno or Postman: object and field authorization, auth, limits, business flows, and more.
How to write API test cases from the contract: a six-source derivation method, 40 worked cases for one payment endpoint, and data-driven automation in Bruno.
Run API test collections in CI with Bruno CLI, Postman CLI, or Newman in GitHub Actions: secrets, tags, JUnit and HTML reports, private networks, flaky tests.
What counts as a breaking API change, versioning strategies, Deprecation and Sunset headers, detecting breaks with oasdiff, and consumer impact assessment.
Build a first API collection in Bruno and Postman: environments, variable precedence, inherited auth, secrets in .env or a vault, and cURL imports.
GraphQL for analysts: queries, variables, mutations, errors returned with HTTP 200, cursor pagination, and hands-on testing of the GitHub GraphQL API in Bruno.
A method for analyzing an API before integration: capability mapping, field-level data mapping, failure behavior, limits, versioning, and a fit-gap worksheet.
How to document an API as an analyst: the seven sections consumers need, an OpenAPI endpoint example, an error catalogue, flow guides, and docs you can test.
How webhooks work and what analysts must specify: events, signatures, retries, duplicates, and ordering, plus testing with webhook.site and the Stripe CLI.
What an API is and how one works, for analysts: request and response, methods, headers, auth, status codes, and a real GitHub API call you can send today.
Troubleshoot failed API requests by symptom: connection and SSL errors, 401 vs 403, wrong-URL 404s, 415 and 422, 429, 5xx, CORS, and unresolved variables.
Small businesses now need SEO and GEO: ranking in Google and being quotable by AI answer engines. The shared technical base, what GEO adds, and how to measure.
When an AI agent beats a single prompt for analyst work, what tools it needs, where the guardrails go, and the three agent flows worth building first.
The five AI flows that measurably speed up analyst delivery: transcript to draft spec, negative test matrix, test data, log triage, and contract diffs.
Which analyst tasks to automate first, ranked by payback: environment checks, test data setup, reconciliation, contract validation, ticket evidence.
Six reusable prompt patterns for requirements work: grounded extraction, format contract, adversarial review, gap interrogation, traceability, testability.
How to build a second brain as a technical analyst: a plain-Markdown knowledge base, organized by system and decision, that answers questions months later.
Triage is a classification problem with money attached. How to rank by business impact, settle defect versus change request fast, and defer a defect on purpose.
A go decision is made under uncertainty. The analyst's job is to make it explicit, not make it disappear. The readiness dimensions and the evidence.
The output of refinement is not an estimate, it is decisions closed. What to bring, how to split a story without knowing the code, and what ready means.
Developers do not need you to read code. They need decisions, edge cases answered before they hit them, and the why behind the what. The questions that work.
QA finds where the system disagrees with the spec, and you wrote the spec. An untestable requirement is an analyst defect. How to be the partner QA needs.
The difference between an API key, a personal access token, and an OAuth token, how to scope and rotate them, and where they belong across an analyst toolchain.
Use a personal access token and the Jira and Confluence REST APIs to generate traceability matrices and publish specs, with working Python scripts.
Bruno keeps API collections as files in your repo with no account; Postman wraps them in a cloud platform, now with Native Git. Trade-offs for pacs.008 tests.
A Claude Skill packages your method, references, and scripts into a folder the model loads on demand. Build one that writes pacs.008 test cases.
ISO 20022 carries rich structured data, and every non-native hop quietly degrades it. The field-by-field loss ledger, and how to specify what you accept losing.
Migration programmes scope the payment rail and forget everything reading it: screening, monitoring, the warehouse, reports. The downstream impact register.
Five identifiers travel with every payment and only one survives the whole chain. Which to trace on, reconcile on, deduplicate on, and never use as a key.
A field can be optional in ISO 20022, mandatory in CBPR+, forbidden by your correspondent, and absent from your database. How to build the net rule matrix.
Namespaces, element order, the business header, empty vs absent, amount precision, and code choices. The XML layer that fails messages your test tool accepts.
How to build an Obsidian vault for analyst work: folder structure, atomic notes per ISO 20022 message and reason code, daily investigation logs, and Jira sync.
What non-functional requirements are, the categories that matter, and how to write testable NFRs with measurable targets instead of adjectives. With examples.
What slowly changing dimensions are, how SCD Type 1 and Type 2 differ, how a Type 2 table works with valid_from and valid_to, and how to query it correctly.
Smoke testing proves the build is testable, sanity testing proves a fix landed, regression testing proves nothing else broke. How they differ, when each runs.
SQL window functions and the three patterns analysts use daily: ROW_NUMBER for latest record per group, LAG for event timing, SUM OVER for running totals.
What user acceptance testing is, how UAT differs from SIT and QA testing, who writes the scenarios, and the entry and exit criteria that make a UAT cycle real.
The ISO 20022 payment transaction statuses explained: RCVD, ACTC, ACCP, ACSP, ACSC, PDNG, RJCT, and more, with the lifecycle order and what each guarantees.
The ISO 20022 reason codes analysts meet daily: account codes (AC01, AC04, AC06), amount codes (AM04, AM05), agent and regulatory codes, and what each means.
SWIFT, the EPC, and CHAPS deferred the November 2026 ban on unstructured addresses. What structured and hybrid addresses are and how to migrate anyway.
Which ISO 20022 message replaces each SWIFT MT: MT103 to pacs.008, MT202 to pacs.009, MT940 to camt.053, and the traps in the mapping. A reference table.
ISO 20022 gives three ways to bring money back: returns, reversals, and recalls. Who initiates each, which message carries it, and how to model them.
Airflow schedules tasks; Dagster declares the data assets those tasks produce. What the task vs asset split means for lineage, testing, and debugging pipelines.
A business analyst describes intended behavior; a technical BA verifies it against the running system. What separates the roles and how to cross the gap.
Data engineers build the pipelines and platforms that move data; analytics engineers model it in the warehouse so it means something. The split, explained.
Data lineage maps how each field flows from source through transformations to the report that shows it, enabling impact analysis, trust, and audit.
A data mesh decentralizes data: domains own and publish their data as products, on a self-serve platform, under federated governance. Explained with a diagram.
A dbt DAG is the dependency graph of transformations, built from ref() calls. How to read one, the staging to marts convention, and why tests sit on nodes.
dbt and SQLMesh both turn SQL into tested, versioned transformation pipelines. Where they differ: SQL parsing, environments, incremental state, and lineage.
Both write code against the same systems. The backend developer owns the production system; the developer analyst uses code to verify and automate analysis.
Fivetran and Airbyte both move source data into your warehouse. They differ on openness, hosting, pricing, and who fixes the connector when the API changes.
A functional analyst is accountable for exact system behavior; a product owner for what gets built and in what order. The split, and which seat fits you.
Kimball builds dimensional marts first and integrates through conformed dimensions; Inmon builds a normalized enterprise warehouse first. The debate, mapped.
A warehouse is a managed analytical database; a lakehouse adds warehouse guarantees to open files on object storage. The real differences, with a diagram.
Looker is a code-defined semantic layer that governs metrics; Tableau is the strongest visual exploration tool. What each optimizes for and when each fits.
The medallion architecture organizes a lakehouse into bronze (raw), silver (cleaned), and gold (business-ready) layers. What each layer owns, with a diagram.
Medallion and Data Vault answer different questions: medallion says how many quality layers, Data Vault says how to model history inside them. With diagrams.
A QA analyst derives what must be tested from requirements and risk; a test engineer builds the automation that runs it at scale. The split and the overlap.
Snowflake and BigQuery are both elastic cloud warehouses. They differ on compute models, pricing units, cloud lock-in, and the knobs your team must operate.
Star and snowflake schemas differ in one thing: whether dimensions are denormalized. What each looks like, when each fits, and how to read one. With diagrams.
A systems analyst maps how systems connect and behave; a solutions architect decides how they should, and answers for it. The line, the overlap, and the jump.
A self-assessment matrix of 25 skills across the five technical analyst hats, with three levels per skill and where to build each one. Original to this site.
Both are technical; the deliverables differ. A technical BA ships verified understanding and specs; an engineer ships production code. Which seat fits you.
How to write acceptance criteria for AI and LLM features with non-deterministic outputs: bounds, properties, guardrails, and eval sets, not exact matches.
A practitioner guide to API testing: status codes, response schemas, request chaining, authentication, error contracts, and checks that catch real defects.
Batch and event-driven processing differ in timing, which shapes latency, failure modes, and customer experience. When to use each, with banking examples.
Business Requirements Document vs Functional Requirements Document: what each covers, who reads it, and when you need both. With worked examples.
How to turn a vague business requirement into a precise functional specification: decompose intent, define inputs and outputs, and write testable behavior.
What contract testing is, how it differs from integration testing, and how consumer-driven contracts catch breaking API and event changes before production.
What a data dictionary is, how to build one, and why one authoritative definition of every field prevents the ambiguity that breaks integrations and reports.
What a dead-letter queue is, why event-driven systems need one, and how an analyst specifies DLQ behavior: retries, routing, monitoring, and recovery.
Use decision tables to specify complex business rules completely: conditions, actions, rule columns, and collapsing combinations so no case is undefined.
How to write requirements for event-driven systems: event schemas, ordering, idempotency, retries, and consistency. A practitioner guide with a Kafka example.
Field notes on going from intimidated to fluent with OpenAPI: what confused me, what clicked, and how reading the contract myself changed my analyst work.
How to run a fit-gap analysis: compare requirements to system capability, classify each fit, gap, or partial, and turn gaps into decisions. Payments example.
A functional specification template: scope, actors, data, business rules, behavior, error handling, and acceptance criteria that make a spec buildable.
The Git an analyst actually needs: clone, navigate, read a diff, browse history, and find when behavior changed. Read the codebase without breaking anything.
How a technical business analyst investigates a failed payment: the questions, the tools, and following one transaction from the complaint to the root cause.
How to write API requirements: endpoint, method, request and response schema, status codes, error contracts, and testable acceptance criteria. With examples.
An analyst's guide to HTTP status codes: the 2xx, 4xx, and 5xx families, what each common code means, and why 202 Accepted vs 200 OK matters in payments.
How to test idempotency in APIs and event consumers: idempotency keys, duplicate requests, redelivered events, and race conditions behind double processing.
Integration patterns that wire systems: request-response, messaging, publish-subscribe, request-reply, batch file transfer, and webhooks. Payments examples.
What ISO 20022 actually is as an architecture: the business model, message definitions, structured data, and usage guidelines that shape modern payment systems.
How an analyst reads JSON: objects, arrays, nesting, and types. Understand API payloads, event messages, and config files without asking a developer.
A guide to testing Kafka: consuming events in a test, asserting schema and key, verifying ordering and duplicates, and checking consumer side effects.
How to use MoSCoW prioritization to rank requirements: what each category means, how to stop everything becoming a Must, and how it drives scope decisions.
Design negative tests systematically: boundary values, invalid inputs, state violations, and failure injection, since real defects live on the unhappy path.
A field-by-field guide to pacs.008 test cases: mandatory fields, structured data, validation, reason codes, and the pacs.002 responses that prove each case.
How ISO 20022 payment messages flow end to end: pain.001 initiation, pacs.008 interbank, pacs.002 and pain.002 status, and camt reporting, for analysts.
A practitioner guide to payment testing: one transaction through ingestion, events, settlement, and status, plus the rejection and stuck-payment cases.
Production support skills for technical analysts: triage, tracing transactions, reading logs, staying calm, and turning incidents into requirements.
How an analyst reads an API contract: endpoints, methods, request and response schemas, status codes, and OpenAPI structure, without asking a developer.
Field notes from a major payments incident: reading logs under pressure, what the trail revealed, and the observability lessons that became requirements.
How an analyst reads production logs to debug a system: correlation ids, log levels, searching by transaction, and following one request across services.
How to map payment reason codes to causes and customer messages: ISO 20022 codes like AC04, internal errors, and the mapping that prevents support incidents.
How to design reconciliation between systems: matching keys, break detection, tolerance, timing, and exception handling. The control proving money is right.
The regular expressions an analyst actually needs: matching patterns in logs, validating formats like IBAN and BIC, and searching data. Practical, not theory.
Regression testing in payment systems: what to retest, building a regression suite, risk-based selection, and automating checks that protect live behavior.
What a requirements traceability matrix is, how to build one, and why it proves every requirement is designed, built, and tested. With a payments example.
How an analyst uses Python to automate repetitive checks: calling APIs, comparing files, querying data, and chaining requests. Small scripts, large leverage.
How business analysts use sequence diagrams to map a flow across services, expose integration gaps, and write better requirements. With a payments example.
The SQL a technical analyst actually needs: SELECT, WHERE, JOIN, GROUP BY, and reading state during analysis and testing. Not for reports: for finding truth.
How to model a payment as a state machine: the states, allowed transitions, triggers, and illegal moves. The tool that makes payment status behavior precise.
Synchronous and asynchronous communication differ in whether the caller waits, and that choice shapes coupling, latency, resilience, and customer experience.
What a system context diagram is, how to draw one, and why starting at the boundary stops you scoping the wrong thing. With a payments example and the C4 model.
User stories capture intent; specifications capture exact behavior. The real difference, when each fits, and why complex systems need both. With examples.
A developer analyst reads and writes enough code to verify, automate, and prototype without becoming a full-time engineer. What the role does in payments.
A functional analyst turns business intent into precise, testable system behavior. What the role does in banking and payments, and how it differs from a BA.
A QA analyst proves a system behaves correctly by testing it end to end, not by reading the spec. Here is what the role does in banking and payments.
A systems analyst maps how services, messages, and data flow across a system so the pieces work as a whole. Here is what the role does in banking and payments.
A technical business analyst analyzes, codes, tests, and supports. What the role actually does day to day in banking and payments, and how to become one.
Field notes on an AI project where acceptance criteria failed: why exact-match criteria break on non-deterministic output, and what we replaced them with.
PAIN vs pacs explained: why pain.001 is not pacs.008, how pain.002 and pacs.002 mirror it, where camt fits, and how ISO 20022 splits customer and bank.
Why testing a payment flow end to end teaches you the system and the UX better than any diagram: microservices, Kafka, the database, logs, and pain.002.