Lead Software Developer

Key responsibilities

• Design and build scalable, production‑grade web applications.
• Contribute to system architecture and technical design decisions.
• Develop high‑quality, maintainable React applications using Type Script.
• Build and evolve APIs and services using .NET.
• Participate actively in technical discussions and architectural trade‑offs.
• Conduct code reviews and uphold engineering quality standards.
• Collaborate closely with product, commercial, and support teams.
• Troubleshoot and resolve production issues across the stack.
• Support and mentor mid‑level engineers.

• 5–8 years of commercial software engineering experience.
• Demonstrated experience operating as a Senior Engineer in a production environment.
• Evidence of ownership beyond individual tasks (features, services, or systems).

• Strong commercial experience with React and Type Script (typically 3+ years).
• Proven experience building production‑grade, scalable UI applications.
• Solid understanding of:
  • Component architecture and reuse.
  • State management approaches.
  • Performance optimisation in real‑world applications.
• Candidates whose primary experience is in Angular or other frameworks, with only limited React exposure, are unlikely to be a fit.
• Solid, hands‑on experience with .NET / .NET Core.
• Experience building and maintaining APIs and service‑based architectures.
• Good understanding of:
  • Performance considerations.
  • Reliability in production systems.
• Experience working on e‑commerce, marketplace, or transactional systems is strongly preferred.
• Candidates without direct e‑commerce experience should demonstrate experience with complex user‑facing platforms and systems that involve transactions or business‑critical workflows.
• Experience working with Azure or comparable cloud platforms.
• Familiarity with CI/CD pipelines and Docker or containerised environments.
• Exposure to monitoring and observability tools.

• A strong hands‑on engineer who takes ownership and delivers reliably.
• A pragmatic problem solver who balances quality, speed, and business needs.
• Someone who contributes beyond code through ideas, improvements, and collaboration.
• A supportive mentor who helps others grow without needing to be a formal manager.

• Experience with high‑scale or high‑traffic systems.
• Exposure to microservices architectures.
• Experience in payments, pricing, or order management domains.
• Experience with Kubernetes or cloud‑native patterns.

• Not a junior or mid‑level position.
• Not a frontend‑only or backend‑only role.
• Not a Staff / Principal‑level ownership role.

• Opportunity to work on a commercially critical platform.
• A collaborative, pragmatic engineering environment.
• Exposure to modern technologies and evolving architecture.
• Real opportunity to influence how systems are built and improved.

• Systems they’ve built and their specific contribution.
• Technical decisions they’ve contributed to and why.
• How they’ve handled real‑world production issues.
• Examples of ownership, improvement, or mentoring.