Job Description

Role Positioning in iDynamics

This role is not a developer upgrade — it is a technical leadership role accountable for architecture outcomes.

•  Sits at the same leadership layer as HODs (PS, Support) in terms of influence
•  Owns technical architecture standards across delivery
•  Acts as the bridge between strategy (what to build) and delivery (how to build it right)
•  Critical in building iDynamics Integration IP (middleware layer, connectors, frameworks)

Role Objective (Why This Role Exists)

To design, standardize, and scale integration architecture across all customer implementations, transforming iDynamics from:

project-based custom integration

→ into

reusable, structured, IP-driven integration platform

Key Responsibilities (Outcome-Focused)

1. Architecture Ownership (Core Accountability)

•  Own the end-to-end integration architecture for AutoCount and other systems
•  Define standard integration patterns (API, middleware, sync models)
•  Ensure all solutions are:
• Scalable
• Maintainable
• Reusable (not one-off builds)

1. Middleware & IP Development

•  Lead development of iDynamics Middleware Layer (Node.js / Express)
•  Experience in the Frontend tech stack (React) and UX experience design
•  Drive creation of:
• Standard connectors (WMS, CRM, eCommerce, POS)
• Reusable integration modules
•  Convert project learnings into productized assets (IP)

1. Delivery Governance & Quality Control

•  Establish coding, integration, and documentation standards
•  Review solution designs before implementation (Design Authority role)
•  Ensure:
• Minimal rework
• Low defect leakage
• Stable deployments

1. Cross-Functional Leadership

•  Work with:
• PS Team → ensure implementable designs
• Support Team → ensure maintainability & support readiness
• Strategic Team → align architecture with future direction
•  Act as escalation point for complex technical issues

1. Team Capability Building

•  Mentor developers and elevate them from:

task executors → solution thinkers

•  Instill:
• Structured thinking
• Documentation discipline
• Ownership mindset

1. Continuous Improvement & Scalability

•  Reduce dependency on “key person knowledge”
•  Build repeatable frameworks
•  Improve:
• Delivery speed
• Solution consistency
• Team productivity

KPIs (Operational – Measurable)

Delivery & Quality

•  % of projects using standardized integration architecture
•  Reduction in custom one-off integration builds
•  Post-go-live defect rate related to integration
•  Rework rate due to poor design

Efficiency

•  Average integration delivery time reduction (%)
•  Reusability rate of existing connectors/modules
•  Number of projects supported per architect

System Stability

•  Integration-related support tickets (trend ↓)
•  Critical incidents caused by integration failures

Job Requirements

 Technical

•  Strong expertise in C# / .NET (integration-heavy environment)
•  Proven experience in system architecture / solution design
•  Deep knowledge of:
• REST APIs, Webhooks
• JSON / XML
• Integration patterns (event-driven, async, sync)
•  Experience with:
• Node.js, Express (middleware design)
• React (frontend design)
• Database design & data transformation

Domain Advantage

•  Experience with AutoCount or similar ERP/accounting systems
•  Exposure to:
• WMS
• CRM
• POS / Retail systems
•  Understanding of real-world business process flows
•  Strong knowledge on design and build multi tenant software from scratch

Leadership

•  Experience in leading technical teams or acting as design authority
•  Strong decision-making capability (not just suggesting — deciding)
•  Able to challenge both:
• Engineers (technical quality)
• Business (unrealistic expectations)
•  Malaysian Citizens only

Skills