Technical Specialist

HCL Technologies Limited, a global IT services leader, is hiring a Technical Specialist to join onsite in Australia. The role centers on building and operating scalable backend services and APIs with a strong emphasis on the modern C#/.NET stack and AWS cloud-native deployments. It’s a hands-on position that suits engineers who enjoy shaping enterprise integrations and ensuring production systems stay reliable.

Located in Australia and offered as a full-time onsite opportunity, the role targets developers who want to own backend capabilities from design through deployment and production support. If you relish working with contemporary C#/.NET and cloud-first architectures within a corporate environment that values solid, scalable software, this could be the right fit.

Crafting reliable backend services

In practice, you’ll design and implement backend services using C#, the current .NET family, and ASP.NET Core, while building scalable REST APIs and integration points. You’ll also help shape cloud-native applications on AWS and craft integrations with enterprise APIs, data platforms, and downstream systems. Containerization and modern deployment patterns will be part of the daily workflow to keep services portable and resilient.

You’ll contribute to CI/CD pipelines, automated testing, and deployment practices, and you’ll implement telemetry and observability to keep systems healthy. Production engineering and incident resolution will be ongoing responsibilities, with participation in API and integration-contract design and in technical design discussions and code reviews shaping engineering best practices.

Core tech you’ll need

Here’s the core set of capabilities the team is looking for.

• Solid command of C# and the current .NET ecosystem, including .NET Core and ASP.NET Core
• Hands-on experience building scalable RESTful APIs and web service interfaces
• Extensive experience delivering cloud-native solutions on AWS
• Strong SQL skills for data access and persistence
• Practical experience containerizing applications and working with container tooling
• Proficiency with Git in collaborative development
• Ability to design and maintain CI/CD pipelines
• Experience with automated testing to enable reliable releases
• Focus on secure coding practices and application security
• Hands-on production engineering and troubleshooting across systems
• Knowledge of enterprise API design and integration approaches
• Comfort collaborating on technical design and engineering best practices

Nice-to-haves that help you stand out

Beyond the essentials, these capabilities can differentiate a candidate:

• Familiarity with .NET 8 features
• Experience with AWS Lambda serverless functions
• Exposure to event-driven design patterns
• Background in distributed systems
• Strength in observability and telemetry practices
• Knowledge of Snowflake data warehousing
• Experience in financial services domains such as cards or payments

On-site in Australia

The role is full-time and on-site in Australia, with HCL Technologies Limited as the employer.

Guidance for applicants

Put your most relevant work up front in your resume by leading with how you’ve used C#, the .NET stack, and AWS to deliver scalable backend services and cloud-native apps. Include concrete outcomes, like performance gains, reliability improvements, or successful production deployments, to show impact.

To prove you have the must-have skills, point to specific projects where you built REST APIs, containerized services, implemented CI/CD, and ensured security and production readiness. If you can cite a production incident you resolved or a performance issue you triaged, describe the tooling you used and the result you achieved.

For interviews, be prepared to discuss concrete designs for enterprise API integrations and how you approached production engineering and troubleshooting in real-world scenarios. You may be asked to explain trade-offs you considered when balancing security, scalability, and maintainability in cloud-native architectures.

Ask a thoughtful question about how the team weighs cloud-native AWS work against enterprise integration constraints, and which observability metrics matter most for the systems they build. A good question could be: what telemetry targets do you prioritise for the critical paths in your API integrations and how is success measured?