Maulana Irfan Firdian
Frontend Developer
TypeScript
Node JS
Python
JavaScript
Go
API Design: 5/10
Data Layer & Database: 5/10
System Architecture: 4/10
Download CVCV
Overview
Technical skills
Timeline
Roles
Overview
Fullstack engineer (senior-level judgment) focused on building practical SaaS features and integrations with a strength in stateful backend-to-frontend data flows. The strongest proven skill is server-side state and integration design backed by migration and transactional logic in scripts like scripts/migrate-component-schemas.ts and API routes that include validation and auth checks. Public code shows limited explicit accessibility engineering and little evidence of large-scale measured performance tuning or a bespoke component design system.
Phone
Technical skills
Languages
5
TypeScript
Node JS
Python
JavaScript
Go
Node JS
7
PM2
Express
Bcrypt
Mongoose
Morgan
Cheerio
Nodemailer
Frontend
11
Tailwind CSS
React.js
Pinia
Nuxt.js
Vuex
shadcn/ui
ESLint
Next.js
Zod
Vue.js
Radix UI
Other
16
Figma
gRPC
Nginx
Cypress
Vitest
Prisma
Dotenv
Docker
Git
Rest API
Vite
Webpack
PostCSS
AppSec
Cryptography
Least Privilege
Timeline
Frontend Engineer
·
Middle
Suteki
·
Full-Time
Maintained and evolved a multi-tenant academic SaaS platform used by universities across Indonesia, covering student, lecturer, operator, learning, and admissions portals. Streamlined frontend delivery by simplifying the QA/branching workflow to reduce duplicate testing and release approvals. Built a reusable component foundation by extending shadcn/ui into configurable production components and backed shared pieces with tests. Standardized code quality with shared ESLint rules, implemented tenant-aware feature flags, and integrated analytics to support campus-level product insights.
React.js
shadcn/ui
ESLint
Frontend Engineer
·
Middle
Billerpay
·
Full-Time
Contributed to the development of a PPOB and white-label platform for digital payment services and CMS solutions for partner management. Worked in a lean team where the frontend setup and component architecture were key to maintaining delivery speed and consistency. Focused on building maintainable frontend foundations and reusable UI patterns to support ongoing feature development.
Frontend Engineer
·
Middle
Lentera Kata
·
Full-Time
Joined at project inception and built the frontend for a creative community platform connecting writers, artists, and readers. Architected the application using Nuxt.js with SSR, establishing structure, reusable components, API integration patterns, and development conventions. Created a reusable component library with Tailwind CSS aligned to a custom design system and implemented major product experiences such as forums, nested discussions, publishing, directories, and merchandise showcases. Supported production releases by configuring Nginx as a reverse proxy and using PM2 with SSH-based deployment workflows.
Nuxt.js
Tailwind CSS
Figma
Nginx
PM2
Frontend Engineer
·
Middle
Bank Saham
·
Full-Time
Maintained and enhanced a production stock trading platform for retail investors, focusing on real-time interfaces and responsive trading workflows. Implemented real-time market experiences powered by gRPC server streaming across quotes, order books, watchlists, and portfolios. Built responsive trading views integrating TradingView widgets with search, filtering, pagination, and portfolio management features. Managed application state using Pinia and Vuex to keep data flow predictable during real-time updates.
gRPC
Pinia
Vuex
Universitas Telkom
Bachelor's Degree ·
Informatics
Middle Backend Developer
Confidence: High API Engineer
Backend Node.js engineer (Middle) focused on building API-driven SaaS and automation tooling with a pragmatic, code-first approach. The strongest proven skill is data modeling and safe schema evolution as shown by the transactional Prisma migration script that reassigns sections, renames duplicates and upserts component schemas (microsite/scripts/migrate-component-schemas.ts). There is limited public evidence of large-scale distributed system design, advanced observability (metrics/alerts) or formalized production-grade resilience patterns like circuit breakers and exponential-backoff retries.
API Design
5/10
How well APIs are designed
Solid REST API patterns with authentication checks, validation and pagination; lacks an explicit versioning strategy and an idempotency/key design for mutating endpoints.
Evidence
affiliator/src/app/api/schedules/route.ts: auth() checks, zod validation and pagination handling
volkpedia-backend/app/api/v1/customer/controller.js: consistent StatusCodes responses and try/catch -> next(err) pattern
microsite/src/app/api/sections/route.ts: standard REST handlers for GET/POST (presence of routes indicates API surface)
Data Layer & Database
5/10
Working with databases
Deliberate schema management and transactional updates via Prisma and careful seeding; mixed patterns with Mongoose services that perform in-place mutations without explicit transactions or optimistic concurrency controls.
Evidence
microsite/scripts/migrate-component-schemas.ts: uses prisma.$transaction, upsert, section reassignment and renames with counts
microsite/prisma/seed.ts: structured seeding, upserts for themes and components
volkpedia-backend/app/services/mongoose/cart.js: population and in-place product.stock updates without an explicit DB transaction
Scalability & Performance
3/10
Handling load and speed
Some practical scalability choices for automation and scraping (rate delays, API fallbacks) but no evidence of caching strategies, rate-limiting, connection pooling tuning or measured performance optimizations.
Evidence
affiliator/scheduler/lib/social/threads.ts: randomDelay between posts and error screenshots to avoid/handle throttling
affiliator/src/lib/products/scraper.ts: multi-step fetch with crawler UA and Shopee API fallback
affiliator/scheduler/package.json: separate scheduler executable indicates decoupled batch processing
System Architecture
4/10
Overall system structure
Modular service boundaries (web app, scheduler, lib modules) and clear separation of db/provider logic; no evidence of explicit inter-service contracts, service discovery, or large-scale distributed design decisions.
Evidence
repository structure: separate projects microsite, affiliator, affiliator/scheduler (top-level separation of concerns)
affiliator/src/lib/contents/providers/openai.ts: provider abstraction for AI backend
microsite/src/lib/db/*: modular DB access layers (components, themes, sections)
Security & Auth
4/10
Protecting data and access
Good basic hygiene: bcrypt for passwords, auth checks on routes, HMAC-style token signing for checkout tokens and webhook verification; some risky artifacts like seeded plaintext demo passwords and a few endpoints doing unsanitized operations.
Evidence
microsite/src/lib/billing/checkout-token.ts: HMAC signing and verifyCheckoutToken functions
microsite/prisma/seed.ts: bcrypt hashed seeds but uses known demo password strings (admin123, demo1234)
affiliator/src/app/api/schedules/route.ts: uses auth() to gate operations and validates request body with zod
Reliability & Observability
3/10
Stability and monitoring
Basic error handling, logs and defensive scripting are present (dry-run, screenshots on failure), but there is limited evidence of structured observability, retries with backoff, circuit breakers, or operational runbooks and metrics.
Evidence
microsite/scripts/migrate-component-schemas.ts: dry-run/force flags, verbose logs and transactional verification
affiliator/scheduler/lib/social/threads.ts: try/catch per post, screenshots on error and storageState persistence
affiliator/src/app/api/schedules/route.ts: try/catch and standardized 500 responses with console.error
Expertise
Backend AI & LLM· Middle
Microservices & API Architecture· Middle
Node.js· Middle
Industries
Commerce· Middle
Sales & Marketing· Middle
Software· Middle
Technologies
Node JS· Middle
Rest API
gRPC· since 2022
Express
Bcrypt
Prisma
Mongoose
Dotenv
Morgan
Nodemailer
Cheerio
Recommendations
- Build multi-tenant SaaS backend features that require schema migrations and transactional data integrity (Prisma migrations, seeders and upserts).
- Implement API integrations and automation pipelines that combine scraping, scheduler workers and provider abstractions (Threads publisher, OpenAI provider).
- Lead Node.js backend services around auth, billing webhooks and provider integrations where module boundaries and request validation matter.
- Harden operational excellence by adding structured logging, metrics, retry policies with backoff, and documented runbooks for scheduler/worker jobs.
Repositories
The developer's experience in this domain has been verified based on AI analysis of the following repositories:
Middle Frontend Developer
Confidence: High Fullstack
Fullstack engineer (senior-level judgment) focused on building practical SaaS features and integrations with a strength in stateful backend-to-frontend data flows. The strongest proven skill is server-side state and integration design backed by migration and transactional logic in scripts like scripts/migrate-component-schemas.ts and API routes that include validation and auth checks. Public code shows limited explicit accessibility engineering and little evidence of large-scale measured performance tuning or a bespoke component design system.
UI Component Architecture
3/10
How interface parts are built
Component boundaries and schema-driven component registry exist but most UI component code is scaffolded or referenced; clear component schema migration and seeding logic shows intent but not extensive custom UI system design in the analyzed human-authored files.
Evidence
microsite/scripts/migrate-component-schemas.ts: canonicalization and transactional upsert logic for components
microsite/prisma/seed.ts: seedAllComponents upsert of COMPONENT_SCHEMAS and display names
Responsive & Cross-browser
2/10
Works on all screens and browsers
Some responsive patterns and theme CSS utilities are present, but there is little evidence of advanced responsive strategies or broad cross-browser feature detection in the inspected files.
Evidence
microsite/src/lib/themeCss.ts: functions to normalize colors and build css vars
volkpedia-backend/app/views/email/invoice.html: responsive media query for mobile layout
Performance Optimization
5/10
Speed of the interface
Measured and purposeful performance-minded patterns appear (streaming AI completions, multi-stage fetch for scraping) but there are no published before/after metrics or large-scale bundling analysis in the inspected artifacts.
Evidence
affiliator/src/lib/contents/providers/openai.ts: streaming chat completion wrapped in a ReadableStream for efficient client-side streaming
affiliator/src/lib/products/scraper.ts: two-stage fetchAsCrawler flow and conditional API fallback to reduce failed scrapes
Accessibility & Semantics
2/10
Usable for everyone
Minor accessibility-aware selectors and role-based queries appear in automation scripts, but there is little evidence of deliberate a11y engineering for custom widgets or CI linting dedicated to accessibility.
Evidence
affiliator/scheduler/lib/social/threads.ts: uses [role] selectors and dialog queries when automating UI interactions
State Management & Data Flow
6/10
Managing data in the app
Strong server-state discipline and non-trivial data flow patterns are present: validation, auth gating, transactional DB migrations, seed scripts, and streaming AI generation indicate real state-machine thinking and defensive data handling.
Evidence
microsite/src/lib/configState.ts: nested value helpers and array item mutation helpers used for editor state
affiliator/src/app/api/schedules/route.ts: session auth, zod validation, ownership checks and guarded CRUD flows
microsite/scripts/migrate-component-schemas.ts: careful transaction-based reassign/delete/rename migration logic
UX & Visual Polish
3/10
Look and feel quality
Mock data, email templates and seeded themes show attention to UX and polish for demos and seeded tenants, but interactive UX elements, advanced perceived-performance patterns or undo/rollback UX are limited in the inspected files.
Evidence
microsite/src/lib/themePreviewMockData.ts: curated preview sections and image assets for live preview
volkpedia-backend/app/views/email/invoice.html: a styled, responsive invoice template for transactional UX
Verified artifacts
Expertise
React· Middle
Modern Web Frameworks· Middle
Frontend AI Integration· Middle
Industries
Commerce· Middle
Sales & Marketing· Middle
Technologies
JavaScript
TypeScript· since 2024 · Middle
Vue.js
Webpack
Nuxt.js· since 2023
Tailwind CSS· since 2023
Next.js
Figma· since 2023
Git
Docker
Nginx· since 2023
React.js· since 2024
Pinia· since 2022
Vite
Radix UI
PM2· since 2023
PostCSS
ESLint· since 2024
Zod
shadcn/ui· since 2024
Vuex· since 2022
Recommendations
- Develop fullstack SaaS features that require Prisma-backed data models, transactional migrations, and Next.js API routes - ideal for multi-tenant admin flows and seeded demo experiences.
- Implement AI-driven content features and streaming endpoints using the existing OpenAI provider pattern and ReadableStream-based responses.
- Build backend scheduler and automation jobs that integrate scraping, publishing and Playwright-based browser automation using the existing scheduler and Threads provider patterns.
- Lead component schema and theme systems work that connects config-state helpers and preview mocks into a more explicit design-system surface and documented component API
Repositories
The developer's experience in this domain has been verified based on AI analysis of the following repositories:
Middle Security Engineer
Confidence: Medium Generalist
Laravel-focused web application developer at a middle level specializing in building RESTful APIs and authorization controls. The strongest proven skill is designing and implementing authenticated, user-scoped API endpoints evidenced by app/Http/Controllers/Api/V1/TaskController.php together with the presence of app/Policies/TaskPolicy.php and app/Http/Middleware/CheckTokenExpiry.php. There is little to no public evidence of vulnerability research, detection or incident response artifacts, comprehensive security testing, or protocol-level cryptographic design.
Vulnerability Analysis
Finding security weaknesses
Not evidenced in public code
Cryptography & Secure Protocols
2/10
Using encryption correctly
Basic framework-level cryptography configuration and use of token/session primitives are present, but there is no evidence of protocol design, key lifecycle management, or cryptographic misuse analysis.
Evidence
config/app.php: 'cipher' and 'key' configuration entries
config/session.php: session cookie settings including 'secure', 'http_only', and 'same_site'
composer.json: requirement of 'laravel/sanctum' indicating token-based auth usage
Offensive Security / Pentesting
Testing by attacking
Not evidenced in public code
Defensive Hardening
3/10
Making systems harder to break
Defensive hardening and secure-by-default patterns are present at the application level (input validation, per-user resource checks, policies, token expiry), but there is limited evidence of systematic hardening, automated security testing or infrastructure/cloud hardening.
Evidence
app/Http/Controllers/Api/V1/TaskController.php: user-scoped queries and Auth::id() checks for CRUD operations
app/Http/Requests/StoreTaskRequest.php and app/Http/Requests/UpdateTaskRequest.php: use of FormRequest validation
app/Http/Middleware/CheckTokenExpiry.php: middleware to enforce token expiry
Detection & Incident Response
Spotting and handling attacks
Not evidenced in public code
Compliance & Threat Modeling
Planning against threats
Not evidenced in public code
Expertise
Application Security· Junior
Technologies
Cryptography
AppSec
Least Privilege
Recommendations
- Develop RESTful APIs and CRUD backends with Laravel and Sanctum, focusing on per-user authorization and predictable API resources and pagination.
- Implement and extend policy-based authorization and middleware (token expiry, rate limiting) to enforce least privilege across endpoints.
- Harden session and cookie configuration and add automated security checks (SAST, dependency scanning) and security-focused unit/integration tests.
- Expand into security engineering tasks such as threat modeling, attack surface analysis, and reproducible vulnerability reports with mitigations.
Repositories
The developer's experience in this domain has been verified based on AI analysis of the following repositories: