
Developer - L3
- Austin, TX
- $45,000-110,000 per year
- Permanent
- Full-time
- Develop and customize Microsoft Dynamics 365 applications to fulfill specific business needs.
- Hands-on experience with CRM, sales and marketing modules
- Develop software and design solutions independently to satisfy customer requirements that consider performance and availability
- Partner with engineering product managers and principal software engineers to translate requirements into detailed designs
- Tune performance and resolve availability issues of product or service and its dependencies in production.
- Estimate software development effort including identifying dependent teams and developing code to satisfy complex requirements
- Adopt engineering best practices while contributing to the definition of the engineering lifecycle as well as the definition of best practices
- 7+ years of hands-on experience in software development, specifically with Microsoft Dynamics 365
- Experience in user management, role assignment, and security configuration within Dynamics 365 and Power Platform
- Ability to configure and customize Dynamics 365 applications to meet business requirements, including creating custom entities, workflows, power automate flows and business rules
- Familiarity with Azure Active Directory and integration with other Microsoft services
- Proficient in C#, .NET, JavaScript, and SQL with experience in web services (REST/SOAP)
- Solid understanding of Dynamics 365 customization, configuration, and deployment using managed solutions
- Experience with the Power Platform, including Power Apps (both model-driven and canvas apps), Power Automate, and PCF controls etc. Experience on Power pages is mandatory.
- Knowledge of Azure and cloud-based services is advantageous, specifically Azure Functions
- Experience with SQL Server Integration Services (SSIS)
- Experience with HTTP and REST architecture
SAP as service providerWe use the following session cookies, which are all required to enable the website to function:
- "route" is used for session stickiness
- "careerSiteCompanyId" is used to send the request to the correct data center
- "JSESSIONID" is placed on the visitor's device during the session so the server can identify the visitor
- "Load balancer cookie" (actual cookie name may vary) prevents a visitor from bouncing from one instance to another