We are looking for an "extremely productive" software engineer who loves to code, has "exceptional" skills in programming and problem solving, is enthusiastic about learning new technologies, and has a strong work ethic. If you;ve competed in a programming competition, this may well be a job for you.Candidates applying for this position should ideally be prepared to join the team immediately.We are looking for an "extremely productive" software engineer who loves to code, has "exceptional" skills in programming and problem solving, is enthusiastic about learning new technologies, and has a strong work ethic. If you;ve competed in a programming competition, this may well be a job for you.Candidates applying for this position should ideally be prepared to join the team immediately.
Personal Skills:
- Strong programming and problem solving skills
- A quick and keen learner, flexible with employing different development technologies
- Good communication skills in English, both verbal and written
Technical Expertise:
- Exceptional Object Oriented Programming Concepts
- Knowledge of the .NET Framework either 2.0 / 3.5 / 4.0 / 4.5 / 4.6 / Core
- Proficienct in expressing concepts in the C# Language
- Knowledge of ASP.NET MVC, and its architecture
- Knowledge of ORMs, especially Entity Framework
- Knowledge of Twitter Bootstrap, HTML5, CSS3,
- Knowledge of JavaScript, jQuery and its plugins, and other client side libraries.
- Knowledge of working with XML, JSON, Windows and Web Services
- Good Database design, and development concepts.
- Experience working with Version Control Software, especially Git
Nice to have:
- Knowledge of working with WPF, WCF is a plus
- Knowledge of working with GitFlow is a plus.
- Knowledge of working with Dependency Injection, and TDD is a definite plus
- Experience with Xamarin, or any Mobile Application development experience is a definite plus
Questions to ask yourself:
- Do I know why majority of the code written employing the .NET Framework is called managed code?
- What is the difference between a Controller and a Model, and if all the logic were to reside in the Controller, what is the point of having Models in the first place?
- Do I know what is the difference between Application Lifecycles of a ASP.NET Web Forms app versus an ASP.NET MVC app?
- Have I ever implemented an interface before? Or have I extracted an interface from a class before?
- Do I know what ORMs do when I ask one to get me some records?
- Have I ever created a Pull Request before?
- Have I been working on personal projects to discover the technologies mentioned above or any other software development related technologies?
If you have answers to these questions, you're are headed in the right direction. The ideal candidate would be a software enthusiast and has been coding since early age.