Sr. Microsoft Dynamics and Integration Developer

Seeking a candidate located in the specified area.

Senior Developer

On an ongoing basis, the Senior Developer will report to the Application Development and Support manager. The Senior Developer may serve as the liaison for the Department with the Florida Digital Service, and solution providers/suppliers. The Senior Developer will work closely with project stakeholders and the OIT Applications Team. Work related to other divisions may be assigned by the Department's Contract Manager. The Senior Developer will focus on developing and improving business processes, assisting with the development of metrics, both within the technology and business organizations. The candidate must have the following abilities for consideration:

• A strong technical mastery possessing a deep expertise in a number of core languages/frameworks (e.g., .NET/C#, Java, or Python) alongside a broad understanding of the technical ecosystem (i.e., frontend, backend, databases, and infrastructure).
• Agnostic problem solving to not be attached to a specific tool or language, selecting the right tool for the job based on performance, maintainability, and business alignment.
• Effectively manage data transfers between multi-platform applications, leverage Integration Platform as a Service (iPaaS) tools, and design clean APIs.
• Identify, track, and deliberately manage technical debt, knowing how to balance refactoring code with delivering new business value.
• Understand the entire software development lifecycle (SDLC) and play a key role in technical scoping, estimation, and risk mitigation before a single line of code is written.
• Actively guide junior and mid-level developers through constructive code reviews, pair programming, and architectural deep-dives.
• Explain complex technical constraints, risks, and trade-offs to product managers, business analysts, and executives in a way that aligns with business goals.
• Champion documentation, automated testing, CI/CD pipelines, and coding standards to make the entire team more efficient.

The Senior Developer will provide, but not be limited to, the following activities and tasks.

• High-Impact Technical Delivery Activities. The Senior Developer will tackle the tasks that require the highest degree of critical thinking and risk management.
  • 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.
• Technical Governance and Code Quality Delivery Activities. The Senior Developer will act as the guardian of the codebase, ensuring that the software remains maintainable, secure, and scalable over time.
  • 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.
• Project Scoping and Business Alignment Delivery Activities. The Senior Developer will bridge the gap between business requirements and technical execution before development begins.
  • 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.
• Team Enablement and Mentorship Daily Activities. The Senior Developer's output is multiplied by how much they improve the efficiency of the developers around them..
  • 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.

Contract Deliverables.

• Pull Request (PR) Review Logs & Comment History: Exported or linked code reviews demonstrating thorough analysis of other developers' work, focusing on architectural alignment, edge-case validation, and security practices.
• Automated Test & Code Quality Reports: Baseline and current reports from tools like SonarQube, checkstyle, or built-in framework linters showing maintained or improved code coverage, security vulnerability drops, and reduced technical debt.
• CI/CD Pipeline Configurations: Documented YAML files or build definitions (e.g., GitHub Actions, Azure DevOps Pipelines) proving they established or optimized automated deployment and validation processes.
• System Architecture Diagrams: Visual representations of the platform layout, data flow, and components (e.g., UML diagrams, C4 Model contexts, or cloud infrastructure maps).
• Data Models & Entity Relationship Diagrams (ERDs): Documented schemas detailing how data is structured, stored, and related, ensuring long-term database integrity.
• API & Integration Contracts: Swagger/OpenAPI specifications, data mapping sheets, or MuleSoft/iPaaS configuration designs outlining exactly how data transfers between multi-platform applications securely.
• Technical Discovery & Spiking Summaries: Short, written summaries of Proofs of Concept (PoCs) or technical "spikes" that outline feasibility, tool evaluations, and clear recommendations for the path forward.
• Technical Debt Registers / Risk Matrix: A documented backlog or log identifying current architectural weaknesses, security gaps, or compliance risks, accompanied by estimated effort and impact levels for remediation.
• Detailed Estimation & Task Breakdowns: Jira epics, Azure DevOps features, or work breakdown structures (WBS) showing vague business requirements translated into granular, estimated, and sequenced technical tasks.
• System Runbooks & Deployment Guides: Step-by-step instructions for environment provisioning, configuration settings, manual deployment steps (if any), and disaster recovery procedures.
• Troubleshooting and Incident Post-Mortems: Root Cause Analysis (RCA) documents detailing complex production bugs, why they happened, how they were resolved, and the preventative measures implemented
• Developer Onboarding and Setup Documentation: A comprehensive "Readme" or wiki page detailing how a new developer sets up their local environment, runs the codebase, and adheres to team coding standards.

Required Skills :

Basic Qualification :

Additional Skills :

Background Check : No

Drug Screen : No