Builder Academy · Learning pathway

Engineering connected systems

Explore how software, data, research, security and operations fit together. Start with the mental model, try a synthetic exercise, then apply it to a portfolio project.

Planned learning modules

Planned outline · Module 01

Web research infrastructure

Search indexes, crawling, extraction, RAG, provider selection and citations.

Practice: Draw a research request from browser to verified evidence.

Planned outline · Module 02

Systems architecture

Modular monoliths, service boundaries, coupling and scaling.

Practice: Choose a boundary for a new research consumer.

Planned outline · Module 03

Data engineering

Sources, ETL/ELT, transformations, contracts, versioning and quality.

Practice: Trace one RSS item through a pipeline.

Planned outline · Module 04

API engineering

HTTP, REST, GraphQL, webhooks, authorization, pagination and versioning.

Practice: Design an authenticated research API contract.

Planned outline · Module 05

Distributed systems

Parallelism, asynchronous jobs, queues, retries, consistency and idempotency.

Practice: Find duplicate work in a retried job.

Planned outline · Module 06

Software security

Threat modeling, least privilege, SSRF, injection, secrets and supply-chain safety.

Practice: Identify two unsafe trust boundaries.

Planned outline · Module 07

Knowledge engineering

Taxonomies, ontologies, entity resolution, relationships and temporal history.

Practice: Resolve two names to one vendor entity.

Planned outline · Module 08

Reliability engineering

Structured logs, metrics, traces, SLOs, alerts and incident response.

Practice: Diagnose a failed extraction task.

Planned outline · Module 09

AI engineering

RAG, embeddings, reranking, tool calls, MCP and evaluation.

Practice: Verify a machine-generated claim.

Planned outline · Module 10

Infrastructure and DevOps

Environments, Docker, CI/CD, deployments and rollback.

Practice: Plan a safe database migration.

Planned outline · Module 11

Engineering economics

Provider prices, latency, cache, usage budgets and build-versus-buy.

Practice: Compare cost per verified finding.

Planned outline · Module 12

Software governance

ADRs, ownership, reviews, versioning and deprecation.

Practice: Write an architecture decision record.

Planned outline · Module 13

Product engineering

Discovery, PRDs, roadmaps, UX, accessibility and feature flags.

Practice: Define acceptance criteria for a lab.

Planned interactive labs

Specifications only: these labs are not yet interactive or connected to paid APIs.

Architecture Explorer

Frontend → API → queue → provider → database; identify failure boundaries.

Data Pipeline Simulator

Collect → validate → deduplicate → normalize → store → review.

Distributed Systems Playground

Compare sequential work, concurrency, retries and idempotency.

Security Threat Modeling Lab

Identify prompt injection, SSRF and access-control weaknesses using synthetic examples.

Incident Response Simulator

Investigate a fictional provider outage, leaked token or deploy failure.

Research Provider Playground

Compare mock Exa, Firecrawl and Parallel responses; never label fixtures as live measurements.

Evidence Explorer

Inspect citations, source hashes, freshness, conflicts and review status.

Capstone: research you can trust

Use public or synthetic cybersecurity sources to map source → capture → hash → entity → claim → review → downstream product. Never confuse a provider result with independently verified evidence.

Start with the Account Signal Engine Research Hub and its RSS / Firecrawl foundation; add paid providers only after security, cost and quality evaluation.