Share - Staff Software Engineer

• 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. • Strong preference • Strong preference • Experience in East African fintech or mobile money ecosystems (M-Pesa, SasaPay, Airtel Money). Understanding of Kenya’s payment infrastructure and regulatory environment. • Experience with ISP billing systems, RADIUS protocols, or telecommunications platforms. • Experience with Prisma ORM and NestJS specifically. • Production experience with multi-tenant SaaS platforms (provider-scoped data, API key auth, webhook delivery). • Track record of migrating monolithic systems to microservices while keeping production running. • 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 coding assistants (Claude, Cursor, Copilot, or similar) daily and can articulate how they change your workflow — not just autocomplete, but architectural reasoning, spec review, and debugging. • You are comfortable working with AI-generated specifications and can critically evaluate them, push back where they are wrong, and extend them where they are incomplete. • You see AI as a force multiplier that lets a small team operate at the capacity of a much larger one. You are not threatened by it; you are faster because of it. • You are willing to contribute to improving our AI-assisted workflows — better prompts, better context files, better session structures.