Lead Platform Engineer (Framework)

Mandatory Requirements

• More than seven (7) years of experience, with at least two (2) years in a leadership role.
• Five (5) years of experience designing and developing reusable software libraries, SDKs, or core frameworks used across multiple development teams.
• Five (5) years of advanced programming experience in Java.
• Five (5) years authoring technical documentation.

Desirable Qualifications

• 5 years of experience with software design patterns, dependency injection, and API design principles.
• 5 years of experience publishing and managing software packages to JFrog Artifactory
• 5 years of experience with CI/CD pipelines and build automation tools using GitLab
• 5 years of experience writing comprehensive unit tests and integration tests for shared libraries.

Position Overview & Key Responsibilities

The Lead Platform Engineer (Framework) (Specialist III) is a senior software architect and platform engineering lead responsible for designing, developing, and governing the core software frameworks, SDKs, and reusable libraries used across all enterprise application development teams. Operating as a "developer's developer," you will establish the foundational software architecture, API design principles, and security baselines that accelerate application delivery and ensure system consistency. This role requires advanced programming expertise in Java or C#, deep knowledge of modern software design patterns, and the leadership capabilities necessary to govern the shared codebase, manage package repositories, and enable development teams across the agency.

Core Framework & SDK Architecture

Architect, develop, and maintain high-performance, reusable software libraries, SDKs, and shared services in Java or C# to standardize common application capabilities (e.g., authentication, logging, data access, and integration).

• API Design & Software Patterns: Apply advanced software design patterns, dependency injection, and clean API design principles to ensure shared components are intuitive, modular, highly extensible, and loosely coupled.
• Package Management & Release Engineering: Publish, version, and manage software packages using enterprise repository managers (e.g., Nexus, Artifactory, Maven Central, NuGet). Enforce semantic versioning and strict backward-compatibility standards to ensure seamless upgrade paths for consumer applications.
• CI/CD & Build Automation: Design and optimize automated build pipelines and CI/CD workflows using tools like Maven, Gradle, or npm to automate the testing, packaging, and deployment of shared frameworks.
• Rigorous Testing & Quality Assurance: Establish and execute comprehensive automated testing strategies, including unit, integration, and regression test suites, specifically designed to validate the reliability and security of shared libraries.
• Architectural Governance & Standards: Define, document, and enforce enterprise-wide coding standards, architectural patterns, and security baselines within the shared codebase to minimize technical debt and security vulnerabilities.
• Developer Enablement & Collaboration: Partner closely with application development teams to facilitate the integration of shared frameworks, troubleshoot complex technical challenges, author comprehensive developer guides and code samples, and conduct technical training sessions.