On-Site Senior Application Developer (Microsoft Dynamics/Power Platform; web platform development; Data modeling; Snowflake pipeline creation; Team Dynamix iPaaS; Odoo/Azure DevOps)

Note : Please reply ONLY if you
1) Can work 100% on-site from day one. NO REMOTE option allowed
2) have all the Required skill set and have worked as an "On-Site Senior Application Developer (Microsoft Dynamics/Power Platform; web platform development; Data modeling; Snowflake pipeline creation; Team Dynamix iPaaS; Odoo/Azure DevOps)
 in a large & Complex enterprise level IT Environment.
3) Minimum of 13-15 years of combined IT and security work experience with a broad range of exposure to systems analysis, applications development, and database design and administration, 
4) can provide at least 3 verifiable experience from completed and/or substantially completed jobs that closely match this request (Filling the client provided form) + fill out a skill Matrix + Sign Resume certification form
5) Can go through a background check including fingerprinting + Agree to a Face to face interview OR a WEB CAM Interview
6) A Competitive Rate
7) will be available Nov/Dec 2026 to start at the project.

s and those authorized to work in the US are encouraged to apply.  We are unable to sponsor H1b candidates at this time.
NOTE: GIS will utilize the U.S. Department of Homeland Security's E-Verify system to verify the employment eligibility of all persons employed during the term of the Contract
Note to Consulting Companies : ANY CONSULTANT’S RESUME YOU SEND ME “MUST” BE ON YOUR COMPANY’S PAYROLL, NO H1-VISA TRANSFER, NO PRO-MARKETING, NO SISTER COMPANY RESUMES.
The resume should have the DIRECT contact info and email of the candidate otherwise the candidate will NOT be considered.
ALL H1 candidates including those onWOULD need to provide I-797 + DL copy (no exceptions).

Each staff member assigned to this project must have a background screening that is equivalent to a Level Two (2) screening standard.
This is a fixed fee/hourly based project which is inclusive of travel, lodging, per diem expenses and all other costs associated with the completion of the associated tasks.

Interviews: 
In the event an interview is requested; 1st round interviews will be conducted via web Cam. The client may ask for 2nd round F-2-F and no expenses are paid
Telecommuting: 
Not allowed for this position.

Education: Bachelor’s degree in computer science, information systems, cybersecurity, or a related field, or equivalent work experience; and at least two current industry certification from the following (others may be considered):

BACKGROUND/OVERVIEW
The Department is seeking quotes from Contractors to provide one (or two) experienced Senior Developers with strong communication skills and expertise in managing highly complex applications pertaining to Microsoft Dynamics, Microsoft Power Platform, SaaS Solutions, and various methods of application integrations (i.e. leveraging APIs, as well as file transfer and transformation processes).

SCOPE OF WORK
4.1.
The Contractor shall provide Information Technology (IT) staff augmentation services in support of the Department’s Office of Information Technology (OIT). The Contractor must propose at least one qualified Senior Developer in its Response who in the Department’s sole discretion has the experience and ability to fulfill the requirements of this Scope of Work (SOW). The Department may fill one or multiple positions from this RFQ based on experience and ability to fulfill the requirements of this Scope of Work (SOW).
The Senior Developer position is anticipated to be Full-Time.
4.2.
On an ongoing basis, the Senior Developer will report to the Application Development and Support manager, the designated Contract Manager (Section 15). 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.
4.3.1. High-Impact Technical Delivery Activities. The Senior Developer will tackle the tasks that require the highest degree of critical thinking and risk management.
4.3.1.1. 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).
4.3.1.2. 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.
4.3.1.3. 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.
4.3.2. 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.
4.3.2.1. Conducting Rigorous Code Reviews: Reviewing pull requests not just for syntax, but for architectural alignment, security vulnerabilities, edge-case handling, and test coverage.
4.3.2.2. Managing Tech Debt and Refactoring: Actively identifying rotting code or rigid architectures, documenting the risk, and systematically refactoring components during appropriate sprint windows.
4.3.2.3. Defining and Enforcing Engineering Standards: Establishing linting rules, branching strategies, automated testing protocols, and continuous integration/continuous deployment (CI/CD) pipelines to streamline delivery.
4.3.2.4. 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.
4.3.3. Project Scoping and Business Alignment Delivery Activities. The Senior Developer will bridge the gap between business requirements and technical execution before development begins.
4.3.3.1. 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.
4.3.3.2. Risk Assessment and Mitigation: Flagging potential compliance, security, or performance risks early in the planning lifecycle and designing technical workarounds.
4.3.3.3. Evaluating Third-Party Tools: Assessing vendor software, APIs, or iPaaS platforms to ensure they meet the organization’s technical, security, and integration standards.
4.3.4. 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..
4.3.4.1. 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.
4.3.4.2. Leading Technical Knowledge Discussions: Introducing the team to new tools, design patterns, or platform updates.
4.3.4.3. 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.

4.4. Contract Deliverables. Contractor’s Senior Developer shall perform the tasks listed in Section 4.3., above. The Contractor shall invoice these tasks to the Department in one-hour increments, at the fixed hourly rate specified in the Attachment A – Price Sheet attached to this RFQ. The Senior Developer shall provide evidence of performance by submitting documentation exampled in the list below. Documentation shall be submitted in a format compatible with MS Office 2013, or newer. All deliverable documentation must be satisfactorily completed within the response time specified within this RFQ or by operational/project plan and accepted by the Department’s Contract Manager.
4.4.1. 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.
4.4.2. 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.
4.4.3. 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.
4.4.4. System Architecture Diagrams: Visual representations of the platform layout, data flow, and components (e.g., UML diagrams, C4 Model contexts, or cloud infrastructure maps).
4.4.5. Data Models & Entity Relationship Diagrams (ERDs): Documented schemas detailing how data is structured, stored, and related, ensuring long-term database integrity.
4.4.6. API & Integration Contracts: Swagger/OpenAPI specifications, data mapping sheets, or MuleSoft/iPaaS configuration designs outlining exactly how data transfers between multi-platform applications securely.
4.4.7. 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.
4.4.8. 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.
4.4.9. 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.
4.4.10. System Runbooks & Deployment Guides: Step-by-step instructions for environment provisioning, configuration settings, manual deployment steps (if any), and disaster recovery procedures.
4.4.11. 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
4.4.12. 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.

QUALIFICATION REQUIREMENTS FOR SECURITY ANALYST
The Security Analyst candidate(s) submitted by Contractor to provide these staff augmentation services must possess the following minimum qualifications and experience:
Minimum of 13-15 years of combined IT and security work experience with a broad range of exposure to systems analysis, applications development, and database design and administration, 

5.1. The Senior Developer candidate(s) submitted by the Contractor to provide these staff augmentation services must possess the following minimum qualifications and experience:
5.1.1. Possess the professional and technical skills necessary to perform advanced development activities.
5.1.2. Minimum of 7 years in multiple IT areas requiring advanced to expert level knowledge and understanding of application systems design and integrations. Experience working on projects in multiple technologies and functions.
5.1.3. On-site availability at the Department’s location 

5.1.4. Educational Requirements. The Contractor Senior Developer, and any subsequent Contractor Senior Developer provided by the Contractor, must possess, at a minimum, one of the following:
5.1.4.1. Bachelor’s degree in computer science, information systems, or other related fields, or equivalent work experience.
5.1.5. Expertise in analysis, research, and documentation.
5.1.6. Expertise in the Software Development Lifecycle (SDLC).
5.1.7. Advanced to expert level knowledge in Microsoft Dynamics and Microsoft Power Platform.
5.1.8. Advanced to expert level knowledge in web platform development
5.1.9. Advanced to expert level knowledge in data modeling
5.1.10. Advanced to expert level knowledge in communication skills

The Senior Developer candidate(s) submitted by the Contractor to provide these staff augmentation services may possess the following preferred qualifications and experience:
5.2.1. FLAIR (Florida Accounting Information Resource) data transfers and transformation for internal Department accounting systems.
5.2.2. PALM (Planning, Accounting, and Ledger Management) data transfers and transformation for internal Department accounting systems.
5.2.3. Snowflake pipeline creation.
5.2.4. Team Dynamix iPaaS.
5.2.5. Odoo.

Facilities and Equipment
The Department will provide items such as working facilities, development and testing environments, equipment and software licenses, access to the Department’s network, and internet connectivity, etc. Note: A Contractor Representative with access to the Department’s network is required to complete the Department’s security awareness training.  This training must be completed within fifteen (15) calendar days of the Contractor Representative’s start date.  If the Contractor Representative uses his or her own computer laptop, the equipment must undergo a security review by the Department to ensure it is free of software viruses and does not otherwise pose a security threat, prior to connection to the Department’s network.

"When replying please make sure to list your (All Inclusive) Compensation requirements !!!"

Note : This is a Full time ON SITE Contract Position with no REMOTE options allowed !!

Start date : Nov/Dec 2026
# OF POSITIONS : 1

No phone calls please.
Local Citizens are encouraged to Apply
No relocation assistance provided.
ONLY Candidates with an exact match will be contacted
Candidates should be authorized to work in the US.