Business Process Analyst / Technical Writer

**Benefits:** * 401(k) * Competitive salary * Dental insurance * Health insurance * Vision insurance **Title \- Business Process Analyst / Technical Writer** **Client \- NOAA** **Location \- Remote** **Duration \- 1 year contract** Key Responsibilities Meeting Attendance and Information Gathering * Attend up to four to five virtual meetings per week with NOAA OAR administrative teams and up to three to four per week with portal development staff. * Come to each session prepared with a structured agenda and specific open questions rather than attending passively. * Capture meeting minutes, decisions, and action items, and issue them within one business day. * Maintain a running action item register with named owners and due dates, reconciled at each subsequent session. **SOP Compilation and Formatting** * Compile administrative workflows into clear, accurate Standard Operating Procedures suitable for handoff to developers. * Apply a single standardized template across all teams so the SOP library is consistent from the first document to the last. * Return drafts to the owning team for validation, adjudicate comments, and manage version control and change logs. * Deliver SOPs iteratively as teams complete them, and assemble a consolidated final package at the end of the engagement. **Portal Requirements Documentation** * Decompose validated SOPs into discrete, testable requirement statements written for programmers, not administrators. * Assign each requirement a unique identifier, a source reference, a priority, and an acceptance criterion. * Map user workflows to ticketing system capabilities, including roles, request types, routing rules, status transitions, approvals, notifications, and exception handling. * Maintain full traceability from SOP section to requirement to portal capability, and manage the requirements baseline through a logged change process. **Cross\-Team Coordination** * Identify where administrative teams handle the same function differently, and log each discrepancy with both variants and the rationale behind them. * Convene the affected team leads and drive reconciliation at the working level, escalating only where teams cannot agree — and escalating with options and a recommendation, not an open question. * Communicate approved documentation changes to affected team leads proactively so alignment is maintained rather than periodically restored. **Portal Developer Coordination** * Serve as the single interpretive channel between administrative intent and system configuration. * Acknowledge developer questions within one business day and provide a substantive answer or a scheduled working session within three. * Where a technical constraint makes a documented workflow unbuildable, return to the process owner with the constraint and a proposed alternative. * Deliver workflow and configuration data in the structure the development team has agreed to consume. **User Instr