> Markdown version of [/jobs/ext/3875536-technical-analyst](https://www.wearedevelopers.com/jobs/ext/3875536-technical-analyst). Every page supports `.md` or `Accept: text/markdown`. Links point to the HTML versions so they work for humans too. Agent guide: [/agents.md](https://www.wearedevelopers.com/agents.md).

---

# Technical Analyst

- **Company:** Net2Source
- **Location:** Riverview, FL, United States (Remote available)
- **Experience:** Expert
- **Salary:** $89,190.0 - $99,590.0
- **Contract:** Permanent contract
- **Skills:** Application Programming Interfaces (APIs), JIRA, Extract Transform Load (ETL), Data Migration, Middleware, Microsoft Visio, Lucidchart, Salesforce.Com, Data Streaming, Systems Integration, Gitlab, OSS/BSS, Tools for Reporting
- **Published:** October 22, 2026
- **Apply:** https://www.careerbuilder.com/job-details/technical-analyst-tampa-fl--1c852993-6656-4f34-a246-1b9b8b3169a0

## About the Role

Technical Analysis, Technical Analysis, Technical Writing, Operational Support Systems (OSS), Customer Relationship Management (CRM) Systems, Billing, Technical Support, Documentation, System Integration (SI), Business Architecture, Experience level: This is not an entry-level position. Candidates are expected to work independently and bring prior experience documenting complex system integrations., Proven technical writing experience documenting complex systems and integrations for mixed technical/business audiences.
Demonstrated ability to produce architecture diagrams and data flow diagrams (e.g., Visio, Lucidchart, draw.io, Mermaid, or equivalent).
Ability to read and interpret data models - source/destination tables, field mappings, and how data is used in workflows.
Experience decomposing workflows into development-ready user stories with acceptance criteria.
Strong interviewing and requirements-elicitation skills; able to extract accurate detail from system owners and subject matter experts.
Excellent written communication and the ability to tailor material from detailed technical specs up to leadership-level summaries.
Preferred Qualifications
Familiarity with OSS/BSS domains - billing and CRM systems in telecommunications.
Hands-on exposure to Salesforce, BMC Remedy (or comparable ITSM/ticketing platforms), and BI/reporting tools.
Experience supporting data migration or system convergence programs, especially mergers/integrations.
Understanding of integration patterns (APIs, ETL, middleware) and how systems are linked in practice.
Experience working within Agile delivery and writing stories in tools such as Jira or GitLab.

## Description

We are seeking a Technical Writer to support the OSS/BSS Migration program, which addresses the convergence of Cox and Charter billing and CRM systems. This role is focused on decomposing complex, cross-system workflows into clear architecture and data flow documentation that feeds directly into the creation of development user stories.
This is a documentation and analysis role at the intersection of business workflows and system integration. The ideal candidate is as comfortable interviewing system owners as they are diagramming how data moves between Salesforce, business intelligence platforms, and support systems such as BMC Remedy.
Engagement Details, Decompose system and business workflows into architecture diagrams and data flow diagrams (DFDs) that communicate clearly to both technical and non-technical audiences.
Document integrations across Salesforce (CRM), BI/reporting platforms, and support systems (e.g., BMC Remedy for ticketing), including how these systems exchange and consume data.
Map source and destination data - tables, fields, and records - and describe how that data is used within end-to-end workflows.
Identify and document gaps, risks, and open questions that must be resolved as Cox accounts are migrated into Charter billing systems.
Translate finished workflow and integration documentation into well-formed development user stories with clear acceptance criteria.
Partner with system owners, architects, and business stakeholders through interviews and working sessions to capture accurate current-state and target-state detail.
Maintain consistent, reusable documentation artifacts as the program evolves.