Skip to main content
Posted 12 June, 2026

Technical Lead

Connection denied by Geolocation
Australia,Australia,2000 Full Time
Reference: 365_629181_26-00001

Role Overview: The Tech Lead is a hands-on leader responsible for the technical direction of a specific team or project. They ensure the team builds high-quality, scalable, and maintainable software while bridging the gap between technical requirements and business goals. They spend a significant portion of their time (typically 30%-60%) still writing or reviewing code.
Key Responsibilities:
  • Technical Vision & Architecture: Own the technical roadmap for the team. Make high-level design choices and dictate technical standards (e.g., choosing a database, defining API contracts).
  • Mentorship & Guidance: Act as the "go-to " expert. Help SDE 1s and 2s solve complex bugs and provide detailed feedback in code reviews to elevate the team's skill level.
  • Delivery & Quality: Oversee the software development lifecycle (SDLC) for the team. Ensure that the code meets performance, security, and scalability requirements.
  • Impediment Removal: Identify technical bottlenecks (technical debt, environment issues) and clear them so the team can move faster.
  • Stakeholder Liaison: Work with Product Managers and Business Analysts to translate "business speak " into "technical specs " and provide accurate effort estimations.
  • Retail: Candidates are required to have hands-on experience in the e-commerce or retail sector.
  • Hands-on Coding: Lead by example by taking on the most complex or critical components of a project.
Qualifications:
  • Bachelor's or Master's degree in Computer Science or a related field.
  • 7+ years of software engineering experience, with a proven track record of designing complex systems.
  • Expert-level proficiency in the team's primary tech stack (e.g., Java/Spring, Python/Django, React/Node).
  • Strong understanding of system design, microservices, and cloud infrastructure (AWS/Azure/GCP).
  • Excellent communication skills-the ability to explain "the why " behind a technical decision to non-technical stakeholders.

Sign up for Job Alerts