Arifin Avicena

Backend engineer for APIs, integrations, and automation.

9 years shipping backend systems — e-commerce platforms, data pipelines, and webhook-driven services. Deep PHP/Magento history with active Node.js work for automation and pipelines.

Indonesia (UTC+7) — EU mornings overlap, full APAC day covered.
US teams: async-friendly.

Selected work

Three projects that show how I build: pipelines, integrations, and the boring reliability work in between.

Scraping & Sync Pipeline

Node.js · Puppeteer · Chrome Extension

End-to-end automation of a repetitive multi-system data-entry workflow: crawl → extract → transform → submit → track.

  • Crawled German and Austrian target websites with Puppeteer
  • Chrome extension for operator-driven capture; backend handles validation and transformation
  • Batch submission to third-party platforms — up to 10 records per operation
  • Email-based status sync closed the loop; saved ~10 minutes of manual work per workflow
Engineering depth →

E-commerce Backend at Scale

Magento 2 · PHP · GraphQL · MySQL

Backend for flagship Magento 2 stores: custom modules, payment integrations, and production monitoring.

  • Custom modules for payment workflows on revenue-critical checkout paths
  • GraphQL and REST APIs serving storefronts, third-party integrations, and internal operations
  • Slack monitoring pipeline for production-issue visibility
  • Scope: 3 flagship stores, 5–10 custom modules built or led, business-critical integrations (payments, Google Ads, Slack), project team of ~5 including TL/PM
Engineering depth →

Podcast Automation Pipeline

Automation · AI Content API · PDF Processing

Turned static PDF documents into finished podcast episodes, no manual steps.

  • End-to-end pipeline: PDF ingestion → content extraction and structuring → audio generation via AutoContent API
  • Document-to-content design: the same extract → structure → generate shape as any data pipeline
  • Built for unattended batch operation
Engineering depth →

Experience

9 years, fully remote since 2021, with experience spanning Indonesia, Singapore, and Germany.

Software Engineer — Schutze Web Engineering Pte. Ltd.

Jul 2024 – May 2026 · Remote

Backend and automation work for German clients: the scraping/sync pipeline and podcast pipeline above, plus three Contao sites (trustdino.de, datana.rocks, gansel-rechtsanwaelte.de) — building content elements with HTML, CSS, and Tailwind — and Azure OpenAI chatbot and recommendation features. Also continued existing Next.js work for a client when the previous dev left.

Software Engineer (Backend) — ICUBE by SIRCLO

Feb 2021 – Jul 2024 · Remote

Magento 2 backend for flagship e-commerce stores — custom modules, payment integrations, GraphQL/REST APIs, and Slack ops monitoring (detailed in E-commerce Backend at Scale above).

Web Developer — ECC.co.id

Aug 2017 – Feb 2021 · Yogyakarta

Admin portals, business modules, and REST APIs on Yii 2/MySQL. Optimized SQL and backend logic for faster API responses, replaced legacy iframe integrations with secure REST APIs, and built face-recognition and RBAC features.

About

I'm a backend engineer who gravitates to integration work — the seams between systems where data gets lost, duplicated, or silently dropped. E-commerce backends taught me reliability under real money; automation pipelines taught me to make failure visible. I write TypeScript/Node.js services now, and my PHP/Magento years mean I've already made most of the mistakes once.

Languages
TypeScript · JavaScript · PHP · SQL
Backend
Node.js · REST API design · GraphQL · webhook/event-driven services · MySQL
Integration & automation
Puppeteer · Chrome extensions · third-party API integration · data pipelines · batch processing
Platform & ops
Docker · Linux · Git · CI/CD · Slack ops monitoring
Frontend (secondary)
HTML · CSS · Tailwind · some React/Next.js
Earlier stack (still fluent)
Magento 2 · Contao · Yii 2 · WordPress

Hiring for backend?

I'm in UTC+7 — your EU morning standup is my afternoon, and the whole APAC day is covered. US teams work too if the role is async. Either way, you get an engineer who answers in hours, not days.