Western suburbs of Chicago (Naperville area). No H1B, no remote. We are looking for junior to mid-level person with either a Java background looking to move to C# or a C# background. If coming from a C# background, must be open to open source libraries like Spring.NET.
It's a small team and you will work with public-facing web applications in the financial field as well as back-office application for internal stuff. Must understand RDBMS fundamentals.
I cannot name the company publicly because this is not an endorsed post. But shoot me an email (email is in my profile) if you're interested or have any questions.
I am not interested in this particular job but why would you want to use Spring.NET? Is it because you are migrating from a Java application using Spring.NET? Are there any other reasons?
If you are moving to C#, I would definitely recommend another framework which is more suited to leverage C#/.NET. The reason I am suggesting is that because it is very difficult to hire good C#/.NET developers these days and the problem becomes 10 times harder if you are going to use Spring.NET. I know that it will be a deal breaker for me and my other friends who use C#/.NET.
When this application was started around 2008 or so we had a number of frameworks to choose from. At the time we chose spring.net. Looking back on it, that was a good choice considering most of our alternatives at the time (and since) have come and gone. Particularly Microsoft technologies that seem to come and go all the time. We're pretty happy that we chose a reliable, stable and well-maintained library such as spring.net.
I am curious what alternative you'd recommend, particularly if it's something that is production ready and has a certain future.
We're well aware of how hard it is to hire good C# developers. But in my opinion, a good C# developer isn't going to be put off by the choice of Spring.NET.
I think Spring.NET is too verbose and too big. I would rather use few well tested and idiomatic C# frameworks as an alternative to Spring.NET
E.g. IOC - You can use MEF which is part of the framework. OR my personal favorite Ninject.
Web Applications - Without a doubt ASP.NET MVC.
Aspect Oriented Programming - Postsharp
DataAccess - I do not think ORM technology is mature enough to use it for any complicated work. For simpler things, Dapper does the trick.
I believe in using best tool for a given problem instead of using one monolithic framework. I especially don't like Spring framework because it needs too much configuration in terms of XML files. I prefer configuration through code approach.
It's a small team and you will work with public-facing web applications in the financial field as well as back-office application for internal stuff. Must understand RDBMS fundamentals.
I cannot name the company publicly because this is not an endorsed post. But shoot me an email (email is in my profile) if you're interested or have any questions.