Voltex Electrical Accessories

We are building Ora — a connected device ecosystem for professional electrical installers and homeowners. The architecture is deliberately two-phased, and the Lead Engineer must hold both phases clearly from day one. Phase 1 launches with a strict privacy-first, local-first philosophy: the Hub is the brain, the cloud is a relay. Cloud connectivity is disabled by default. The backend does not store device state, does not process command logic, and does not inspect device payloads. It routes encrypted packets, manages installer workflows, and stays out of the way. Phase 2 expands into full cloud connectivity — remote device access, live streaming, and cloud-to-device control at scale. This is a fundamentally different architecture from Phase 1, and the single most important design constraint on the Lead Engineer is this: Phase 1 must be built in a way that does not make Phase 2 a rebuild. The foundations laid now — data models, identity architecture, relay infrastructure, security posture — must extend cleanly to full cloud connectivity without structural rework. This is not a role for someone who has only built relay systems, or only built full-cloud IoT platforms. It is a role for someone who has built both, understands the transition between them, and can architect the bridge from day one. You will be the sole technical authority on the backend. There is no backend architect above you — you are that person. What You Are Building The Ora cloud backend has four primary responsibilities, all shaped by the cloud-optional design principle: 1. MQTT Relay Broker A lightweight, Mutual TLS 1.3 encrypted relay that routes packets to Ora Hubs by UUID. The cloud does not decrypt, store, or process the payload — it is a secure tunnel, not a state manager. Experience designing relay-model MQTT infrastructure rather than full-stack IoT backends is directly relevant here. 2. Installer Portal & Project Management Backend A professional-grade backend serving licensed electricians: account and credential management, project templates, floor plan and pairing plan storage, AccessKey lifecycle (create, claim, expire, regenerate), and encrypted Project Key custody for the remote handover path. This backend enforces Voltex ID re-verification before releasing sensitive handover credentials and strips user-identifiable data from project records post-handover. 3. Analytic Ingest Service A minimal, privacy-enforcing telemetry pipeline. A server-side filter explicitly drops any payload containing camera, microphone, occupancy, or contact sensor keys. Only system health metrics (CPU, RAM, signal strength) are stored. GDPR-compliant and aligned with Australia's Code of Practice for Securing the Internet of Things. 4. Identity-Free Backup & Restore Configuration backup that stores only Matter node topology and room layout — explicitly excluding personas, shadow identities, and system lifecycle data. Restore requires offline Recovery Key input at the device. The cloud holds an encrypted file; it cannot interpret or use what it holds. Phase 2 — Full Cloud Connectivity (Architect Now, Build Next) The next phase introduces full remote cloud control — live device streaming, cloud-to-device commands at scale, and real-time remote access from anywhere. The Lead Engineer does not build Phase 2 first, but must design Phase 1 so that Phase 2 is an extension, not a replacement. This requires deliberate choices today around identity architecture, data models, relay infrastructure extensibility, and security posture — so that when Phase 2 arrives, the foundations are already there. What You'll Do Technical Leadership • Own the backend architecture end to end — design decisions, standards, trade-off calls, and documentation — with no backend lead above you. • Defend the cloud-optional, minimal-footprint design philosophy across the team and with stakeholders, and resist feature creep that compromises the privacy model. • Lead technical design reviews and collaborate directly with the firmware and mobile leads to ensure the cloud, Hub, and App layers remain coherent. • Define and enforce engineering standards for API design, security posture, observability, and code quality. • Mentor engineers on the team and raise the technical bar across the backend. Hands-On Engineering • Design and deliver the MQTT relay broker with Mutual TLS 1.3, Hub UUID-based routing, and DoS-resilient connection handling. • Build and maintain the Installer Portal REST API — project management, AccessKey lifecycle, credential verification, and handover state machine integration. • Implement the analytic ingest pipeline with server-side payload filtering and GDPR-compliant retention policies. • Design PostgreSQL schemas and Redis caching strategies for installer project data, access control, and real-time sync. • Implement API security across all surfaces — OAuth2/OIDC, JWT, RBAC (Electrician vs Homeowner roles), rate limiting, and input validation. • Configure and manage AWS API Gateway for routing, throttling, and token validation, behind Cloudflare for external security and DDoS protection. • Own the CI/CD pipeline end to end — GitHub Actions → ECR → ECS Fargate (Sydney, production), with Render for dev environments. • Integrate OTA firmware distribution with Hub state-awareness — updates pause during PENDING_HANDOVER lockdown states. • Drive observability through OpenTelemetry → Grafana Cloud + Sentry — structured, trace-correlated logging via Serilog, diagnosable without accessing device payloads

Job Overview:  We’re seeking a Senior Software Engineer to lead the design and development of the backend systems that power our connected device ecosystem. You’ll architect scalable, secure, and modular APIs and services enabling real-time communication , state synchronization , and cross-platform device interoperability —with a strong focus on IoT and Matter standards. This is a senior, hands-on engineering role for someone deeply passionate about building robust systems that bridge hardware, cloud, and mobile experiences. Key Responsibilities:  - Design and develop high-performance backend services in C# . - Architect cloud-agnostic solutions deployable on AWS , GCP , Azure , or on-premises. - Build and maintain REST APIs with a focus on performance and scalability. - Implement real-time event-driven systems , including push notifications, web hooks, and messaging services. - Design and optimize PostgreSQL and Redis systems for relational, caching, and live data sync use cases. - Ensure observability through Sentry or similar tools for monitoring and performance tracing. - Implement strong API security (OAuth2/OIDC, JWT , rate limiting, input validation). - Manage configuration synchronization and state consistency between devices and cloud systems. - Build and deploy containerized services using Docker and CI/CD pipelines . - Maintain exceptional code quality , SQL optimization , and documentation standards .

• Own the backend architecture end to end — design decisions, standards, trade-off calls, and documentation — with no backend lead above you. • Defend the cloud-optional, minimal-footprint design philosophy across the team and with stakeholders, and resist feature creep that compromises the privacy model. • Lead technical design reviews and collaborate directly with the firmware and mobile leads to ensure the cloud, Hub, and App layers remain coherent. • Define and enforce engineering standards for API design, security posture, observability, and code quality. • Mentor engineers on the team and raise the technical bar across the backend. Hands-On Engineering • Design and deliver the MQTT relay broker with Mutual TLS 1.3, Hub UUID-based routing, and DoS-resilient connection handling. • Build and maintain the Installer Portal REST API — project management, AccessKey lifecycle, credential verification, and handover state machine integration. • Implement the analytic ingest pipeline with server-side payload filtering and GDPR-compliant retention policies. • Design PostgreSQL schemas and Redis caching strategies for installer project data, access control, and real-time sync. • Implement API security across all surfaces — OAuth2/OIDC, JWT, RBAC (Electrician vs Homeowner roles), rate limiting, and input validation. • Configure and manage AWS API Gateway for routing, throttling, and token validation, behind Cloudflare for external security and DDoS protection. • Own the CI/CD pipeline end to end — GitHub Actions → ECR → ECS Fargate (Sydney, production), with Render for dev environments. • Integrate OTA firmware distribution with Hub state-awareness — updates pause during PENDING_HANDOVER lockdown states. • Drive observability through OpenTelemetry → Grafana Cloud + Sentry — structured, trace-correlated logging via Serilog, diagnosable without accessing device payloads

• Assist with month-end close activities • Perform balance sheet and bank reconciliations • Maintain general ledger accuracy • Assist with BAS and GST preparation (Australia & New Zealand) • Support external audits • Ensure adherence to finance policies • Accounts receivable transactional processing • Accounts payable transactional processing

About Voltex Electrical Voltex Electrical is a proudly Australian business, built from the ground up to serve the real needs of licensed electricians. Founded in 2001, we design, manufacture and supply high-quality electrical accessories directly to contractors through our own online platform, removing the traditional wholesaler and retailer layers from the equation. It is a model that gives us a unique market advantage. No one else is delivering this kind of end to-end service at scale, and it is why we are trusted by thousands of electricians across the country. Our customer experience, speed of delivery, and investment in quality set us apart. With strong brand recognition and 5 to 10 per cent market share, Voltex is well established but still growing fast. We have gone from strength to strength and are very much on a journey of market takeover with exciting projects in the pipeline. Position Purpose We are seeking an Assistant Accountant to support the finance team with accurate financial reporting, reconciliations and day‑to‑day accounting operations. This role plays a key part in month‑end close, balance sheet integrity, compliance support and continuous improvement of finance processes. It is well suited to someone early in their accounting career who is confident in cloud accounting systems and keen to develop in a fast‑paced, growing business. Key Responsibilities •        Assist with month-end close activities •        Perform balance sheet and bank reconciliations •        Maintain general ledger accuracy •        Assist with BAS and GST preparation (Australia & New Zealand) •        Support external audits •        Ensure adherence to finance policies •        Accounts receivable transactional processing •        Accounts payable transactional processing

About Voltex Electrical Voltex Electrical is one of Australia’s leading electrical wholesale distributors, with 25 years of history and a growing national footprint. Our IT team powers the platforms, systems, and data that keep the business running — from e-commerce and ERP to logistics and customer experience. We’re in the middle of a deliberate transformation: building the leadership layer, delivery systems, and engineering culture that will carry us through the next stage of growth. This role is central to that transformation. The opportunity This isn’t a maintenance role. You’re joining at a moment where the IT organisation is being reshaped — new leadership structures, new engineering standards, and a clear shift from reactive execution to predictable, outcome-driven delivery. As an Engineering Manager, you’ll own the health of a team and its delivery system. You’ll coach engineers, build repeatable processes, and partner with product and business stakeholders to turn strategy into shipped outcomes. The expectation is that you build something that scales — not that you become the team’s top individual contributor. If you’ve ever walked into a team that was busy but not visibly connected to business outcomes, and built the systems that changed that — this is your role. What you’ll do Team leadership & people management - Hire, onboard, coach, and retain engineers; build a strong team culture. - Run effective 1:1s, performance reviews, development plans, and career pathing (Intermediate → Senior → Lead). - Address performance issues early with clarity and fairness. - Build team norms around quality, ownership, and collaboration.   Delivery execution & predictability - Own team delivery health: planning, prioritisation, sequencing, execution, release readiness. - Operate the team’s delivery cadence (sprint-based for Delivery teams; flow/kanban for Platform teams). - Drive clarity of work: crisp tickets, acceptance criteria, dependency mapping, risk management. - Escalate early and solve bottlenecks — process, staffing, tech debt, unclear requirements.   Systems thinking - Replace heroics with systems: repeatable processes, guardrails, automation, documentation. - Improve engineering throughput without sacrificing quality (tests, CI/CD hygiene, code review standards, incident learnings). - Build operating mechanisms: definitions of done, incident postmortems, quality gates, release playbooks.   Cross-functional partnership - Partner with Product Managers, Data, Infra, and business stakeholders to translate objectives into deliverable plans. - Communicate tradeoffs, timelines, and risks honestly to executives and stakeholders. - Improve the stakeholder experience: clear updates, predictable outcomes, fewer last-minute surprises.   Technical stewardship (hands-off by default) - Maintain enough technical depth to evaluate architecture and quality, but not act as the primary implementer. - Partner with Staff / Architects / Lead Engineers on technical direction, tech debt, and platform maturity. - Ensure the team invests appropriately in maintainability, reliability, and security. What success looks like Within 12–18 months, we’d expect to see: - Your team delivers reliably — visible commitments, improving sprint accuracy, fewer surprise escalations. - Lightweight but consistent engineering standards and delivery rituals are in place and self-sustaining. - Clear ownership boundaries between PM, EM, and technical leadership — documented and referenced. - People are growing: at least one direct report promoted or stretch-assigned within your first year. - No critical work is blocked by a single person for more than a sprint. The team is resilient. - Stakeholders trust your team’s delivery and know what to expect. What you own - Team execution model and delivery rituals - Staffing, hiring recommendations, performance and growth decisions - Prioritisation input via sequencing and capacity constraints (in partnership with PM and leadership) - Escalations and risk calls for the team’s work - Standards for team health: quality bar, incident process, sustainable pace

• Hire, onboard, coach, and retain engineers; build a strong team culture. • Run effective 1:1s, performance reviews, development plans, and career pathing (Intermediate → Senior → Lead). • Address performance issues early with clarity and fairness. • Build team norms around quality, ownership, and collaboration. • Own team delivery health: planning, prioritisation, sequencing, execution, release readiness. • Operate the team’s delivery cadence (sprint-based for Delivery teams; flow/kanban for Platform teams). • Drive clarity of work: crisp tickets, acceptance criteria, dependency mapping, risk management. • Escalate early and solve bottlenecks — process, staffing, tech debt, unclear requirements. • Replace heroics with systems: repeatable processes, guardrails, automation, documentation. • Improve engineering throughput without sacrificing quality (tests, CI/CD hygiene, code review standards, incident learnings). • Build operating mechanisms: definitions of done, incident postmortems, quality gates, release playbooks. • Partner with Product Managers, Data, Infra, and business stakeholders to translate objectives into deliverable plans. • Communicate tradeoffs, timelines, and risks honestly to executives and stakeholders. • Improve the stakeholder experience: clear updates, predictable outcomes, fewer last-minute surprises. • Maintain enough technical depth to evaluate architecture and quality, but not act as the primary implementer. • Partner with Staff / Architects / Lead Engineers on technical direction, tech debt, and platform maturity. • Ensure the team invests appropriately in maintainability, reliability, and security.

• Lead UX planning, research, and design direction across multiple digital products. • Champion user-centred thinking and embed UX best practices across the product lifecycle. • Translate business requirements, customer insights, and technical constraints into clear design strategies and solutions. • Facilitate workshops and discovery sessions to explore problem spaces and align teams. • Conduct user research including interviews, usability testing, observational studies, and heuristic evaluations. • Analyse customer behaviour, user journeys, and product analytics to identify opportunities for improvement. • Capture and communicate insights in a way that supports clear decision-making and prioritisation. • Create personas, journey maps, and service blueprints to guide design decisions. • Identify pain points, opportunities, and moments that matter across end-to-end experiences. • Help align teams on current-state and future-state experience improvements. • Produce high-quality wireframes, user flows, information architecture, prototypes, and polished UI designs. • Collaborate closely with engineers to ensure high-quality implementation of UX work. • Contribute to design standards, patterns, and components that support consistency across Voltex platforms. • Partner with product managers, engineering leads, and stakeholders to define roadmap priorities and customer-centric outcomes. • Mentor junior designers and uplift UX maturity within the team. • Facilitate design sprints and workshops to support ideation, alignment, and rapid problem-solving. • Leverage data, feedback, and experimentation to iterate and optimise digital experiences. • Help drive the evolution of Voltex’s design system and UX guidelines. • Keep up-to-date with industry trends, tools, and emerging practices to ensure innovation and quality remain high.

. - Design and develop high-performance backend services in **C#**. - Architect **cloud-agnostic** solutions deployable on **AWS**, **GCP**, **Azure**, or on-premises. - Build and maintain **REST APIs** with a focus on performance and scalability. - Implement **real-time event-driven systems**, including push notifications, web hooks, and messaging services. - Design and optimize **PostgreSQL** and **Redis** systems for relational, caching, and live data sync use cases. - Ensure observability through **Sentry** or similar tools for monitoring and performance tracing. - Implement strong **API security** (OAuth2/OIDC, JWT, rate limiting, input validation). - Manage **configuration synchronization** and **state consistency** between devices and cloud systems. - Build and deploy containerized services using **Docker** and **CI/CD pipelines**. - Maintain exceptional **code quality**, **SQL optimization**, and **documentation standards**.

• Oversee the day-to-day operations of network infrastructure by monitoring system performance, configuration, maintenance, and repair. • Assist in monitoring and managing the network infrastructure, including routers, switches, SASE, and VPNs to ensure uptime and performance. • Assist in data center modernization, and cloud migration / adaptation activities. • Assist with IT infrastructure projects and initiatives. • Provide tier 2-3 operational support to employees, diagnosing and resolving hardware, software, and networking issues. • Performs troubleshooting as required. Leads problem-solving efforts often involving outside vendors and other support personnel. • Management of all networking equipment, and other components. • Ensures high availability and acceptable levels of performance of mission critical host resources. • Ensure that records of infrastructure equipment inventory are properly maintained. • Interfaces with, and contributes to overall success of other IT teams, including Service Desk Operations, Database, and Applications Development. • Creates and maintains a well-documented knowledge base.