Sr. Microsoft Dynamics and Integration Developer

Responsibilities

• Developing Core and Complex Features: Writing the foundational code for new initiatives, setting up architectural scaffolding, or handling highly complex integrations (such as orchestrating data syncs between enterprise systems or configuring secure APIs).
• Deep-Dive Troubleshooting and Stabilization: Stepping in to diagnose and resolve critical production incidents, performance bottlenecks, or tricky data sync failures that have blocked the rest of the team.
• Prototyping and Proofs of Concept: Building throwaway or experimental prototypes to validate a new technology choice, integration platform, or architectural approach before the wider team commits to it.
• Conducting Rigorous Code Reviews: Reviewing pull requests not just for syntax, but for architectural alignment, security vulnerabilities, edge-case handling, and test coverage.
• Managing Tech Debt and Refactoring: Actively identifying rotting code or rigid architectures, documenting the risk, and systematically refactoring components during appropriate sprint windows.
• Defining and Enforcing Engineering Standards: Establishing linting rules, branching strategies, automated testing protocols, and continuous integration/continuous deployment (CI/CD) pipelines to streamline delivery.
• Writing and Maintaining Technical Documentation: Authoring system architecture diagrams, data models, integration maps, and runbooks so the platform's design is transparent to the rest of the organization.
• Technical Discovery and Estimation: Partnering with Project and Product Managers to break down vague business requirements into concrete technical tasks, identifying hidden dependencies, and providing realistic effort estimations.
• Risk Assessment and Mitigation: Flagging potential compliance, security, or performance risks early in the planning lifecycle and designing technical workarounds.
• Evaluating Third-Party Tools: Assessing vendor software, APIs, or iPaaS platforms to ensure they meet the organization's technical, security, and integration standards.
• Mentoring and Pair Programming: Sitting down with junior and mid-level developers to help them talk through logic, learn new frameworks, and grow their problem-solving skills.
• Leading Technical Knowledge Discussions: Introducing the team to new tools, design patterns, or platform updates.
• Unblocking Team Members: Serving as an escalation point when a developer is stuck on a technical hurdle, helping them debug without completely taking over the task.