Fares I

Digital Systems Developer

CDG • Vollzeit

Mar 2025 - Present • 1 yr 6 mos

Fares Ibrahim — Technical & Documentation Support B.S. Computer Science, University of Michigan-Flint (2024). Joined CDG as Administrative Assistant in April 2025 — but the role outgrew filing and tracking fast. Most of what Fares does now is build the systems CDG's proposal and reporting work runs on, not just execute it by hand. What he's built A Python reporting pipeline (ReportLab, arabic_reshaper, python-bidi) generating formatted, bilingual Arabic/English PDF timesheet reports across CDG's active projects — with data-quality issues flagged automatically rather than silently corrected. Document automation for proposal production: CVs, technical sections, and compliance documents generated and formatted programmatically (python-docx / docx.js) instead of assembled by hand, cutting turnaround on multi-CV tender packages from days to hours. An internal document management and automation system — centralized cloud-based file storage, version control, and retrieval across CDG's project portfolio. Web-based internal tools with dashboards for tracking deliverable schedules and team activity across concurrent consultancy assignments. Excel-based scheduling automation — Gantt charts and RFP comparison trackers used on live tenders. Before CDG Research Assistant, University of Michigan-Flint (Nov 2023–Apr 2024). Testing, validation, and structured reporting on research tooling; contributed to development task logging and progress-tracking systems. Why it matters to clients CDG's document output is backed by someone with an actual software engineering background — not just formatting skill. In practice that means fewer errors in compiled tender packages, faster turnaround, and real systems behind document production rather than one-off files.

Full-Stack Developer

MoveLink • Selbstständig

Jan 2025 - Present • 1 yr 8 mos

PhysioLink — Physiotherapy Clinic Management Platform Built a production clinic-management platform for physiotherapy practices in an underserved market — replacing paper records and messaging-app chaos with a real digital system for patient management, home-exercise prescriptions, and scheduling. What I built A three-part system: a patient-facing mobile app, an admin panel for clinic staff, and the backend API connecting them. Multi-tenant by design, so multiple clinics run securely on shared infrastructure with strict data isolation between them. Engineering highlights Secure, token-based authentication with role-based access control Clean, layered backend architecture built for long-term maintainability Cross-platform mobile app with real-time notifications and a polished, production-grade UI A licensed video content library integrated into the patient experience, with playback protections Delivery Fully deployed and live, with automated deployment from source control to production. When the standard app-store distribution path hit a regional blocker specific to the target market, I found and shipped an alternative route rather than delaying launch. Outcome A real, multi-tenant SaaS product — architected, built, and shipped end-to-end — now in active use by real clinics.

Full-Stack Developer

Dun and Bradstreet • Freiberufler

Mar 2026 - May 2026 • 2 mos

The Challenge Manoly International Wood, a wood trading company, was running its warehouse on paper logs and Excel spreadsheets -- manual, error-prone, with no real-time view of what was on which shelf, no way to enforce business rules, and no way to keep pace as inventory, staff, and purchase orders grew. The Solution I designed and built a production warehouse management system on Clean Architecture (Domain, Application, Infrastructure, Controllers) with a rich domain model and EF Core Fluent API mappings. It models the warehouse as it actually exists: 432 shelf positions across six rows (A–F) with variable rack capacities, a dedicated staging area, 421+ SKUs across 39 Arabic categories, and the full purchase-order lifecycle, all wrapped in transactional integrity across every multi-table operation. The interface is Arabic-first, right-to-left, and mobile-optimized for warehouse floor use, on a custom Tailwind design system pairing Fraunces serif with IBM Plex Sans Arabic. PDF exports run through QuestPDF. Legacy Excel inventory data was migrated through a Python/openpyxl pipeline using multi-strategy, Arabic-aware product matching. Working With the Client Delivery was phased, with confirmation checkpoints between stages so requirements were validated before I built on top of them, keeping the client aligned throughout. Deployment & Reliability Hosting was migrated from Render.com to Fly.io (Docker) with Neon.tech PostgreSQL. Before go-live, I ran a production-readiness audit that surfaced a subtle EF Core concurrency issue — direct transaction calls conflicting with retry-on-failure logic — that would have broken core operations, plus hardened credential handling across the deploy pipeline. The Result A system now running daily operations for 5–10 warehouse staff, replacing paper logs and spreadsheets with a tool purpose-built around how the client's warehouse actually works.