Developed scalable Golang microservices and REST APIs for workflow automation, backend integrations, and incident orchestration systems.
Worked on:
• REST/gRPC API development using Gin & Gorilla Mux
• JWT authentication and request validation
• Concurrency implementation using goroutines and worker pools
• Cron jobs and backend workflow automation
• Docker-based deployment and CI/CD integration
• API optimization and monitoring using Splunk/AppDynamics
Think about how much time you spend every week doing the same things.
Replying to customer emails.
Following up with potential clients.
Updating spreadsheets.
Managing leads.
Moving information between applications.
Sending reminders and notifications.
Picture a consultant who takes 8 sales calls a week.
After each one comes the same routine: replay the recording, write notes, update the pipeline sheet, write the follow-up email. Call it 30 minutes a call. That is 4 hours a week, and on busy days the follow-up slips to tomorrow.
I built an n8n workflow that takes that routine away:
→ Fireflies records and transcribes the call
→ As soon as the transcript is ready, AI writes a summary, the open questions, the next step and whether the prospect is ready to go ahead
→ A follow-up email that fits that outcome is saved in Gmail drafts, addressed to the person on the call
→ The call is logged in Google Sheets and the notes land in your inbox
Nothing is sent automatically. You read the draft, change a line if you want, and press send.
For that consultant, 4 hours of admin a week turns into a few minutes of reading, and every prospect hears back the same day.
I tested it on a real recorded client call and have submitted it to the n8n template library as a free template. If you want it set up for your business, send me a message.
As a front-end engineer at GitStart (YC S19), I built core features for AlaanPay, a payment platform from Alaan ($55M raised). I added full Arabic and English support, including right-to-left (RTL) layouts, and built real-time transaction features used by tens of thousands of users.
“Wajiha over-delivered; she wrote great code across both frontend and backend.” – Timothy Olunsaya
What needed the most care in the Arabic version—mirroring the layout, or keeping things like amounts and transaction references readable alongside Arabic text? I'd be curious which details were easiest to miss.