Lead Platform Engineer
# Lead Platform Engineer **LOGWARE** · Remote · `Remote` 🕒 **Статус:** *Опубликовано: 4 дня назад* · *Источник: Indeed* --- ### About the Role Founding CTO / Lead Platform Engineer Role Type: Full-Time (Remote, Africa-based preferred) Compensation: Equity-first (5% equity, 4-year vest, 1-year cliff) About the Role You will own the entire backend architecture of LogWare, including the evidence pipeline, multi-tenant security model, engine infrastructure, and integrations. Your primary responsibility is turning our Knowledge Base specifications into a production-grade reality. What You'll Build Evidence Collection Engine: Normalize, classify, deduplicate, and canonicalize security evidence from AWS, Okta, GitHub, Jira, and manual uploads. Evidence Intelligence Engine: Validate evidence type, source, freshness, and integrity, ensuring generic logs never satisfy controls requiring specific evidence. Trust & Integrity Engine: Implement SHA-256 hashing at collection time, chain of custody tracking, and tamper detection. Control Validation & Compliance Engines: Map evidence to NDPR, CBN, POPIA, Kenya DPA, ISO 27001, SOC 2, PCI-DSS, NIST CSF, and GDPR, while computing real-time framework readiness scores. Continuous Assurance Engine: Build the heartbeat that re-validates controls on schedule and emits events during status changes. Infrastructure: Develop an event-driven architecture using the LogWare Event Bus, enforce multi-tenant database isolation, and build CI/CD pipelines with automated tenant isolation tests. Requirements 3+ years Node.js backend experience in security-sensitive production systems (not just CRUD APIs). Deep MongoDB expertise involving schema design, aggregation pipelines, indexing, and multi-tenant data isolation. Experience building event-driven architectures where engines communicate via events. Security-first mindset with an understanding of cross-tenant attacks, privilege escalation, and input injection. Test-driven approach including writing attack case tests alongside happy path scenarios. Work Location: Remote Work Location: Remote
Наблюдалась 2026-09-21, впервые 2026-09-17, источник — Indeed.