Infosys is seeking a .NET Technology Architect. As a Technology Architect, you will interface with key stakeholders and apply your technical proficiency across different stages of the Software Development Life Cycle including Requirements Elicitation and Design. Also, you will play an important role in creating the high-level design artifacts. Deliver high quality code deliverables and supports peers in quality checks such that design requirements are met. Create the user documentation for the assigned sub-modules. Perform root-cause analysis of any issues that arise post-implementation and work on solutions related to issue fixing.

Qualifications
Basic
• Bachelor's degree or foreign equivalent required from an accredited institution. Will also consider three years of progressive experience in the specialty in lieu of every year of education.

• C# Proficiency: Deep understanding of C# language features, syntax, and best practices.
• .NET 8 Framework: Mastery of the .NET 8 framework, including its new features, performance optimizations, and architectural patterns.
• ASP.NET Core Web API: Expertise in building RESTful APIs using ASP.NET Core Web API, including controllers, models, and routing.
• LINQ: Strong understanding of LINQ for querying and manipulating data.
• Testing: Proficiency in unit testing, integration testing, and API testing frameworks (e.g., xUnit, NUnit, Postman).
  • Unit Testing: Ability to write effective unit tests using mocking frameworks (e.g., Moq, NSubstitute) to isolate components and test their behavior in isolation.
  • Integration Testing: Knowledge of integration testing techniques to verify the interaction between different components of the API, including external API calls.
  • API Testing: Experience with API testing tools to validate API contracts, performance, and security.

• API Consumption: Expertise in consuming external APIs, including:
  • HTTP Clients: Proficiency in using HTTP clients (e.g., HttpClient, RestSharp) to make API requests.
  • API Authentication: Understanding of various authentication mechanisms (e.g., OAuth, API keys) and their implementation.
  • Error Handling: Ability to handle potential errors and exceptions when consuming APIs.
  • Rate Limiting: Awareness of API rate limits and best practices for managing them.
• API Gateway: Experience with API gateways (e.g., Azure API Management) for managing, securing, and publishing APIs.

• YAML pipelines
• Service Principles
• Environments
• Artifacts: Nuget packages

• SOLID Principles: Adherence to the SOLID principles (Single Responsibility, Open-Closed, Liskov Substitution, Interface Segregation, Dependency Inversion) to create maintainable and scalable code.
• DRY Principle: Avoid code duplication by following the Don't Repeat Yourself principle.
• Design Patterns: Knowledge of common design patterns (e.g., Factory, Singleton, Repository) to improve code structure and reusability.
• Dependency Injection: Understanding and implementation of dependency injection to decouple components and make code more testable.
  • Dependency Injection Containers: Experience with popular DI containers (e.g., Microsoft.Extensions.DependencyInjection) to manage dependencies.
  • Constructor Injection: Understanding of constructor injection for injecting dependencies into classes.
  • Property Injection: Knowledge of property injection for injecting dependencies into properties.
  • Service Locator: Awareness of the service locator pattern and its potential drawbacks.
• Clean Code Practices: Adherence to clean code principles, such as naming conventions, formatting, and commenting.

• Problem-Solving: Ability to analyze complex problems and find effective solutions.
• Communication: Excellent written and verbal communication skills, especially for collaborating with API consumers.
• Collaboration: Ability to work effectively in teams and with cross-functional stakeholders.