Fraz Ahmed Cheema
Software Engineer
Management: Under a year (1-5 people)
TypeScript
Node JS
JavaScript
SQL
Active 1 day ago
Invite to interview
Download CVCV
Overview
Technical skills
Projects
Timeline
Roles
Overview
Senior-level backend Node/NestJS developer specializing in multi-tenant SaaS backend services. The strongest proven skill is designing tenant-aware infrastructure and data isolation, evidenced by tenant-aware repository patterns and dynamic tenant connection handling in src/core/base/base-tenant.repository.ts and the tenant connection/provider files. There is little to no public evidence of frontend work, accessibility engineering, measured frontend performance optimization, or meaningful automated test coverage.
Phone
Technical skills
Languages
4
TypeScript
Node JS
JavaScript
SQL
Node JS
3
Nest.JS
Ioredis
Express
DevOps
7
Amazon EC2
GitHub Actions
Rest API
CI/CD
AWS
Amazon S3
AWS Lambda
Frontend
4
Next.js
React.js
class-validator
Tailwind CSS
Databases
3
PostgreSQL
MySQL
Redis
Other
16
Jest
Supertest
Claude
Firebase
GitHub
Socket.IO
Docker
Git
Postman
RabbitMQ
Claude Code
PostCSS
GraphQL
TCP/IP
WebSockets
IAM
Projects
Designed a multi-branch school platform where a single school can manage multiple branches using branch-scoped users and operational data. Centralized student, teacher, and staff administration, including enrollment, profiles, and role-based records. Replaced manual processes with structured billing and exam lifecycle workflows, and consolidated resource handling into an inventory module.
Built a Bitwarden-style password management solution spanning a web app and a browser extension. Implemented end-to-end encryption for vault data to ensure secrets are accessible only to authorized users. Added secure sharing features for teams and families, credential autofill support, password generation, and password health reporting for weak or reused entries.
Created a dual-backend system separating TCP-based wearable communication from the mobile backend while keeping device data synchronized. Built a real-time health data pipeline with automated threshold alerts for abnormal readings. Added GPS tracking with geofencing notifications for caregivers and enabled command-based remote interactions for vital checks and video calls.
Developed an end-to-end telehealth clinic workflow that covers patient/provider lead pipelines, conversions, appointment scheduling, and in-platform video consultations. Integrated an external EMR system to synchronize patient records and reduce manual clinical entry. Implemented self-service billing with subscriptions and appointment payments, with role-based authorization and automated deployment processes for production releases.
Timeline
Full-Stack Software Engineer
•
Middle
BracketsLtd
•
Full-Time
- Built and shipped full-stack features for multiple healthcare and enterprise applications using NestJS, React, Next.js, and MongoDB.
- Designed multi-tenant infrastructure for a clinic management platform with subdomain routing and tenant data isolation.
- Implemented role-based access control and secure handling of production data.
- Owned CI/CD with GitHub Actions and AWS EC2 deployments, cutting release time significantly and reducing manual steps.
Nest.JS
Next.js
React.js
Amazon EC2
GitHub Actions
CI/CD
GIFT University
Bachelor's Degree •
Computer Science
Software Engineer
•
Middle
Authority Hype
•
Part-Time
- Contributed to an e-commerce platform, implementing backend services and RESTful API functionality for catalog, orders, authentication, and checkout flows.
- Supported core application components needed for reliable end-to-end shopping experiences.
- Worked within an iterative development process to deliver features aligned with product requirements.
Rest API
Software Engineer
•
Middle
Volnyn
•
Full-Time
- Developed core capabilities for a freelancer marketplace platform across the customer and freelancer lifecycle.
- Implemented payment workflows for order checkout and freelancer payouts to support secure end-to-end transactions.
- Delivered features for a real-estate product including property discovery and buyer-seller communication flows.
Freelance Software Engineer
•
Middle
Fotan Schools
•
Freelance
- Built a multi-branch school management system to centralize student, teacher, and staff administration across multiple school locations.
- Streamlined fee and examination workflows by automating tracking and generating outputs for reduced manual effort.
- Added inventory management for student essentials and supported centralized handling across branches.
Senior Frontend Developer
Confidence: High Fullstack
Senior-level backend Node/NestJS developer specializing in multi-tenant SaaS backend services. The strongest proven skill is designing tenant-aware infrastructure and data isolation, evidenced by tenant-aware repository patterns and dynamic tenant connection handling in src/core/base/base-tenant.repository.ts and the tenant connection/provider files. There is little to no public evidence of frontend work, accessibility engineering, measured frontend performance optimization, or meaningful automated test coverage.
UI Component Architecture
How interface parts are built
Not evidenced in public code
Responsive & Cross-browser
Works on all screens and browsers
Not evidenced in public code
Performance Optimization
Speed of the interface
Not evidenced in public code
Accessibility & Semantics
Usable for everyone
Not evidenced in public code
State Management & Data Flow
Managing data in the app
Not evidenced in public code
UX & Visual Polish
Look and feel quality
Not evidenced in public code
Industries
Software• Middle
Technologies
JavaScript
Node JS• Senior
Tailwind CSS
Next.js• since 2025
Express
GitHub Actions• since 2025
CI/CD• since 2025
Git
AWS
Docker
React.js• since 2025
PostCSS
Ioredis
AWS Lambda
Amazon EC2• since 2025
class-validator
GitHub
Amazon S3
IAM
TCP/IP
Recommendations
- Lead implementation of multi-tenant SaaS backends, including tenant DB lifecycle, tenant-aware repositories, and tenant-scoped caching.
- Design and implement robust auth and session systems with Redis-backed session storage and token blacklisting.
- Build backend integrations that require per-tenant isolation such as per-tenant DB connections, seeders, and master/tenant coordination logic.
- Harden systems with end-to-end tests and CI pipelines and add measurable performance and security tests for tenant isolation.
Repositories
The developer's experience in this domain has been verified based on AI analysis of the following repositories:
Middle Backend Developer
Confidence: Medium API Engineer
Backend developer (Middle) focused on NestJS APIs and multi-tenant backend patterns with a strength in tenant-aware data and auth flows. The strongest proven skill is building tenant-aware authentication and session tooling using dynamic tenant connections and Redis-backed session/blacklist logic, as shown in src/modules/auth/services/auth.service.ts and src/cache/session-cache.service.ts. There is limited evidence of production-grade concerns such as schema migration history, automated tests, explicit transactional handling, or distributed service contracts.
API Design
3/10
How well APIs are designed
API work shows pragmatic auth flows and consistent use of exceptions but lacks documented versioning, pagination, idempotency, and an explicit error contract.
Evidence
nmsports-backend/src/modules/auth/services/auth.service.ts
LearningNestJs/src/posts/posts.service.ts
Data Layer & Database
4/10
Working with databases
Data layer demonstrates deliberate tenant-aware abstractions, dynamic tenant models and password hashing, but there is no migration history, explicit transaction boundaries, or advanced query tuning shown.
Evidence
nmsports-backend/src/core/base/base-tenant.repository.ts
nmsports-backend/src/modules/user/repositories/user.repository.ts
LearningNestJs/src/users/repository/users.repository.ts
Scalability & Performance
4/10
Handling load and speed
Caching and session management are implemented with Redis (TTL, key prefixes, blacklist patterns), showing attention to performance; no queueing, rate limiting, or benchmarked optimizations are present.
Evidence
nmsports-backend/src/cache/redis.service.ts
nmsports-backend/src/cache/session-cache.service.ts
System Architecture
3/10
Overall system structure
Modular NestJS structure and multi-tenant separation indicate intentional module boundaries and tenancy design, but there is limited evidence of cross-service contracts, graceful degradation or a distributed architecture.
Evidence
nmsports-backend/src/modules/auth/services/auth.service.ts
nmsports-backend/src/core/base/base-tenant.repository.ts
Security & Auth
5/10
Protecting data and access
Authentication and authorization are implemented with bcrypt, JWTs, tenant validation and token blacklisting which provide a solid baseline; advanced token lifecycle features and comprehensive input validation traces are not evidenced.
Evidence
nmsports-backend/src/modules/auth/services/auth.service.ts
nmsports-backend/src/cache/session-cache.service.ts
nmsports-backend/src/modules/user/repositories/user.repository.ts
Reliability & Observability
3/10
Stability and monitoring
Reasonable logging and Redis error/ready/connect handlers provide basic observability and reliability awareness; there are no structured correlation ids, retries with backoff, circuit breakers, or explicit shutdown/cleanup hooks shown.
Evidence
nmsports-backend/src/cache/redis.service.ts
nmsports-backend/src/cache/session-cache.service.ts
Expertise
Node.js• Middle
Microservices & API Architecture• Middle
Technologies
Rest API• since 2025
Nest.JS• since 2025
GraphQL
Recommendations
- Develop multi-tenant REST API endpoints for a SaaS product that require tenant-aware repositories and dynamic DB connections.
- Implement an auth/session subsystem with JWT refresh/rotation, token revocation, and Redis-backed session management including tested edge cases.
- Build schema migration tooling and a migration history for tenant databases to demonstrate safe schema evolution and rollback.
- Add observability and reliability improvements: structured correlation ids, retries with backoff, graceful shutdown hooks, and basic performance benchmarks.
Repositories
The developer's experience in this domain has been verified based on AI analysis of the following repositories:
Middle QA Engineer
Confidence: Medium Generalist
Backend developer specializing in multi-tenant NestJS services with explicit session and cache layers and tenant-aware data access (Senior-level 3.5). The strongest proven skill is designing multi-tenant backend architecture and tenant-aware repositories as implemented in core/base/base-tenant.repository.ts, tenant connection handling, and cache/session services such as cache/redis.service.ts and cache/session-cache.service.ts. Automated test suites, CI pipelines, contract testing and documented QA practices are not evidenced in the public human-authored code.
Test Automation Frameworks
2/10
Building automated tests
Minimal test automation footprint detected: project is configured for Jest and Supertest but there is no human-authored test infrastructure, fixtures, or test code in the analyzed files.
Evidence
nmsports-backend/package.json: jest configuration and scripts
nmsports-backend/package.json: devDependencies.supertest
LearningNestJs/package.json: jest configuration
Test Coverage & Strategy
1/10
What and how to test
No structured test coverage or risk-based test strategy found; only coverage script config exists but no tests, negative-paths, property tests or mutation testing artifacts were present.
Evidence
nmsports-backend/package.json: "test:cov" script and jest.collectCoverageFrom
API & Integration Testing
1/10
Testing how parts work together
API/integration testing tooling is referenced (Supertest, jest e2e script) but there are no concrete integration tests, schema/contract validations, or idempotency/error-path tests in the human-authored code.
Evidence
nmsports-backend/package.json: devDependencies.supertest
nmsports-backend/package.json: "test:e2e" script
Performance & Load Testing
Testing speed under load
Not evidenced in public code
Bug Reporting & Analysis
Finding and describing bugs
Not evidenced in public code
CI Test Integration
1/10
Running tests automatically
Basic test scripts are present in package.json but there is no CI workflow, failure artifact collection, or quarantine/retry policy implemented in human-authored CI files.
Evidence
nmsports-backend/package.json: jest and e2e test scripts
LearningNestJs/package.json: jest scripts
Expertise
Unit & Component Testing• Junior
Technologies
TypeScript• since 2025 • Senior
Postman
Jest
Supertest
Recommendations
- Implement a focused test suite using Jest and Supertest: add unit tests for repository and service logic and end-to-end tests that exercise tenant flows and auth edge cases (invalid tenant, cross-tenant access, expired tokens).
- Add contract/schema validation tests and negative-path cases: validate response schemas, test 401/403/404/409/422 paths and idempotency for critical endpoints and token blacklist behavior.
- Introduce CI integration with per-test artifacts and selective retries: add workflow that runs unit and e2e tests, archives failure logs/screenshots, and isolates test databases (testcontainers or in-memory Mongo) for parallel CI runs.
- Add performance checks for session and cache behavior: create simple load or benchmark scripts (k6 or similar) that measure latency under concurrent auth requests and session-store operations.
Repositories
The developer's experience in this domain has been verified based on AI analysis of the following repositories: