Backend and APIs
Data models, REST APIs, authentication, validation and business rules. Endpoints for portals, administration and connected applications.
Backend and internal systems
Backend, customer portals and admin systems
I build web applications for customers and internal teams, from a user portal or operator workspace to data collection, calculations and exchange with external APIs.
What I can help with
Customer portals
Profiles, roles, permissions, work areas and activity history. Distinct journeys for customers, staff and administrators within one service.
Operational interfaces
Registries, search, filters, bulk actions, statuses and detailed records. The information and controls operators need to carry out daily work.
Data collection and processing
Ingesting data from APIs, files and public sources, then normalising, matching, storing history and finding duplicates. Processing stages with visible status.
Reports and exports
Date ranges, queries, calculated metrics, notes and exports. Historical backfills and checks for differences between source records and reports.
Development of an existing system
Reviewing the code and database, fixing defects, adding roles and workflows, extending integrations and diagnosing performance without requiring a complete rebuild.
Relevant experience
Pro Maps: data and reporting
The system connects multiple analytics accounts through OAuth, collects Yandex Metrica data, backfills historical periods through a retryable queue and prepares reports for PDF export.
Events administration
A WordPress administration area brings together event search, registration and payment counts, attendance, email templates and QR materials.
Lead qualification: work in progress
A separate application is being developed to ingest company lists, inspect public websites, extract contacts and business signals, score prospects and explain their inclusion in a shortlist. This project is still in progress.
Selected work in this area
Pro Maps: Metrica, OAuth and reporting queue
Multi-account statistics, token refresh, retryable historical imports and client reporting.
View project details
Managing events, payments and attendance in WordPress
A dedicated admin area with payment and attendance metrics, search, sorting, QR communications and configurable email templates.
View project details
B2B lead qualification: from website crawling to shortlist
Contact and signal collection, explainable scoring and preparation of a prioritised company list for outbound work.
View project detailsHow the work is delivered
Assessment and scope
We define the process, source data and expected result. For an existing project, I review the affected code. We then agree scope, cost and milestones.
Development and verification
I implement the agreed workflows and check the result and its dependencies. Changes to live systems account for data integrity and neighbouring functionality.
Release and continued support
I prepare the deployment and rollback procedure and verify the result after release. I hand over the changes and we agree further support where needed.
What you receive
- The agreed portal, API and administration workflows.
- Checks of roles, data, operations and reports along real user journeys.
- Source code, an overview of the structure and a release procedure.
Before we start
Can you build an application without a CMS?
Yes. If a packaged platform constrains the data model or workflows, I can design a standalone application. The stack is chosen after reviewing the requirements and existing infrastructure.
Can you extend a live customer portal?
Yes. I first review its roles, data, routes and integrations. We then define the change and check adjacent workflows.
How do you handle different user permissions?
We map roles to data and actions: who can see a record, change a status and review previous actions. Those rules are enforced in the backend and reflected in the interface.
Can reports combine several external data sources?
Yes. Each source needs a format, identifiers, refresh schedule and update rules. Failed imports and unmatched records remain available for investigation.
Describe the workflows your portal or internal system needs to support.
Tell me about your project
No passwords or access credentials are needed for an initial assessment. Send a project link, briefly describe the current and expected behavior, and include a timeframe or budget if already defined.