What are the Analyst Engineering Labs?

The Labs are missions that simulate the work of a technical analyst on a delivery team. Each mission gives you real artifacts (an OpenAPI contract, requirements, Kafka events, logs, database extracts, monitoring) and one deliverable to produce, then a practitioner solution to score yourself against. All missions are set inside Northline Pay, a fictional payment platform documented once and reused everywhere.

Do I need an account to do the Labs?

No. Every mission brief, every step, and every artifact is open. A free account, opened with an email link and no password, saves your step progress and your self-assessment, shows your missions on a dashboard, and unlocks the solutions.

In what order should I do the missions?

Follow the Become a Technical Analyst track: analyze the API first, then validate the event flow, then investigate the incident. Each mission reuses what the previous one taught you about the platform, and the incident in mission three is caused by the gaps found in missions one and two.

>_ Analyst Engineering

Labs

Practice the technical analyst job on a system that behaves like production

Each mission hands you the artifacts a delivery team actually has: an OpenAPI contract, requirements, Kafka events, service logs, database extracts, monitoring panels. You produce one deliverable. Then you compare it with a practitioner's solution and score yourself on what you found.

Every mission is set inside Northline Pay, a fictional payments platform documented once. Learn the system in mission one, and mission three does not need to explain it again.

Start Mission 01 Create a free account

Track

Become a Technical Analyst

Three missions in order: analyze an API before integration, validate an event flow across Kafka and logs, then investigate a production incident to root cause. One system, rising difficulty.

See the track

All missions

Mission 01 Structured 60 min 4 steps

Analyze a payment API

A hands-on lab for technical analysts: read a real OpenAPI contract against requirements, sample responses, and business rules, and find the gaps before a developer writes integration code.

API analysisRequirements gap analysis Functional AnalystBusiness Analyst

Mission 02 Independent 60 min 3 steps

Validate an event flow

A hands-on lab for technical analysts: follow one payment across Kafka topics, consumer logs, and a dead letter queue, and prove why the settlement event never arrived.

Event flow validationLog analysis QA AnalystSystems Analyst

Mission 03 Open 90 min 3 steps

Investigate a production incident

A hands-on lab for technical analysts: work a duplicate refund incident from the ticket through API responses, request logs, database records, and monitoring, and separate the trigger from the defect.

Incident investigationLog analysisSQL investigation Developer AnalystSystems Analyst

How a mission works

01
Read the brief

Your role, the situation, the deliverable, and the articles worth reading first.
02
Work the steps

Each step reveals more evidence and sets one task. Write your answers as you go.
03
Produce the deliverable

A gap register, a diagnosis, an incident report: the artifact a real team would act on.
04
Score yourself

Open the solution, tick the findings you actually had, and learn from the ones you missed.

Skills the missions practice

API analysis: Read an API contract against requirements and business rules, and find what is missing, inconsistent, or unspecified before integration starts.
Requirements gap analysis: Trace each requirement to the artifact that implements it and name the gaps precisely enough that a developer can act on them.
Event flow validation: Follow a business event across Kafka topics, consumers, and logs, and prove where it stopped and why.
Log analysis: Correlate application logs across services by identifier and time to reconstruct what actually happened.
Incident investigation: Move from a vague ticket to a root cause with evidence from APIs, logs, database records, and monitoring, and separate cause from symptom.
SQL investigation: Query production-shaped tables to confirm or refute a hypothesis, and read the result as evidence.
Test design: Derive test cases from contracts, rules, and defects so the same failure cannot ship twice.

The system

Northline Pay

A fictional payment service provider for marketplaces. Every lab is set inside it.

Free account

Practice on the Labs, keep your progress

A free account, no password: an email link signs you in. It saves your steps and self-assessments on the Labs, shows your missions on a dashboard, unlocks the solutions, and, if you tick the box, sends you new missions and articles when they ship.

Your email is used to sign you in. Nothing else, unless you ask. Privacy.