Freelance Frontend Engineers in Islamabad Capital TerritoryFreelance Frontend Engineers in Islamabad Capital Territory
Web Designer & Developer | Figma to Next.js | UI/UX
$5k+
Earned
3x
Hired
5.0
Rating
36
Followers
Web Designer & Developer | Figma to Next.js | UI/UX
Full-stack developer building high-impact web products.
$25k+
Earned
3x
Hired
5.0
Rating
50
Followers
Full-stack developer building high-impact web products.
šŸš€ AI & Fullstack Developer | MERN Expert šŸš€
$10k+
Earned
5x
Hired
5.0
Rating
30
Followers
šŸš€ AI & Fullstack Developer | MERN Expert šŸš€
We build interactive sites - with code & no-code solutions
$1k+
Earned
3x
Hired
5.0
Rating
38
Followers
We build interactive sites - with code & no-code solutions
AI SaaS Dev | LLMs, Agents, Voice & Automation | Web, Mobile
1x
Hired
5.0
Rating
3
Followers
AI SaaS Dev | LLMs, Agents, Voice & Automation | Web, Mobile
Full-Stack & AI Developer | React Native, Next.js, AI Agents
5.0
Rating
2
Followers
Full-Stack & AI Developer | React Native, Next.js, AI Agents
Cover image for EarnDLT (GreenTruth) (https://earndlt.com) is a
EarnDLT (GreenTruth) (https://earndlt.com) is a blockchain-based carbon compliance platform that helps companies track and report emissions data under the EU's Carbon Border Adjustment Mechanism (CBAM) and Scope 3 supply-chain requirements. The backend was live and running on NestJS with a GraphQL API, but as the platform scaled, it needed to support third-party data providers who expected standard REST endpoints rather than a GraphQL schema. šŸš€ What I worked on As part of the engineering team, I worked on migrating the core backend from GraphQL to a REST API architecture, on a platform already handling live compliance data. This involved mapping existing GraphQL queries and mutations to equivalent REST endpoints and reworking the data-access and request/response contracts so external providers could integrate cleanly. šŸš€ Stack: NestJS for the backend framework TypeScript across the API surface PostgreSQL for compliance and emissions data Next.js on the frontend REST replacing GraphQL as the integration layer šŸš€ The key challenge The migration ran over 1-2 months on a live platform handling real regulatory data, so downtime and inconsistency weren't options. The team took an incremental approach — standing up REST endpoints alongside the existing GraphQL layer, validating parity, then cutting over integrations gradually rather than in one hard switch. šŸš€ What shipped A production REST API layer that opened EarnDLT up to third-party emissions-data providers, with no disruption to the platform's live CBAM/Scope 3 compliance reporting.
0
42