​​Looking for Philippines-based candidates Job Role: Senior Shopify Plus Developer Work Schedule: This role is expected to align with the AU business hours (approx. 9 AM - 5 PM, Monday to Friday) for collaboration, but as a contractor, you’ll have flexibility in how you manage your time. Compensation range:$2,000 AUD - $3,000 AUD / Monthly (before tax and deductions) Who We Are: At Hunt St, we help Australian companies hire top remote talent in the Philippines. For this role, you will be formally employed through an Employer of Record (EOR) arrangement. We are not an outsourcing agency. All of our roles are 100% remote, so you’ll be able to work from home. Who The Client Is: Our client is an established Australian digital commerce consultancy that helps retailers and consumer brands build, improve, and scale their online businesses. They combine technical development, digital strategy, and customer experience expertise to deliver tailored e-commerce solutions, integrations, and ongoing platform improvements. With growing demand for online store development, they are expanding their technical capabilities to support a diverse range of projects and clients. Role Overview: The Shopify Developer is a senior, hands-on developer who builds and ships Shopify work to a high standard, working to direction set by a Shopify Tech Lead (STL). This is a delivery role rather than a consulting one: the Developer does not own scoping, solutioning with the client, or the client relationship. They own the quality, accuracy and timeliness of what they build. The role is expected to be deeply capable on Shopify Plus: Liquid and theme architecture, the Plus extension surfaces including Checkout UI Extensions and Customer Account Extensions, Functions, Markets, and the Storefront and Admin APIs. Hydrogen and React experience is valuable where middleware, an API proxy layer or headless components form part of a solution. The Developer works within scope that has already been defined, but is not expected to consume a ticket passively. They estimate it honestly, interrogate it for gaps, ambiguity and hidden dependencies before starting, flag anything that looks like scope movement, and test their own work properly before it leaves their hands. Client communication sits with the Shopify Tech Lead and the Project Manager. The Developer is not client-facing, but is expected to be an excellent communicator internally: clear written updates, early flags, and the confidence to challenge a task that does not make sense. This role does not own: client relationships or client communication, scoping and requirements definition, solution architecture, commercial estimates issued to the client, or project coordination. Those sit with the Shopify Tech Lead, the Shopify Solution Architect and the Project Manager. Key Responsibilities: Development Delivery • Build Shopify storefront, theme, app and integration work to the agreed technical approach, meeting Amblique's coding standards and the client's acceptance criteria. • Work from scope and solutions defined by the Shopify Tech Lead or Solution Architect. Deliver to that design, and surface any point where it does not survive contact with implementation. • Deliver across BAU support, dedicated team retainers, mini projects and implementation projects, understanding that the engagement model changes the process and the tolerance for scope movement. • Fix defects raised in QA, UAT and post-go-live on own work within the agreed defect process, distinguishing genuine defects from change requests and raising the latter per Change Management Processes • Support deployment, release and go-live activity for own work, including environment checks and post-release verification. • Triage and resolve assigned incidents promptly, with sound judgment about severity and when to escalate. Estimation & Scope Protection • Produce accurate, defensible estimates for assigned work, including allowance for testing, review and deployment, and provide them within the turnaround agreed with the Shopify Tech Lead & PM. • Interrogate a ticket before starting it. Where requirements are ambiguous, incomplete, or assume work that is not described, raise it before development begins rather than filling the gap silently. • Protect agreed scope. Where a request grows beyond what was estimated or approved, stop and flag it rather than absorbing it. • Flag risk to date or budget as soon as it is visible, not at the point of impact. • Re-estimate and communicate immediately where new information materially changes the effort required. Quality & Developer QA • Test own work before it is handed on: functional testing against acceptance criteria, cross-browser and responsive checks, and regression checks on the areas touched. • Record evidence of developer QA on the ticket so the Shopify Tech Lead and QA can see what was covered and what was not. • Participate in code review, both as author and reviewer, and act on feedback rather than relitigating it. • Treat a defect found in own work after handover as a signal to tighten developer QA, not simply something to fix. • Leave the codebase in a state another developer can pick up: readable, consistent with standards, and documented where behaviour is non-obvious. Internal Process & Communication • Treat Jira as the system of record. Work, decisions, blockers and time logging belong on the ticket, not in chat threads. • Keep tickets accurate as they move. Status and assignee updated whenever work changes hands, and priorities honoured as set, with any proposed reordering raised with the Shopify Tech Lead first. • Log time daily and accurately against the correct ticket. • Resolve confusion at the earliest point. Where direction or priority is unclear, ask in standup or directly rather than proceeding on assumption. • Communicate in writing, clearly and early. A blocker raised at the start of the day costs far less than the same blocker raised at the end of the week. • Escalate properly. If something should be solved and is not moving, raise it with the Shopify Tech Lead & PM, and escalate further if it stays stuck. • Handle client access and data responsibly. Use only the access granted for the account, follow the agreed environment and credential practices, and never move production customer data into local or test environments. • Client communication sits with the Shopify Tech Lead and the Project Manager. The Developer does not communicate directly with clients unless an alternative arrangement is agreed. Technical Standards & AI Enablement • Work to the practice's coding standards, theme architecture and deployment tooling, and feed back where a standard is not working in practice. • Maintain awareness of Shopify platform changes, including API changes and deprecations, and flag implications for the accounts worked on. • Use AI tooling in development in line with the agency's AI-first direction, and contribute to improving how the team applies it. • Engage in internal R&D and capability-building activities during lower-workload periods. Career Path This is a senior individual contributor role, and the most senior development role that is not clientfacing. The pathway from here is to Shopify Tech Lead, where the engagement model allows. Progression is based on demonstrated accuracy, the quality of delivered work, reliability of communication, and a growing ability to hold a technical conversation about a client's wider context rather than a single ticket. Requirements Required Skills and Qualifications: • 5 or more years of hands-on Shopify development, with significant time on Shopify Plus and enterprise merchant configurations. • Deep Liquid and theme architecture capability, including performance-conscious storefront development. • Hands-on experience with Shopify Plus extension surfaces, including Checkout UI Extensions and Customer Account Extensions. • Strong working knowledge of Shopify Functions, Markets, and the Storefront and Admin APIs. • Experience with custom Shopify app development, public and private. • Exposure to third party integration patterns such as ERP, loyalty, fulfilment and POS. • Hydrogen and React experience, particularly where used for middleware, an API proxy layer or headless components, is an advantage. • Understanding of Git workflows and CI/CD deployment pipelines in a Shopify context. • Proven ability to produce accurate estimates and deliver to a defined scope in an agency or professional services environment. • Experience with AI-assisted development tooling such as Cursor. • Excellent written and verbal English: able to explain technical detail clearly in writing and verbally, and to raise problems early and directly. • Comfortable working as part of a distributed team, with sufficient overlap with Australian Eastern business hours for daily collaboration. Reporting Structure • Solid line: Shopify Practice Lead, who owns standards, tooling, workflow and team capability. • Day to day direction: Shopify Tech Lead on each assigned account. The Tech Lead sets the technical approach, assigns and prioritises work, and provides performance input to the Practice Lead. • Works closely with: Shopify Solution Architect, Shopify Tech Lead, Project Managers, Delivery Managers, other Developers, and QA. • Alongside the Project Manager. The Project Manager owns the commercial and delivery wrapper: scope, schedule, budget, resourcing, change control and client reporting. The Shopify Developer surfaces anything that moves date, cost or scope to the Shopify Tech Lead, who carries it to the PM and the client. Where a problem is structural or beyond the Developer's remit, the Tech Lead and PM own the client conversation. Key Performance Indicators (KPIs) • Delivery Performance - Assigned work delivered within estimate and to agreed dates. Blockers raised the day they appear rather than at the point of impact. Incidents actioned within the agreed SLA for the account • Estimate Accuracy - Actual versus estimated variance under 15% on own work, excluding approved scope changes and work paused by external dependency. Estimates provided within the turnaround agreed with the Shopify Tech Lead, with testing, review and deployment effort included rather than assumed away. • Developer QA - Evidence of developer QA recorded on the ticket for all work, covering acceptance criteria, cross-browser and responsive checks, and regression on areas touched. • Technical Lead Feedback - Positive qualitative feedback from the Shopify Tech Lead and Practice Lead on code quality, reliability, responsiveness to review, and clarity of written communication. • Software Quality - Defects attributable to own work are found in developer QA before handover. Under 10% of defects on own work are first raised by the client during UAT or after go-live. Defects found by QA are tracked as a trend rather than a threshold, and are expected to reduce over time. No repeat defects of the same root cause. No unplanned hotfix within 48 hours of a release. • Scope Protection - Scope gaps, ambiguous requirements and out-of-scope requests raised before development starts, not after. Work that grows beyond what was estimated is stopped and flagged rather than absorbed • Jira Hygiene & Capacity Visibility - Time logged daily against the correct ticket. Status and assignee current as work moves. Capacity risk flagged at least one business day prior • Practice & AI Contribution - At least one meaningful internal contribution per quarter across tooling, the theme framework, R&D or AI initiatives, with time allocated by the Practice Lead rather than absorbed outside client hours. Work Arrangement & Expectations: This is a remote role that will be set up via an Employer of Record (EOR) service. To ensure alignment and transparency, successful candidates will be expected to: • Disclose any existing ongoing roles or client work • Reflect this engagement on their LinkedIn profile Originally posted on Himalayas