INTERVIEW= Onsite / Virtual
JOB TYPE= Onsite

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 4040 Esplanade Way, Tallahassee, Florida is required. Remote work may be considered on an occasional, ad-hoc basis, subject to prior written approval from the Contract Manager. This arrangement is intended for intermittent use only and does not constitute a permanent or hybrid remote work schedule. Travel costs will not be reimbursed.
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
5.2.
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.

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.
4.3.
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 Client 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.