Posted today · be early
Product Engineer
CentralApp
IndiaremotePosted today
Skill Required
Product-EngineeringFullstack-DevelopmentSoftware-EngineerFrontend-DevelopmentBackend-DevelopmentProduct-EngineerProduct-Development-EngineerProduct-Design-EngineerProduct-Software-EngineerDeveloperHardware-EngineerObservabilityWeb AccessibilityPrototypingEngineeringdevelopingWordPressdebuggingNode.jsTestNGdesignReactAPIsAWSSEOandAIFulltime
Key highlights
- Remote-first role (Preferred timezone: anywhere between London and Singapore)
- Notable requirement: Your strongest execution layer should be backend & dev ops, and you should be able to review Haskell code independently
Role overview
CentralApp (soon rebranding) is moving away from a template-first approach (such as Wordpress or Wix) to develop an innovative method for website creation, integrating pre-designed business modules and a branding engine. Their solution is used by thousands of businesses across Europe, alongside a suite of additional tools designed to enhance business impact.
Responsibilities
- Turn ambiguous product problems into clear user flows, product behavior, edge cases, and success criteria.
- Build and maintain scalable, modular, high-performance frontend code.
- Review backend and frontend implementation independently across UX, code quality, performance, accessibility, maintainability, and product correctness.
- Define API contracts and backend expectations clearly.
- Collaborate with backend engineers on architecture, data models, permissions, error handling, observability, and performance.
- Use AI tools to accelerate prototyping, implementation, refactoring, testing, debugging, and technical exploration.
- Critically review AI-generated output and stay accountable for correctness, maintainability, and product quality.
- Balance speed, simplicity, performance, maintainability, and user experience.
- Keep the end user, business impact, SEO, accessibility, and product quality in mind.
Requirements
- You want to own outcomes end to end: clarify the problem, define the product behavior, implement the frontend, coordinate backend work (or even develop it depending on which service we need to act on), and ship.
- You are strong enough in frontend to review React code independently, while also reasoning about APIs, data models, permissions, backend constraints, and edge cases.
- You use AI to move faster, but still trace the logic, adapt the output to the codebase, and verify the result before it reaches review.
- Your strongest execution layer should be backend & dev ops.
- You should be able to review Haskell code independently and maintain a high bar on performance, accessibility, maintainability, and product correctness.
- You need to be able to reason about front-end constraints, including UX and be able to implement Front-end parts of the project you will work on.
Benefits
- Remote-first role, with flexibility in how and where you work.
- Preferred timezone: anywhere between London and Singapore
- High ownership: you will have real influence over product direction, technical decisions, and the evolution of the stack.
- Flexible working setup, focused on output, autonomy, and impact rather than rigid process.
- Opportunity to work across product, design, frontend, backend architecture, and AI-assisted engineering workflows.
- Small, experienced team where strong contributors can move fast and have visible impact.
Additional details
- This is not a narrow frontend role or backend role
- You do not need to be a production front-end engineer aswell (AI will do the translation, or frontend focused colleague can help)
- Current stack: Our backend includes Haskell services and Node.js; Our frontend stack includes: React, including server-side rendering and Node.js; Our infra is AWS focused.
- This role is not for you if: You want a pure frontend implementation role with detailed tickets, finalized designs, and predefined APIs.
- This role is not for you if: You expect product managers, designers, or backend engineers to make the hard product and technical decisions before you start.
- This role is not for you if: You prefer narrow specialization, heavier process, or avoiding ownership of backend or UX constraints, edge cases, and AI-assisted output quality.
- Originally posted on Himalayas
