// ENGINEERING DIVISION

Building the Nervous System of Global Knowledge

We design, ship, and maintain the distributed systems that power real-time AI inference, petabyte-scale search, and verified knowledge graphs across 140+ languages.

Production-Ready Stack

Performance, reliability, and developer velocity drive our technology choices. We standardize on battle-tested infrastructure while remaining pragmatic about trade-offs.

⚑

Frontend

  • Next.js 14
  • TypeScript
  • Turborepo
  • Tailwind CSS
  • React Query
  • Vitest
πŸ”§

Backend & Services

  • Go
  • Rust
  • gRPC / Protocol Buffers
  • tRPC
  • Zod
🧠

AI & Inference

  • Python
  • LangGraph
  • vLLM
  • ONNX Runtime
  • LangSmith
πŸ—„οΈ

Data & Search

  • PostgreSQL
  • ClickHouse
  • Milvus
  • Elasticsearch
  • Kafka
☁️

Infrastructure

  • Kubernetes
  • Terraform
  • AWS / GCP
  • ArgoCD
  • Datadog

From Ingestion to Inference

Every article, citation, and multimedia asset passes through a multi-stage verification and indexing pipeline before reaching users.

πŸ“₯
Ingestion
APIs, scrapers, and contributor submissions
πŸ”Ž
Validation
Source cross-referencing & bias detection
πŸ”—
Graph Mapping
Entity extraction & relationship linking
πŸ—‚οΈ
Indexing
Vector embeddings & semantic search
πŸš€
Delivery
Edge CDN & real-time API responses
> Pipeline latency: P99 < 120ms
> Daily throughput: ~2.4M entities
> Verification SLA: 99.94% accuracy
> All stages are idempotent, retriable, and observable via OpenTelemetry traces.

How We Build

Our technical decisions are guided by principles that prioritize correctness, transparency, and long-term maintainability.

01

Reliability Over Speed

We ship fast, but never at the cost of data integrity or user trust. Every feature includes automated regression tests and canary deployments.

02

Open by Default

Internal tools, RFCs, and postmortems are public unless they contain PII or security-sensitive logic. Transparency builds better systems.

03

AI-Augmented, Not AI-Replaced

We use AI to automate boilerplate and surface insights, but human experts retain final authority on knowledge verification and editorial policy.

04

Global-First Architecture

Multilingual support isn't a featureβ€”it's a constraint. We design schemas, UIs, and search algorithms from day one for 140+ locales.

Built in Public

We contribute back to the ecosystem and run our development process openly. Every major change starts with an RFC.

$ gh pr list --repo aevum/eng-rfcs
#42 [WIP] Standardize vector embedding rotation strategy
#39 [MERGED] Replace Redis cache with distributed KV layer
#34 [REVIEW] Multi-tenant LLM gateway rate limiting
# All RFCs are public, archived, and version-controlled.

$ aevum-cli submit-rfc --title "Search Re-ranking Pipeline"
βœ“ Draft created: ./rfcs/2025-04-11-search-reranking.md
βœ“ PR opened β†’ aevum/eng-rfcs#43

Engineering Culture

  • πŸ”

    Blameless Postmortems

    Every incident is a system failure, not a person failure. We document root causes and implement preventive controls.

  • πŸ“–

    Async-First Communication

    Decisions are documented, not discussed in meetings. PRDs, RFCs, and runbooks replace status updates.

  • πŸ§ͺ

    20% Exploration Time

    Engineers dedicate one day per week to tooling, research, or open-source contributions aligned with platform goals.

  • 🌍

    Remote-First, Globally Distributed

    Team spans 14 time zones. We optimize for written communication, overlapping cores, and async code reviews.

Ship Systems That Scale Knowledge

We're looking for engineers who care about correctness, love building infrastructure, and want to work on systems that impact millions of learners worldwide.

Backend (Go/Rust) AI/ML Infrastructure Platform Engineering Search & Indexing SRE / Reliability
}