Full Stack Engineer

BlueLift builds software for businesses that operate under licence — banks, asset issuers, and institutions under regulatory supervision. We're building a multi-tenant platform where each client runs their own branded environment on shared infrastructure, and we need someone to own the application layer entirely.

You'd be the first engineer on the application side. A separate blockchain engineer owns the contract layer, and the two of you would define the boundary between them together.

The architecture decisions you make in month one will still be there in year three.

WHAT YOU'LL OWN

• Multi-tenant architecture — tenant isolation, per-client theming, configuration management. One client seeing another client's data is a business-ending event, not a bug, and this gets designed on day one rather than retrofitted.
• Admin dashboard — setup workflows, permission management, records views, approval flows.
• White-labelled client portal — onboarding, document access, and interfaces used by people who are not technical.
• Integration layer — third-party identity and verification providers, through clean, swappable interfaces.
• Audit trail and reporting — append-only records that hold up when someone with authority asks for six months of evidence in a specific format.
• The API boundary between the application and contract layers, defined jointly with the blockchain engineer.
• Engineering foundations — code standards, review culture, CI/CD, deployment pipeline, monitoring. All from scratch.

TECHNICAL REQUIREMENTS

Core

• 5+ years building production web applications
• At least one multi-tenant SaaS product you shipped and then maintained — this specific experience matters more than total years, because the hard problems only surface once real clients are on it
• TypeScript with Node.js, or Python — strong in at least one, comfortable in the other
• React or an equivalent modern framework, with real component architecture experience rather than only feature work
• PostgreSQL — schema design, query performance, indexing, and data integrity constraints

Architecture and security

• Multi-tenancy patterns and their trade-offs — shared schema with row-level scoping, schema-per-tenant, database-per-tenant — and when each is appropriate
• Authentication and authorisation: session management, JWT, OAuth flows, and role-based access control that survives contact with real permission requirements
• Append-only or event-sourced data patterns, or a demonstrated understanding of why records in regulated systems are never updated in place
• Secure handling of sensitive data — encryption at rest and in transit, secrets management, and a working knowledge of the OWASP Top 10

Infrastructure

• Cloud deployment on AWS or GCP — containers, managed databases, object storage, networking fundamentals
• CI/CD pipelines with automated testing and repeatable deployments
• Monitoring, structured logging, and error tracking — assume things will break and design so that you find out first
• Comfortable with Docker; Kubernetes useful but not required at our scale

Practice

• Testing discipline across unit, integration, and end-to-end. Tenant isolation tests are non-negotiable here
• API design — REST or GraphQL, versioning, and documentation someone else can actually use
• Git workflow, and code review as a discipline rather than a formality
• The ability to make architecture decisions and defend them, and to work without detailed specs when they don't yet exist

STRONGLY PREFERRED

• Fintech or regulated-industry software
• White-label or heavily configurable products — theming systems, per-tenant feature flags, configuration over code forks
• Experience integrating KYC or identity verification providers (Sumsub, ShuftiPro, Onfido, or similar)
• Background job processing and scheduling at scale
• Any blockchain exposure — useful for the API boundary, though the contract layer isn't your responsibility

WHAT WE'RE NOT LOOKING FOR

• Someone who wants to be a blockchain developer — that's a separate role, and we're hiring for it separately
• An architect who doesn't write code. This role builds
• Anyone who treats tests, documentation, and review as overhead
• Engineers whose experience is entirely agency or project work with no long-term ownership of a system

WHY THIS ROLE IS UNUSUAL

Most senior engineering roles in Pakistan involve inheriting someone else's decisions. Here you'd set them — the stack, the standards, the way the team works — and then help hire the engineers who work within them.

The work is also demanding in a specific way: our clients' systems get audited. That changes what "done" means. If that sounds interesting rather than tedious, this is a rare seat.

TERMS

Full-time, on-site in Karachi. Compensation is market-competitive for senior engineering and based on demonstrated depth rather than years alone. Formal employment with written probation terms, EOBI/SESSI registered from month one. Modern hardware, tooling, and the software licences you need. Direct founder access and a short decision chain. A defined path to engineering leadership as the team grows.