Aleph - Principal Engineer

• Set the technical direction for new products and major changes, and stay the technical decision-maker through build and post-launch — with the authority to course-correct when implementation drifts, and the habit of being in the codebase to catch the drift early. • Build the hard parts yourself. Write production code on the riskiest, highest-leverage paths; prototype the uncertain approach to turn an argument into evidence; build the reference implementation others extend. • Turn intangible trade-offs — partner API risk, team capability, long-term scalability, cost of change — into clear, written decisions (ADRs) that leadership and the technical committee can sign off on. • Define service and data contracts, integration patterns, and resilience strategies that survive third-party API deprecations and outages. • Go deep when it breaks: lead diagnosis on the gnarliest production incidents and performance regressions, and land the fix and the systemic follow-up. • Identify the infrastructure (compute, data, messaging, observability) needed to meet current and near-future goals. • Raise the bar through others: mentor engineers and tech leads, set the standard in code review, and drive cross-functional decisions across engineering, product, security, and operations — through influence, not line management. • Evaluate third-party and vendor solutions against our integration and data requirements. • Monitor systems against performance and business benchmarks and escalate with concrete recommendations.