Digital Library .Net Developer
Location: Minneapolis, MN
Start Date: 7/27/2009
End Date: 10/1/2009 With option to extend into Feb/March
Rate: Depends On Experience
Detailed Description of Job Responsibilities (Tasks & Deliverables):
- Participate in design meetings & code reviews
- Participate in Scrum practices
- Must provide daily discussion on progress & impediments
- Must have the ability to break stories down into tasks
- Problem Solve Skills
- Must be able to understand and implement abstract OO designs that fit within the Client's framework.
- Write & re-factor code
- Write Unit Test
Mandatory Experience:
4+ Years experience in object-oriented software architectures and concepts.
.NET (ASPX, VB)
SQL Server (TSQL, stored procedures, database schema design)
Must be comfortable to participate in constructive design meetings where ideas are shared and must align to the overall Client's architectural vision for this project.
Candidates must work well with teams, be easily approachable, and have the ability to figure out problems and implement them.
Nice to Have:
Experience with Scrum/Agile development.
WCF, WPF, Silverlight
XML, XSLT, XML Schema
Additional Information:
Our Client's Digital Library space currently has two applications, a Digital Asset Management (DAM) system and a Recipe Information System (RIS). The DAM system is for storing and repurposing various types of digital assets. These include; packaging, logos, equity characters, barcodes, commercials, package photography, food photography, life style photography, and more. The RIS is a collection of all of our Client's recipes; this tool also supports the creation, workflow, and publishing of recipes to web sites.
The Digital Library will focus on the transformation of moving from a silo application approach to a multi tiered, services approach. The approach to this transformation will be to begin building role based applications leveraging existing system’s databases & services. These applications will be built using an agile development approach with daily scrum meetings led by the scrum master (project manager). These applications need to be built to allow their components to be reused and services built to access the data layers or provide access to various functions. The lower services & component layers will interact with the digital repositories and other services to do publishing, workflow search, etc.