2025Case study

Automated Monthly Fee Deduction System

Automation around recurring fee workflows and operational data movement in a fintech backend environment, using Go, PostgreSQL, Python, and ETL-style jobs.

Technologies

GoPostgreSQLPythonETLAutomationFintechBackend

Source code or a live demo is not currently published for this project.

Case study

Proof-oriented project context

These notes focus on context, contribution, technical approach, constraints, and what the work demonstrates for software engineering roles.

Reading map

01Brief
02Delivery evidence
03Boundaries & value

Overview

A backend automation project around recurring fee workflows, operational data movement, and scheduled jobs in a fintech product context.

Problem / Context

Recurring operational workflows can create manual effort and data freshness risk when they are not handled through clear backend automation. The project addressed that kind of workflow while keeping internal financial logic private.

My Role

Built and contributed backend automation around recurring fee workflow steps, scheduled data movement, and supporting scripts.

Technical Approach

Used Go and PostgreSQL around backend account and fee-processing workflows.
Used Python scripts and ETL-style jobs for operational data freshness.
Kept the public description focused on automation boundaries instead of private financial rules.

Key Decisions

Frame the work around backend automation and data movement, not private fee logic.
Use conservative value language because no approved metric is available.
Connect the project to backend developer, PostgreSQL developer, Docker/API-adjacent, and fintech software engineer intent through actual stack and workflow evidence.

Constraints

Private/internal work with no public source code or demo.
No private account logic, financial rules, or operational thresholds should be described.
No reduction metric is stated until Wasif approves a factual number.

Result / Value

The project shows backend automation work that reduces manual handling at a workflow level while keeping data movement and operational behavior easier to reason about.

What This Demonstrates

Backend workflow automation
PostgreSQL-heavy product systems
Go backend development
Python ETL support work
Fintech engineering discipline

Next step

Want to discuss similar backend, API, or full stack work?

I can talk through the public parts of this work, the engineering tradeoffs behind it, and how the same approach applies to recruiters, founders, or engineering teams evaluating reliable software delivery.

Contact Wasif Ali

Continue evaluating the work

Professional experience Software engineering CV Contact Wasif Ali

Related work

2025

Fintech Integration Platform

2024

Buddy - Voice-Activated Assistant