Job description

A leading organization is seeking a Systems Analyst to support a data annotation and review platform. The Systems Analyst will focus on designing workflows, improving review processes, supporting data movement, and helping technical teams use the platform effectively. The position will collaborate closely with data science teams to turn operational needs into efficient, well-defined system workflows.

Responsibilities

• Design and document data annotation workflows.
• Define structured review processes for annotation activities.
• Analyze and optimize end-to-end workflows to improve operational efficiency.
• Partner with data science teams to support effective tool adoption.
• Map data movement and integrations between systems.
• Use SQL to support data analysis and workflow requirements.
• Develop process and workflow documentation using tools such as Visio.
• Help establish consistent processes for moving data into and out of the platform.

Required experience and skills

• Experience designing annotation or data-focused workflows.
• Experience defining and improving review processes.
• Ability to analyze and optimize end-to-end workflows.
• SQL experience.
• Experience with APIs and data mapping.
• Experience using Visio or similar process-mapping tools.
• Ability to work effectively with data science teams on technical workflows and tool adoption.

FAQs

1. What does a Systems Analyst do?

A Systems Analyst evaluates business processes and technology systems to identify requirements, resolve problems, and improve how applications support organizational needs. The role often bridges business stakeholders and technical teams by translating operational requirements into practical system solutions.

2. How does a Systems Analyst gather and document requirements?

Systems Analysts gather requirements through stakeholder interviews, process reviews, workshops, existing-system analysis, and documentation reviews. They translate findings into functional requirements, workflows, use cases, process diagrams, and other specifications that guide development or system changes.

3. How does a Systems Analyst analyze existing systems?

The analyst reviews application functionality, data flows, integrations, business processes, and system dependencies to understand how the current environment operates. This analysis helps identify inefficiencies, gaps, risks, technical constraints, and opportunities for improvement.

4. What role does a Systems Analyst play in application integrations?

Systems Analysts help define how applications exchange information and how changes in one system may affect others. They may document APIs, data mappings, integration workflows, business rules, error scenarios, and dependencies to support reliable system-to-system communication.

5. How does a Systems Analyst work with developers?

The analyst provides developers with clear requirements, process flows, business rules, data requirements, and acceptance criteria. Throughout development, they clarify questions, review proposed solutions, validate functionality, and help ensure the delivered system meets the original business need.

6. What tools are commonly used by Systems Analysts?

Systems Analysts may use SQL, Excel, Jira, Confluence, Visio, Lucidchart, diagramming tools, requirements-management platforms, and application monitoring or reporting tools. The specific toolset depends on the organization's technology environment and development methodology.

7. How does a Systems Analyst troubleshoot system issues?

Troubleshooting typically involves reproducing the issue, reviewing system behavior and logs, tracing data flows, examining integrations, and identifying the source of the problem. Analysts collaborate with technical teams to determine root causes and validate fixes before changes are released.

8. What role does SQL play in systems analysis?

SQL can help Systems Analysts investigate application data, validate business rules, identify data inconsistencies, and understand relationships between database entities. It is particularly useful when analyzing system behavior or verifying whether technical changes produce the expected data results.