DevOps/Deployment Engineer

Lentech Inc.•Elkridge, MD

About The Position

Lentech is seeking a high-Performance, multi-disciplinary team to lead a technical implementation of a Microsoft Dynamics 365 and Power Platform-based case management system (CMS). This mission-critical project and CMS supports legal services to children in support of the U.S. Government. U.S. Citizenship is required along with the ability to positively pass a public trust background investigation. The primary implementation timeline occurs across the first 180 days of the project and moves into steady state operations for the remainder of the first year. A five-year follow-on contract is expected based on positive performance in the first year. The implementation follows an aggressive timeline divided into four key phases: Mobilization, Core Operations, Fully Functional Delivery, and Steady-state Operations. This effort demands a collaborative team capable of maintaining operational continuity throughout the transition and into operations. You will be working with a primary legal team providing the CMS to the lawyers working each individual case. Candidates must be prepared to handle high-velocity delivery, strict data privilege boundaries, and the technical rigor required to support vulnerable populations. Role Overview: The DevOps/Deployment Engineer is a critical technical role responsible for the automation, security, and integrity of the system’s release cycle during the implementation and supporting day to day operations of the environment post implementation. Responsibilities include establishing a robust Application Lifecycle Management (ALM) foundation and executing secure, repeatable deployments across the environment path.

Requirements

7+ years experience
Extensive experience with Azure DevOps and CI/CD for the Power Platform, specifically regarding managed solutions and solution checker integration.
Proven experience managing Government Community Cloud (GCC) environments and implementing security-aware deployment patterns.
Understanding of Azure integration services and the ability to manage secret storage for complex "reversible adapter" designs.
Experience in a "requirements-first" delivery model, ensuring that every release and configuration item is traced within the Requirements Traceability Matrix (RTM).
One of the following certifications: MS DevOps Engineer Associate, Power Platform Developer Associate or Azure Administrator Associate
U.S. Citizenship is required
Ability to pass a public trust background investigation

Responsibilities

Design and maintain automated deployment pipelines to move managed solutions and configurations between Development, Test, UAT, and Production environments.
Provision the agreed-upon ALM foundation during the Mobilization and Foundation (R0) phase, including source control integration, solution checking, and release approval workflows.
Implement and manage secure secret storage for credentials and connection strings, ensuring environment-specific variables and connection references are externalized from the core CMS.
Develop and execute detailed cutover and rollback plans for each release window (R1, R2, and R3), including performing at least one formal rehearsal in a non-production environment.
Maintain a comprehensive configuration-item inventory and baseline manifest covering all solutions, flows, custom components, and environment settings.
Support the final go/no-go criteria by conducting production validation to confirm that workflows, reports, automations, and monitoring are operational before broad release.
Document the environment topology and automated CI/CD path.
Create detailed step-by-step guides for production deployment, including rollback checkpoints and interim operational procedures.
Develop monitoring and alerting plans, deployment records, and environment manifests required for the final handoff to the Organization.
Ensure the solution remains supportable and deployable without reliance on undocumented vendor knowledge.
Establish automated guardrails and secure deployment practices early in the 120-day timeline to mitigate the risk of manual configuration errors and ensure the Organization can maintain the system independently following the final transition.