Release and Engagement Coordinator

Electrosoft Services, Inc. is an award-winning company that provides comprehensive technology-based solutions and services to federal customers. While cybersecurity is our specialty, we also focus on ICAM, enterprise IT modernization, and software solutions. We always seek to delight our customers, so we retain highly qualified employees and offer them meaningful work, growth opportunities, and work-life balance. What sets us apart from all other contractors is the sense of teamwork our employees feel – and the knowledge that outstanding effort is recognized and rewarded. The camaraderie we share emanates from Lunch & Learn sessions where we explore new ideas together, fun group activities ranging from escape rooms to miniature golf, and much, much more. If we’ve described you and your dream workplace, please apply and share in the many benefits and opportunities we offer.

Release & Engagement Coordinator

The Contractor shall be capable of performing the tasks and/or possess the skill sets listed below:

• Tracks release timelines, QA milestones, and stakeholder inputs to ensure alignment with planned deployment windows.
• Prepares and routes communication materials such as bulletins, timeline reminders, and stakeholder notifications.
• Supports coordination across internal teams (developers, testers) and external stakeholders (OpDiv release contacts), ensuring schedule awareness.
• Documents change tracking inputs, integrates release artifacts into ServiceNow/Remedy, and ensures accessibility of deliverables.
• Assists with demo scheduling and readiness communications but does not lead validation or decision-making.
• Supports maintenance of release checklists, issue logs, and documentation archives to assist senior staff with audit readiness.
• Facilitates requirements workshops and stakeholder interviews to gather process flows, system gaps, and compliance reporting needs.
• Prepares user stories, acceptance criteria, and mockups for use by developers and testers.
• Works with Product Owners to validate feature priorities and ensure implementation matches stakeholder intent.
• Supports traceability from requirement gathering through release and post-implementation testing.
• Documents change requests and assists in impact assessments for existing GRC platform and application modules.
• Coordinates with QA and development teams to ensure requirements are testable and documented in OSCAL-compatible structures when applicable.
• Supports version-controlled documentation practices using tools like SharePoint or Confluence.

Basic Qualifications

• Possesses 3–5 years of experience supporting enterprise-level IT releases and coordinating logistics and release documentation activities.
• Candidate to possess Bachelor’s degree from an accredited institution in Information Systems, Information Technology, Computer Science, Business/Management Information Systems, Systems Engineering, Public Administration, or a closely related field with over 5 years of directly related experience (release coordination, ServiceNow/Remedy workflow administration, requirements documentation for enterprise IT) to be accepted as an equivalent.
• Familiar with Enterprise Governance, Risk, and Compliance (GRC) platform release checkpoints, system architecture, and documentation workflows in use at HHS.
• Demonstrates strong attention to detail, follow-through, and ability to coordinate tasks across multiple workstreams.
• Demonstrates strong communication and documentation skills with the ability to interface between technical and business audiences.
• Familiar with GRC platform and application workflows, field types, and application builder tools preferred.
• Exposure to RMF-aligned planning, ATO documentation, and OSCAL structure is preferred.
• Supports formatting and routing of OSCAL-compliant records under guidance from senior staff.
• Must be familiar with and adhere to the full Enterprise Performance Lifecycle (EPLC) and defined Software Development Life Cycle (SDLC) policies. This includes responsibility for documenting design, implementation, testing, deployment, rollback, and lessons learned. Any and all alterations, changes, or modifications to a GRC/Archer Production type environment must be processed through the Change Control Board (CCB) with clear risk analysis, system impact reviews, and rollback procedures.