Job Opportunities API

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. Share’s network spans thousands of kilometers of fiber, 12 infrastructure providers, and 10 data centers, reaching over 8 million people across East Africa. 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 VP & Staff 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. This is the most senior individual contributor role on the engineering team. You are expected to make architectural decisions, write production code, review others’ work, and unblock the team when they hit technical walls. You will not manage people. You will build systems. WHAT YOU WILL OWN - Payments domain: SasaPay collections integration (C2B API, STK push, IPN handling), revenue split engine (per-partner, per-BNG percentage logic), ChoiceBank treasury operations (withdrawals, internal transfers, OTP flows), and the payment completion handler that bridges payment confirmation to subscriber activation. - Billing engine: Subscription and BillingCycle lifecycle, automated renewal cron, grace period enforcement, plan change mid-cycle logic, and the event-driven communication triggers that notify subscribers at every billing moment. - Integration layer: Splynx adapter (plan sync outbound, subscriber sync inbound, activation webhooks), custom webhook delivery engine, and the event routing that connects domain events to external system notifications. - Architecture decisions: Service boundaries, event contracts (Kafka), data model evolution (Prisma/PostgreSQL), API design for both public and private endpoints, and the migration strategy from the legacy Next.js monolith to the NestJS microservices platform. TECHNICAL ENVIRONMENT Backend (where you will spend most of your time) - NestJS monorepo with 7 microservices (CRM, Billing, Payments, Ledger, Communications, Provisioning, Integrations) - TypeScript end-to-end - PostgreSQL with Prisma ORM (shared database, service-scoped access) - Kafka message bus (migrating from RabbitMQ) for inter-service communication (send/emit patterns) - Redis for caching, queues, rate limiting, and idempotency - REST API gateway with Swagger documentation Payments and financial systems - SasaPay (OAuth 2.0, C2B collections, B2B transfers, IPN webhooks) - ChoiceBank BaaS API (KYC, internal transfers, OTP-based withdrawal confirmation) - Revenue split engine with per-partner/per-BNG/per-plan configuration - Double-entry ledger (AccountTransfer, AccountLedgerEntry, AccountRevenueSplit) - M-Pesa STK push integration via SasaPay as collections gateway Infrastructure and tooling - GitHub Actions CI/CD, SSH deployment to VMs - Sentry for error monitoring, Loki + Pino for structured logging (being implem