Fullstack Engineer Frontend Depth

PT Rakamin Kolektif Madani Yogyakarta, DI Yogyakarta

Deskripsi pekerjaan

Posisi Fullstack Engineer (Frontend Depth) menuntut kepemilikan penuh atas modul lintas seluruh tumpukan teknologi mulai dari antarmuka pengguna (UI), API, data, hingga pengujian. Anda akan membawa setiap fitur dari tahap purwarupa (prototype) hingga menjadi perangkat lunak yang berfungsi dan teruji dengan baik. Fokus utama Anda terletak pada kedalaman di sisi frontend, termasuk modul dengan antarmuka web yang kompleks seperti dashboard, visualisasi data, implementasi sistem desain, dan penyetelan performa (performance tuning) di dalam squad pengiriman kami.

Tanggung jawab: On our delivery squads, every engineer owns a module across the whole stack, its UI, its API, its data, and its tests, and carries it from prototype to working, tested software; Depth is where you go deeper than the rest of the squad, while still owning your module end to end. Your depth is the frontend: the modules with hard web UI such as dashboards, data visualization, design-system implementation, and performance tuning.; From day one, you own real modules on live client squads and on internal product, at a scope matched to your experience: routine-to-common frontend complexity you run independently, with a Technical Lead, a more senior fullstack engineer, or the Prod; What you will do; Own a module across the whole stack: build its UI, the API behind it, its data, and its tests. You finish a whole feature; Take the modules where the interface is the hard part (dashboards, data visualization, design-system work, performance) and go deep there, while still delivering the rest of the module yourself; Build against the hi-fi prototype so a screen matches it exactly. A screen that looks different from the prototype is treated as a bug; Write the tests for what you build, from week one, as continuous regression; Turn a Definition of Done and a clickable prototype into working, traceable software, on real client engagements; Join story kickoffs and walk the acceptance criteria and edge cases before you write code; Use the design-to-code pipeline and AI as leverage, then verify. Producing plausible UI is cheap. Matching the prototype and the persona is the skill; What you own now; Modules built fullstack, end to end, at routine-to-common frontend complexity: UI, API, data, and tests, traced to a requirement and matching the prototype; Your module’s defects and its demo, including at least one dashboard or visualization view a stakeholder actually uses; Who you will work with; Reports to: Technical Lead. Hiring decision: CTO; You get a prototype and a Definition of Done from the product and tech layers, you get design fidelity checks from the Product Designer, and you hand the SDET a module that is testable in CI.

Tanggung jawab

  • On our delivery squads, every engineer owns a module across the whole stack, its UI, its API, its data, and its tests, and carries it from prototype to working, tested software
  • Depth is where you go deeper than the rest of the squad, while still owning your module end to end. Your depth is the frontend: the modules with hard web UI such as dashboards, data visualization, design-system implementation, and performance tuning.
  • From day one, you own real modules on live client squads and on internal product, at a scope matched to your experience: routine-to-common frontend complexity you run independently, with a Technical Lead, a more senior fullstack engineer, or the Prod
  • What you will do
  • Own a module across the whole stack: build its UI, the API behind it, its data, and its tests. You finish a whole feature
  • Take the modules where the interface is the hard part (dashboards, data visualization, design-system work, performance) and go deep there, while still delivering the rest of the module yourself
  • Build against the hi-fi prototype so a screen matches it exactly. A screen that looks different from the prototype is treated as a bug
  • Write the tests for what you build, from week one, as continuous regression
  • Turn a Definition of Done and a clickable prototype into working, traceable software, on real client engagements
  • Join story kickoffs and walk the acceptance criteria and edge cases before you write code
  • Use the design-to-code pipeline and AI as leverage, then verify. Producing plausible UI is cheap. Matching the prototype and the persona is the skill
  • What you own now
  • Modules built fullstack, end to end, at routine-to-common frontend complexity: UI, API, data, and tests, traced to a requirement and matching the prototype
  • Your module’s defects and its demo, including at least one dashboard or visualization view a stakeholder actually uses
  • Who you will work with
  • Reports to: Technical Lead. Hiring decision: CTO
  • You get a prototype and a Definition of Done from the product and tech layers, you get design fidelity checks from the Product Designer, and you hand the SDET a module that is testable in CI

Informasi lowongan

Tipe pekerjaan
Full-time
Gaji
Rp 8.000.000 – Rp 12.000.000 per month
Batas lamaran
19 November 2026

Cara melamar

Lowongan aktif terkait

Lihat lowongan kerja terbaru lainnya