.NET/AWS Software Engineer - Remote

As a .NET/AWS Software Engineer at Mindex, your responsibilities will include designing, implementing, and maintaining complex systems using .NET Core, developing microservices with an event-driven architecture on AWS, and creating RESTful Web Services. You'll also collaborate with the scrum master and product owner to align software solutions with business needs, while documenting technical changes to uphold our standards.

To qualify for the .NET/AWS Software Engineer role at Mindex, you should hold a Bachelor's degree in Computer Science (or a related field) or have equivalent experience. Additionally, at least three years of extensive software development experience in Microsoft .NET and C# is required, along with expertise in building and consuming RESTful APIs.

Candidates for the .NET/AWS Software Engineer position at Mindex should be familiar with technologies such as .NET Core, Web API, AWS services like Lambda, SQS, SNS, and DynamoDB. Proficiency in tools such as Postman, XUnit, and Git will also be advantageous.

Absolutely! The .NET/AWS Software Engineer position at Mindex is fully remote, allowing you to work from anywhere while maintaining a globally distributed collaboration with our dynamic team.

Mindex offers a competitive benefits package for .NET/AWS Software Engineers, including health insurance options, flexible time off, a 401(k) plan with company match, professional development opportunities, and various insurance options, among many others.

When designing a RESTful API, it’s essential to start with clear use cases and user stories. I begin by defining resources, their endpoints, and understanding the data model. It's crucial to adhere to REST standards, implement proper status codes, and ensure each endpoint offers a straightforward, intuitive way for clients to interact with the service.

Event-driven architecture in AWS allows systems to respond to events immediately, enhancing scalability and efficiency. By using AWS services like EventBridge or SQS, I can enable microservices to react asynchronously based on specific triggers, simplifying workflows and reducing dependencies between components.

Writing technical documentation is vital to ensure that knowledge is shared among team members. It aids in maintaining the system, helps onboard new developers, and provides clear guidelines about functionalities. Good documentation should cover system changes, processes, and design decisions to facilitate easier troubleshooting and future updates.

I manage version control through Git by ensuring that I commit changes frequently with clear, descriptive messages. I utilize branching strategies—like feature branches—for collaboration and enforce code reviews before merging to maintain code quality and system stability. This helps track changes efficiently and enables easy rollbacks if necessary.

For debugging applications, I leverage built-in debugging tools in Visual Studio, implement logging using frameworks like NLog or Serilog, and employ profiler tools to analyze performance. I also utilize unit testing practices to isolate and address issues early in the development process.

In a previous project, I faced performance issues due to high API call volumes. I resolved this by implementing caching strategies and optimizing database queries, which significantly improved response times and reduced system load, enhancing overall user satisfaction.

To ensure clean and maintainable code, I adhere to coding standards and best practices, employ SOLID principles, and regularly refactor my code to improve readability. Additionally, I write unit tests to validate my code changes and conduct code reviews to gain insights from team members.

I have extensive experience working in Agile environments, participating in sprint planning, daily stand-ups, and retrospectives. I value the iterative approach of Agile, which allows for continuous feedback and adaptation, ensuring that projects stay aligned with business needs and stakeholder expectations.

I prioritize effective time management and transparent communication when facing tight deadlines. By breaking down tasks into smaller milestones and regularly assessing progress, I can focus on delivering high-quality features while managing workloads, even under pressure.

I have implemented several AWS services in my projects, including AWS Lambda for running backend processes without server management, SQS for message queuing, and DynamoDB for NoSQL database solutions. This experience allows me to leverage cloud capabilities effectively to enhance system performance and scalability.