Work
GeniusPay — POS and payments platform
Hands-on CTO at GeniusPay AB, a Swedish POS and payments company serving restaurants and retail: engineering leadership across a distributed team, plus direct contribution to the .NET backend and the native Android app.
C# · .NET · Java · Android
- Context
- GeniusPay AB provides point-of-sale systems, payment terminals and business management software for restaurants and retail in Sweden. Majed is the company’s CTO — named openly here, because the role is public on LinkedIn.
- Problem
- Payments demand correctness under concurrency, auditability and integration discipline — across a transaction backend and a native Android client that must move together.
- Constraints
- A financial domain where mistakes cost money and trust; a distributed team across time zones; and the payment industry’s usual discipline — volumes, partners and internals stay off the public record.
- Role
- CTO at GeniusPay AB — engineering leadership plus direct, verifiable contribution to the C# backend and the Java Android app.
- Architecture
- A C#/.NET transaction backend with CI-gated delivery, a native Java Android application, and a bilingual public web presence. Detailed payment architecture is deliberately not documented publicly.
- Key decisions
- Most technical decisions stay internal. The shareable one is an operating principle: the CTO stays in the codebase — leadership earns its opinions by shipping alongside the team.
- Outcome
- The platform is the company’s core product, publicly marketed at geniuspay.se. Volumes and business metrics stay internal.
- Evidence
- The role is public on LinkedIn; the company’s site runs at geniuspay.se (verified live 2026-07-15). Contribution history is verifiable in the organisation’s repositories.
- Confidentiality
- The company is named — it is Majed’s own role, public on his LinkedIn. What stays internal: volumes, partners and detailed payment architecture.