Product engineering / FlexyPack
A Custom Recruitment System for FlexyPack
A purpose-built WordPress recruitment platform designed and developed from the ground up, with custom code and business logic supporting FlexyPack's hiring workflow.
Work / Sultan Kautsar
Systems built, extended, and kept operational.
Selected work across product platforms, recruitment, campaign engineering, and measurement infrastructure.
Selected work / 01
Project records with the surrounding context left in.
The work ranges from systems built from the ground up to multi-stack maintenance and consent-aware measurement.
01
Custom WordPress / Recruitment workflows / Business logic / Server operations
Read case study02
Web and campaign engineering / FlexyPack
FlexyPack's Web Platform and Localized Campaigns
A web platform built from the ground up and extended with focused landing pages for product-, region-, and market-specific advertising.
WordPress / Localized landing pages / GA4 and GTM / Server operations
Read case study03
Measurement engineering / MediaConversion and client projects
Consent-Aware Conversion Tracking
End-to-end GA4, Google Tag Manager, and Google Ads conversion tracking with Consent Mode v2 across MediaConversion, YogaBali, and Ihr Umzugsplaner.
GA4 / Google Tag Manager / Google Ads conversions / Consent Mode v2
Read case study04
Platform engineering / Rucika
Maintaining Rucika Across WordPress and Next.js
Ongoing technical management across Rucika's WordPress presence and the custom Next.js stack behind Rucika Institute.
WordPress / Next.js / Maintenance / Platform operations
Read case study05
Independent project / Rayatiga
Reframing Rayatiga as an Independent Project
A rebuilt digital presence that preserves the Rayatiga identity while moving the former business site into an independently maintained project.
Web development / Brand continuity / Deployment / Independent product
Read case study
Evidence / 02
The structure makes each claim easier to evaluate.
Each record follows the same boundaries so ownership is clear and presentation does not replace evidence.
01
Context
The problem, operating environment, and constraints that made the work necessary.
02
Role and scope
A precise account of responsibility, boundaries, and the parts of the system involved.
03
Technical decisions
The architecture, implementation choices, tradeoffs, and reasoning behind the approach.
04
Result
The outcome and available evidence, presented without inflated metrics or implied attribution.
Collaboration / 03
Have a system or difficult technical problem in view?
Start a direct conversation about the context, constraints, and work involved.
Contact Sultan