Freelancers using Node.js in Federal Capital Territory

Freelancers using Node.js in Federal Capital TerritoryFreelancers using Node.js in Federal Capital Territory

Projects People

Full Stack Web Developer | n8n & AI Automation Engineer,PHP

$1k+: Earned

1x: Hired

5.0: Rating

91: Followers

Full Stack Web Developer | n8n & AI Automation Engineer,PHP

Cover image for Seamlessly Automate Data Integration and Reporting with n8n

n8n Automated Workflow: Built a production-ready n8n automation workflow that fetches data from a REST API, transforms and processes 100+ items, then splits into two parallel pipelines. The upper branch filters records by user, aggregates data per user, generates a CSV report, and writes it to disk. The lower branch prepares a full JSON export, saves all posts, builds a summary report, and writes it to file. Demonstrates API integration, data transformation, conditional filtering, aggregation, and automated file-based reporting, all orchestrated in n8n with zero manual intervention.

1

195

Cover image for AgriSignal is a digital platform

AgriSignal is a digital platform that helps farmers quickly declare crop treatments and automatically notify nearby residents. It ensures legal compliance, improves transparency, and replaces manual reporting with a fast, map-based system connecting farmers and communities. https://agrisignal.fr (https://agrisignal.fr/)

1

78

Cover image for Scan, import, and search all

Scan, import, and search all your documents right from your phone. No cloud, no subscriptions, no data ever leaving your device. https://docuradar.com

1

72

Cover image for I've set up automations for

I've set up automations for dozens of businesses. These three pay for themselves faster than anything else. And most companies are still doing them manually. 1. Speed-to-lead response. A potential customer fills out your form. What happens next? In most businesses: nothing. For hours. Sometimes days. The data sits in a form submission folder. Someone checks it 'when they get a chance.' By then, the lead has already talked to a competitor. 2. The invoice-to-cash pipeline. Most businesses send invoices manually. Then they forget to follow up and wonder why cash flow is tight. 3. The Monday morning report nobody has to build. Someone on your team spends Friday afternoon pulling numbers into a slide deck or spreadsheet. Every single week. Three automations. Maybe 2 weeks of setup total. Months of time saved every year.

1

3

213

Replit App Design | Brands, Websites and Full-Stack Web Apps

New to Contra

Replit App Design | Brands, Websites and Full-Stack Web Apps

Cover image for Startup Networking Platform Development

Startup Networking Platform Development

4

8

Cover image for Beezy Mobile Scheduling App Development

Beezy Mobile Scheduling App Development

4

9

Cover image for TrustedRV Marketplace MVP Enhancement

TrustedRV Marketplace MVP Enhancement

4

7

Cover image for AI-Powered Financial Analysis Platform Development

AI-Powered Financial Analysis Platform Development

4

8

Full-Stack Engineer Delivering Secure and scalable Systems

Full-Stack Engineer Delivering Secure and scalable Systems

Cover image for Architected and delivered a semi-decentralized

Architected and delivered a semi-decentralized USDT ↔ KRW trading platform, balancing centralized compliance controls with decentralized transparency to enable secure, real-world crypto–fiat exchange in a regulated market. Co-designed a regulation-friendly transaction flow with product and compliance, enabling secure on-/off-ramp operations tailored to Korean financial regulations and reducing manual review overhead. Led multilingual localization (Korean/English), expanding regional adoption and driving a 40% increase in active users within the first year of launch. Optimized frontend performance and API design, cutting page load time by 35% and improving transaction completion rates through reduced latency and error handling. Owned end-to-end development across React, Node.js, and MongoDB, ensuring production-grade scalability and reliability for high-volume financial transactions with sub-second response times.

0

18

Cover image for Finditor — Engineering in Practice
Built

Finditor — Engineering in Practice Built Finditor to solve a simple but expensive problem: people and businesses have financial data, but often lack the systems to turn that data into clear decisions. As the Full-Stack Systems Engineer, I designed and built the product across the stack from frontend experience and backend architecture to data processing, APIs, database design, security, and infrastructure. The goal isn't just to make software that works. It's to build a system that turns complex financial data into actionable intelligence, while remaining reliable, scalable, and maintainable as usage grows. Finditor is a practical example of how I approach engineering: solve the business problem first, then build the system that can support the solution.

1

47

Cover image for

-> Re-engineered the frontend architecture

-> Re-engineered the frontend architecture by upgrading Next.js and introducing TypeScript, improving application performance by 30% while strengthening type safety and maintainability. -> Integrated frontend features with backend APIs and authentication services, implementing protected routes, role-based access control, dynamic data flows, and API-driven functionality. -> Engineered 5+ core workforce management workflows covering staff scheduling, employee operations, client management, reporting, and administration for the platform. -> Contributed to the platform's PWA and mobile application experience using Capacitor, extending workforce management workflows from desktop web to mobile devices. -> Collaborated closely with backend engineers and product stakeholders to turn evolving requirements into functional product workflows, resolve integration issues, and continuously refine the user experience.

1

137

Cover image for WelliRecord - Co-Founder &

WelliRecord - Co-Founder & Full-Stack Systems Engineer Building patient-owned health data infrastructure designed for Africa. I lead the architecture and engineering of a health record platform that allows patients to securely carry their medical history across hospitals, reducing fragmented care and unnecessary repeated tests. Key systems I engineer: Patient-owned health data vaults Provider workflows for queues, triage, and clinical encounters Multi-organization access control for healthcare providers Secure and interoperable health data infrastructure I design and engineer reliable healthcare systems that keep patient data accessible even in low-connectivity environments, helping providers reduce fragmented records, repeated tests, and delays in care. Through strong system design, scalable architecture, and secure data infrastructure, I build solutions that connect healthcare workflows, improve data accessibility, and give organizations the technology they need to deliver better patient care.

1

47

Converting ideas to digital products/solutions 💻

1x: Hired

5.0: Rating

2: Followers

Converting ideas to digital products/solutions 💻

Cover image for Kantisoft: Multi-Tenant POS Application

Kantisoft: Multi-Tenant POS Application

0

12

Cover image for Full Functioning E-commerce application

Full Functioning E-commerce application

0

12

Cover image for A Cool Drift Landing Page Design

A Cool Drift Landing Page Design

0

14

Cover image for E-Commerce Software

E-Commerce Software

0

6

Delivering Efficient Fullstack Solutions

Delivering Efficient Fullstack Solutions

Cover image for Express User Manager

Express User Manager

0

8

Cover image for simplicity-js/simplicity

simplicity-js/simplicity

0

8

Cover image for smart-form-validator

smart-form-validator

0

9

Placeholder project card media

View more →

OBI PASCAL BANJUARE

proAbuja, Nigeria

CTO - blending AI, product, code, and DevOps to build apps.

CTO - blending AI, product, code, and DevOps to build apps.

Cover image for "If money touches your system,

"If money touches your system, a ledger should touch it first." Your backend should be ledger-first by design. If there's even a 0.00001% chance that money, balances, fees, commissions, credits, refunds, rewards, or anything involving an amount will flow through your system, every movement should be recorded in a ledger using double-entry accounting principles. This isn't just for banks, fintechs, or payment processors. Whether you're building: =>A payment rail => An e-commerce platform => A marketplace => A grocery delivery app => A subscription service You need to be able to answer: > Where did this money come from? > Where did it go? > Who owns it right now? > Why did this balance change? > Can we prove it months or years later? A ledger provides an immutable audit trail, complete traceability, and financial correctness. It eliminates balance drift, simplifies reconciliation, and gives your team confidence when investigating disputes or anomalies. You don't need to hold funds to need a ledger. The moment your system represents value, tracks balances, calculates fees, records payouts, or reports financial activity, you're already dealing with accounting. Design for auditability from day one. Retrofitting a ledger later is one of the most expensive engineering decisions you'll make.

1

122

Cover image for I’ve been building SabiFlow for

I’ve been building SabiFlow for a while, and honestly, the most interesting part of the project isn’t the code. It's the problem. Because it's personal. I've experienced that thing where money comes in and somehow, without you really noticing, it starts disappearing. Not because you don’t earn enough. Not necessarily because you're irresponsible either. Sometimes money simply has no job when it arrives. And as an engineer, that got me thinking: What if the problem isn't budgeting? What if the problem is that we’re asking people to make too many good decisions at the exact moment they have the most temptation to make bad ones? That question became the foundation for SabiFlow. Instead of telling someone, "You should save 20% of your income," I started thinking about what would happen if the system simply helped assign every inflow a purpose the moment it arrived. That led me down a rabbit hole. Funnels. Automated distribution. Wallet infrastructure. Virtual accounts. User behaviour. Transaction flows. KYC. Compliance. Even the psychology behind notifications. And this is probably my favourite part of being both an engineer and a founder. I don’t just ask: "How do I build this feature?" I ask: "Why does this problem exist, and what kind of system could make dealing with it easier?" Then the engineer in me comes along and asks: "Okay… but how do we actually make this work reliably?" 😂 That tension between the founder thinking about the problem and the CTO thinking about the system is probably what I enjoy most about building SabiFlow. I’m still figuring a lot of it out. But I'm curious: What’s a problem you’ve experienced personally that eventually made you want to build something around it?

0

1

Cover image for One of the most expensive

One of the most expensive lessons I learned building fintech products wasn't about APIs, infrastructure, or scaling. It was about data types. Years ago, while building a bill payment startup, I discovered we had silently lost over ₦3 million to fractional rounding issues. No hacks. No fraud. Just floating-point arithmetic doing exactly what it was designed to do. The Facts In JavaScript, numbers are stored as floating-point values. That means something as simple as: 0.1 + 0.2 doesn't equal 0.3. It equals: 0.30000000000000004 For a shopping cart, that tiny difference may not matter. For a fintech system processing thousands of transactions daily, those tiny fractions accumulate into real money. What I Initially Did Like many developers, I used decimal currency values directly: It looked clean. But calculations, fee deductions, settlements, and balance updates gradually introduced rounding inconsistencies. Over time, the system started leaking funds through fractions. What Fixed It I switched to storing monetary values in the currency's smallest unit using BigInt. Instead of: Store: Now every operation becomes integer math. No hidden fractions. No rounding surprises. No disappearing money. Pros - Precise calculations - Predictable accounting - Easier reconciliation - Safer ledger systems Cons - Requires conversion when displaying values - Slightly more discipline from developers - BigInt cannot be mixed directly with Number types Do's > Store money in the smallest currency unit (Kobo, Cents, etc.) > Use BigInt or dedicated decimal libraries where appropriate > Convert only at the presentation layer > Build your ledger around integer arithmetic > Never convert BigInt to number on runtime to perform arithmetic operation. Perform the arithmetic operation on the BigInt Type. You can build an api transformer layer to return response in the integer form or leave value in the smallest unit while frontend do the conversion by dividing the value by 100. Don'ts X Store money as floating-point values X Compare currency values using decimal calculations X Round repeatedly during transaction processing X Assume tiny fractions won't matter Fun Fact This is the same principle used by companies like Stripe. Amounts are represented in the smallest currency unit (such as cents) rather than floating-point dollars. Wrap Up In fintech, every fraction belongs to someone. If your system cannot account for every smallest unit of currency, eventually those fractions become real losses. The best time to fix monetary precision is before your first transaction. The second-best time is today.

0

29

Cover image for When you're a FinTech Engineer

When you're a FinTech Engineer and you're excited about AI. A called around 11pm NGT and said: Friend👱‍♂️ : Hey Obi, I've got this client from Canada there want an AI Fitness app Its really an exciting project you should add it to your portfolio. At first I was a bit reluctant, but after a lot of persuasion as someone who enjoys working with me, he keeps talking about the project every single opportunity he has for a good friendly conversation. I finally agreed! 4-months down the line - Find Your Fitness was born! As a Sr. Engineer on the team, one of my core responsibility was to coordinate the project from spring planning, task assignment and follow-ups on ticket to make sure the team were on track with schedule. Jira was my home screen 😂 every morning 😭 . The design team where my friends heading did a great job, but I almost got a heart attack at one time 😂 . It was an exciting adventure indeed, am glad I took my friend up on the offer.

0

56

Opeyemi Aderemi

Senior Web Developer | Node JS | React JS | Next JS

Senior Web Developer | Node JS | React JS | Next JS

Cover image for CaseBeautify

1

4

Cover image for Omnifood - Just Think It!

Omnifood - Just Think It!

1

6

Cover image for Trendly

1

5

Placeholder project card media

View more →

Fullstack Wizard: React Native & Next.js Expert

Fullstack Wizard: React Native & Next.js Expert

Cover image for Front-end Developer

Front-end Developer

0

7

Cover image for E-commerce Mobile App

E-commerce Mobile App

0

10

Cover image for Personal Finance Tracker

Personal Finance Tracker

0

8

Placeholder project card media

View more →