Position: Technical Writer
Agency/Program: KY OAG – Child Support Services (KASES III)
Work Location: Frankfort, KY (Hybrid; onsite for key meetings) Remote OK
Office of Information Services Engagement Type: Contract (Full-time)
Position Summary
Produce clear, accurate, audit-ready documentation that a third party can execute without re-interviewing subject matter experts. Scope covers all Child Support Systems and Services and key projects chartered by the Office of Information Systems including migration of child support technologies to a major cloud provider (AWS or Azure): installation, configuration, operation, troubleshooting, cutover, hypercare, and support.
Duties and Responsibilities1
• Write and edit installation, configuration, how-to, troubleshooting, and online help for: o Cloud landing zone (AWS or Azure equivalents).
· Application stack (.NET/Angular, and any platform-specific deployment/run details). o Data tier (AWS RDS/Aurora/SQL Server or Azure SQL).
· Batch/scheduler (Control-M; note any cloud-native hooks such as Event Grid/EventBridge, Functions/Lambda). o Interfaces (file/API; API Management/API Gateway, Key Vault/KMS, Private Endpoint/PrivateLink).
• Publish runbooks/playbooks (batch, interfaces, monitoring/alerts, cutover/rollback, hypercare) with change history.
• Maintain a single, versioned documentation repository (SharePoint/Confluence) with metadata (system, partner, cadence, PII flag) and links to code/configs.
• Convert SME notes into step-by-step procedures (screenshots, scripts, commands). Deliverables • Install/config guides (cloud landing, app, data, scheduler). • Interface runbooks and cutover/rollback checklists.
• Troubleshooting trees and “first-response” procedures.
• Online help; quick-reference job aids.
• Versioned doc set per release. MUST-HAVE Requirements (non-negotiable)
• ≥ 5 years enterprise technical writing with hands-on runbooks/ops docs (samples required). 1 • Demonstrated modernization documentation (legacy → cloud) with legacy + target flows.
• Ability to capture runbooks for: Control-M, interfaces (file/API), SQL platform (AWS RDS/Aurora or Azure SQL), .NET/Angular, and enterprise identity (e.g., Entra ID or AWS IAM/IAM Identity Center).
• Single-source practice (SharePoint/Confluence) with versioning/metadata. • Plain-English writing for technical and non-technical audiences; passes peer review without rewrite. Preferred Qualifications
• State/federal modernization; familiarity with PII safe-harbor (masking in non-prod; encryption in transit/at rest).
• Observability docs (App Insights/Log Analytics or CloudWatch/CloudTrail/OpenSearch). Tools and Platforms Microsoft 365, SharePoint/Confluence, Visio/Lucid, ServiceNow, Git (versioning); Cloud services: Azure (App Gateway/Firewall, Key Vault, Private Endpoint) or AWS (ALB/NLB/WAF, KMS/Secrets Manager, PrivateLink). Performance Measures • Doc completeness/accuracy (review pass rate).
• Findability and update turnaround
. • Reduction in support escalations tied to unclear instructions. Submission & Screening
• Two recent samples: (1) install/config guide, (2) runbook/playbook. • 30-minute rewrite test from raw SME notes.