.Net Developer
watiMinneapolis (MN)
About the role
Job Title: .Net DeveloperClient: State of MinnesotaRole: .Net DeveloperDepartment: MNIT/BCA
Responsibilities:
Rewrite legacy data integration programs into Dynamics 365 compatible code (e.g., C# plugins, etc.)Reverse engineer screens from 4GL legacy application into Dynamics 365 UI workflows/screensBuild out new automations and enhancements as defined by the business area into the Dynamics 365 environmentAssist with UAT testing and data validationCreate operational and production support documentationRespectfully and effectively collaborate with other project team membersProvide knowledge transferMinimum Qualifications: Five (5) years’ experience in Developer/Programmer roleTwo (2) engagements lasting more than six (6) months in Developer/Programmer roleThree (3) years’ experience as a developer using C# on ASP.NETThree (3) years’ experience as a developer using Microsoft T-SQL
Desired Skills:
Development experience with Ingres technologiesDevelopment experience as a programmer or relevant role with Dynamics 365 Ability to program in languages such as SQL, C, C# and Java ScriptExperience with Workflow frameworksExperience developing micro-servicesAbility to transform code into C#/ASP.NET and T-SQL from other languages such as: Ingres ABFIngres RWIngres SCan older dialect of Visual BasicDOS
Before you apply
Applying takes about a minute. These four things decide how fast it moves after that.
Your profile is current
It's what we read first. Occupations, seniority and locations matter more than a long history.
Two examples you can talk through
Not a portfolio — just two pieces of work where you can explain the decisions and what you'd change.
A number in mind
What you're on now and what would make you move. We negotiate better when we know both.
Your notice period
Employers plan around it, and it's the question that stalls offers most often.
Once you apply, someone reads it and calls you before anything reaches the employer — usually within two working days.