Founding Engineer

**About Share** --------------- Share is a venture\-backed internet infrastructure network building Africa’s backbone. The company aggregates underutilized telecom infrastructure, fiber, subsea cables, and data centers, and provides ISPs with scalable access to bandwidth without traditional upfront costs. Through an open\-access model, local internet providers can deliver dramatically faster speeds to their subscribers without raising their own costs. The platform team builds the software that makes this work: billing, payments, subscriber management, RADIUS\-based network authentication, and integrations with ISP billing systems and mobile money providers. We are replacing legacy, non\-API systems with a modern API platform, and real money is already flowing through the system. This is a small, high\-intensity engineering team building core infrastructure under real deadlines. You will own entire domains, not tickets. **The role** ------------ We are hiring a Founding Software Engineer to take ownership of the platform’s most critical technical domains: the payments pipeline (collections, revenue splitting, treasury operations), the billing engine (subscription lifecycle, cycle management, automated renewals), and the integration layer (BSS/OSS sync with partner systems). You will work directly with the CTO and a small team of engineers to ship production systems that handle real financial transactions for real ISP partners. **Non\-negotiable** ------------------- * 7\+ years of professional software engineering experience, with at least 3 years in backend systems handling real financial transactions (payments, billing, ledger, or treasury) * Deep TypeScript/Node.js expertise. You should be able to design a NestJS microservice from scratch, not just work in one. * Production experience with payment gateway integrations (M\-Pesa, Stripe, Adyen, or similar). You understand STK push flows, webhook idempotency, callback signature verification, and reconciliation. * Strong PostgreSQL skills. You can design schemas for financial data, write migrations, and reason about transaction isolation and locking. * Experience with event\-driven architectures (Kafka, RabbitMQ, or similar). You understand the difference between request\-reply and fire\-and\-forget patterns and when to use each. * You ship. You can take a spec document and turn it into production code without waiting for someone to break it into small tasks. **AI\-augmented engineering (required mindset)** ------------------------------------------------ We expect every engineer at Share to use AI tools as a daily part of their workflow. This is not optional and not aspirational — it is how we operate. Our entire project planning, specification, and documentation process runs through AI\-assisted sessions. Our codebase includes AI\-readable context files. We use Claude for architecture decisions, code review, spec generation, and technical writing. What this means for you: * You already use AI...