Full Stack Web Developer | n8n & AI Automation Engineer,PHP
- $1k+
- Earned
- 1x
- Hired
- 5.0
- Rating
- 100
- Followers
Full Stack Web Developer | n8n & AI Automation Engineer,PHP
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
245
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
116
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
112
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
260
Full-Stack Engineer Delivering Secure and scalable Systems
Full-Stack Engineer Delivering Secure and scalable Systems
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
55
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
78
-> 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
253
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
68
Converting ideas to digital products/solutions 💻
- 1x
- Hired
- 5.0
- Rating
- 2
- Followers
Converting ideas to digital products/solutions 💻
Delivering Efficient Fullstack Solutions
Delivering Efficient Fullstack Solutions
Backend Engineer | Node.js, NestJS, TypeScript & AWS
Backend Engineer | Node.js, NestJS, TypeScript & AWS
"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
222
So today, I was going through our product, SabiMoney, and decided to see how far Lovable’s redesign skill could take the UI.
On the right: the original version I designed with Lovable earlier this year.
On the left: the redesigned version using Lovable’s redesign skill.
The difference is honestly huge.
Same product. Same core functionality. Completely different visual experience.
The redesign feels cleaner, more intentional, more modern, and significantly more polished.
0
28
What if the biggest risk in a visa application isn't a missing document but a contradiction between documents that nobody noticed?
That was the problem I needed to solve for VisaGuide, a platform working with a visa agency based in Hungary.
The business wanted applicants to upload their visa documentation, identify potential inconsistencies, understand what needed attention, and receive an Embassy Readiness Report before submission.
Rather than expecting one AI model to handle everything, I broke the problem down and assigned each tool a specific responsibility.
Here was my approach 👇
1. Azure Document Intelligence —> The Extractor 📄
First, I needed to turn uploaded documents into structured data.
The OCR and document extraction layer processes the documents and extracts relevant fields that can be compared across different sources.
2. ElevenLabs —> The Interview Simulator 🎙️
Documents alone don't always provide the full picture.
I included ElevenLabs for a virtual interview simulation, creating another way to collect information from applicants and complement the data extracted from their documents with option to switch to a manual progressive form.
3. Gemini —> The Auditor 🧠
This is where the different pieces come together.
Gemini receives the extracted document data alongside the information collected through manual forms or the interview workflow. The goal is to analyze the combined information, flag potential discrepancies, and produce actionable recommendations.
The output is an Embassy Readiness Report containing:
A readiness score.
Potential inconsistencies and issues requiring review.
Recommendations on what needs to be corrected, clarified, or aligned.
The architecture
User-uploaded documents → Azure Document Intelligence → Structured document data
Applicant information → Manual forms / ElevenLabs interview → Collected data
Structured document data + collected data → Gemini → Readiness score + issues + recommendations
What interests me most about this solution isn't simply the use of AI. It's the orchestration: combining document intelligence, conversational data collection, and AI-powered analysis into one business workflow.
Because building useful AI products isn't just about choosing the most powerful model.
It's about knowing which problem each tool should solve, what data should flow between them, and how to turn the output into something people can act on.
The objective is to help applicants and visa professionals catch avoidable documentation inconsistencies earlier not to guarantee visa approval or replace professional judgment.
I'm curious: if you were architecting this system, what would you add to make the analysis more reliable rule-based validation, confidence scoring, human review, or all three?
#BackendEngineering #AIEngineering #SystemDesign #DocumentIntelligence #SaaS
0
41
Project Overview
VisaGuide is a web platform designed to simplify visa application preparation through guided workflows, document organization, and intelligent readiness checks.
The platform helps applicants navigate the preparation process step by step, identify missing or inconsistent information, and prepare supporting documents before submitting their applications.
The Challenge
Visa applicants often struggle with complex requirements, scattered documentation, lengthy application forms, and inconsistencies between their answers and supporting evidence.
The goal was to deliver a more structured digital experience that guides users through the preparation process and makes outstanding requirements easier to identify.
Key Product Capabilities
Guided application workflows: Structured, adaptive questions based on the applicant's visa journey and previous answers.
Document management: Upload and organize supporting evidence for an application.
Readiness checks: Identify missing information and potential inconsistencies between responses and uploaded documents.
Document drafting: Generate supporting-document drafts from applicant-provided information for review and editing.
Application progress tracking: Help users understand their progress and outstanding requirements.
Destination-specific workflows: Organize visa preparation requirements around the selected destination and visa category.
Engineering Focus
The project demonstrates the engineering considerations involved in building a workflow-driven web application, including structured application data, conditional flows, document-related processes, and the coordination of multiple stages in a user journey.
Outcome
A live visa preparation platform that brings guided interviews, supporting-document preparation, and application-readiness checks into one user experience.
Live website: https://www.myvisaguide.app/
VisaGuide provides application preparation guidance, not legal advice or guaranteed visa outcomes.
1
98
Replit App Design | Brands, Websites and Full-Stack Web Apps
Senior Web Developer | Node JS | React JS | Next JS
Senior Web Developer | Node JS | React JS | Next JS
Fullstack Wizard: React Native & Next.js Expert
Fullstack Wizard: React Native & Next.js Expert
