Available for frontend and mobile work
01Field note

Frontend and mobile engineer

I build production-ready web and mobile interfaces that stay maintainable after launch.

I'm Muhammad Iqbal Firdaus, a Frontend Engineer and Mobile Engineer with 2+ years of professional experience and hands-on web development experience since 2022. I've worked across tourism, government, analytics, automotive, restaurant, IoT, and digital media products, using React, Next.js, Astro, and Flutter to turn designs and APIs into performant applications that are easy to ship and maintain.

Available for frontend and mobile work

02Selected work

Proof should be inspectable

Selected work across production web delivery, mobile product engineering, local-first tooling, and operational interfaces.

03Craft

What the work is made of

The practical stack I use most often: frontend and mobile applications, backend APIs, agentic coding, CLI-heavy Linux tooling, and operational dashboards.

  1. 01

    Frontend applications

    React · Next.js · Astro · SolidJS · TypeScript

    Production React, Next.js, Astro, SolidJS, and TypeScript work: turning Figma designs, REST APIs, and existing codebases into responsive interfaces that teams can maintain after launch.

  2. 02

    Mobile development

    Flutter · Dart · React Native · REST API · Sanity CMS

    Flutter and React Native applications for Android and iOS, including feature delivery, API integration, localization, CMS-driven content, production fixes, and migration work.

  3. 03

    Backend & API workflows

    NestJS · Express · Go Gin · REST API · BFF

    Open to backend work around product APIs, BFF layers, authentication flows, and service boundaries. Most comfortable with NestJS and Express, with exposure to Go Gin when a lean Go service fits the problem.

  4. 04

    Agentic coding

    Pi Coding Agent · Code review · Verification · Automation

    Comfortable using Pi Coding Agent as part of the engineering loop: exploring codebases, planning changes, editing with verification, and keeping AI-assisted work grounded in the actual repository.

  5. 05

    CLI-heavy tooling

    Linux · Neovim · CLI · Git · Shell

    Daily workflow is terminal-first on Linux, with Neovim, shell tools, package managers, git, and local dev servers. I am comfortable debugging and shipping without depending on heavy IDE workflows.

  6. 06

    Dashboards & operational data

    MQTT · Firebase · React Query · Recharts · Supabase

    Real-time interfaces for IoT and analytics use cases, with MQTT streams, Firebase data, cached queries, and charts that help users understand operational metrics quickly.

Responsive by default

Layouts, content density, and interaction states are checked across desktop and mobile.

States are part of the UI

Loading, empty, error, and API edge cases are considered before the interface is handed over.

Built to continue

Components, naming, and implementation choices stay legible for the next person in the codebase.

04Method

Working style

A short note on shipping real products

I work best when design, frontend, backend, and product stay close enough to clarify the problem before the interface hardens into code.

My default approach is practical: understand the requirement, map the API shape, build the smallest reliable UI, then improve the details that make the product feel polished on desktop and mobile. I care about responsive layouts, clear states, maintainable components, and performance because those are the things users notice when they go wrong.

Most of my work has been freelance and remote, so I keep communication explicit. I document assumptions, surface blockers early, and try to leave the codebase easier to continue than when I arrived.

  1. 01

    Clarify

    Align on the requirement, user path, constraints, and API shape before UI decisions harden.

  2. 02

    Structure

    Build the smallest reliable component and state model for the actual product workflow.

  3. 03

    Refine

    Bring responsive behavior, loading states, edge cases, and interaction details into the implementation.

  4. 04

    Handoff

    Document assumptions, surface blockers early, and leave the codebase ready for the next change.

Collaboration

Remote-friendly, async by default, direct with clients, designers, backend teams, and IoT teams.

Delivery

Production features, bug fixes, refactors, migrations, and maintenance for existing applications.

Quality

Responsive UI, API edge cases, performance checks, SEO details, and clear handoff notes.

Mobility

Open to relocation and visa sponsorship opportunities.

05Contact

Next step

If you want to talk about a frontend role, mobile project, freelance build, or relocation opportunity, these are the best ways to reach me.

Start a conversation

Email is the fastest route for roles, project briefs, and freelance work.Typically replies within 1-2 business days.

Emailikbakfir@gmail.combest for roles, project briefs, freelance work, and longer conversations about product problemsGitHubgithub.com/ikbakkportfolio code, side projects, and public engineering workPortfolioikbakk.vercel.appthe live portfolio surface for selected work, skills, and contact detailsLinkedInlinkedin.com/in/ikbakkfor recruiting, sourcing, and professional updatesPhone+62 87815509168available for time-sensitive coordination after an initial messageLocationMataram, Indonesiaopen to remote collaboration, relocation, and visa sponsorship opportunities