

SPADTEK SOLUTIONS
Technical Business Analyst
β - Featured Role | Apply direct with Data Freelance Hub
This role is for a Technical Business Analyst in Alpharetta, GA, onsite for 5 days. Contract length and pay rate are unspecified. Key skills include SQL, documentation, Agile methodologies, and UAT. Experience in business analysis and systems analysis is required.
π - Country
United States
π± - Currency
$ USD
-
π° - Day rate
Unknown
-
ποΈ - Date
April 17, 2026
π - Duration
Unknown
-
ποΈ - Location
On-site
-
π - Contract
Unknown
-
π - Security
Unknown
-
π - Location detailed
Alpharetta, GA
-
π§ - Skills detailed
#API (Application Programming Interface) #Databases #Scrum #UAT (User Acceptance Testing) #Business Analysis #Documentation #Jira #Microsoft Excel #SQL Queries #"ETL (Extract #Transform #Load)" #Agile #SQL (Structured Query Language) #Stories #Data Mapping
Role description
Location: Alpharetta, GA 30009
Onsite
β’ 5 days in office
Job Summary
β’ The Technical Business Analyst will work closely with business owners, users, and technical teams to identify operational needs, document detailed business rules, and translate them into actionable technical requirements for software development.
β’ This role ensures that technical solutionsβwhether custom applications, APIs, or data systemsβare aligned with business goals and efficiently implemented.
Responsibilities
β’ Requirements Elicitation & Gathering: Lead interviews, workshops, and brainstorming sessions to discover, analyze, and define functional and non-functional requirements from diverse stakeholders.
β’ Documentation & Business Rules: Write comprehensive, well-structured documentation including Business Requirement Documents (BRDs), Functional Requirements Documents (FRDs), Use Cases, and User Stories.
β’ Technical Translation: Translate business requirements into clear, technical specifications (e.g., API specifications, database mappings, system workflows) for developers and engineers.
β’ Process Modeling: Analyze and map "as-is" and "to-be" business processes using tools like Visio, or Lucidchart to identify inefficiencies and improvements.
β’ Backlog Management: Work closely with Product Owners to define, prioritize, and groom the product backlog, transforming high-level features into detailed user stories and acceptance criteria.
β’ Systems Analysis & Data Mapping: Perform data discovery, analysis, and modeling to understand how data flows through systems (e.g., SQL queries, API payload analysis).
β’ Solution Validation (UAT): Develop test scenarios and acceptance criteria; support or lead User Acceptance Testing (UAT) to validate that solutions meet defined requirements.
β’ Liaison Function: Act as the primary technical liaison between business units and IT, facilitating communication to ensure alignment on project goals
Knowledge & Skills
β’ Documentation: Extensive experience writing BRDs, FRDs, Use Cases, and Functional Specifications.
β’ Technical Knowledge: Proficiency in SQL for querying databases, data mapping, and analysis.
β’ SDLC/Agile Methodologies: Familiarity with Agile, Scrum, or Waterfall frameworks.
β’ Tools: Proficient in Jira, Confluence, Microsoft Visio, Microsoft Excel, and wireframing tools (e.g., Figma).
β’ Analytical Skills: Strong analytical and critical thinking skills, with the ability to break down complex problems and interpret large data sets.
β’ Communication: Excellent written and verbal communication skills, with the ability to bridge technical and non-technical teams
Location: Alpharetta, GA 30009
Onsite
β’ 5 days in office
Job Summary
β’ The Technical Business Analyst will work closely with business owners, users, and technical teams to identify operational needs, document detailed business rules, and translate them into actionable technical requirements for software development.
β’ This role ensures that technical solutionsβwhether custom applications, APIs, or data systemsβare aligned with business goals and efficiently implemented.
Responsibilities
β’ Requirements Elicitation & Gathering: Lead interviews, workshops, and brainstorming sessions to discover, analyze, and define functional and non-functional requirements from diverse stakeholders.
β’ Documentation & Business Rules: Write comprehensive, well-structured documentation including Business Requirement Documents (BRDs), Functional Requirements Documents (FRDs), Use Cases, and User Stories.
β’ Technical Translation: Translate business requirements into clear, technical specifications (e.g., API specifications, database mappings, system workflows) for developers and engineers.
β’ Process Modeling: Analyze and map "as-is" and "to-be" business processes using tools like Visio, or Lucidchart to identify inefficiencies and improvements.
β’ Backlog Management: Work closely with Product Owners to define, prioritize, and groom the product backlog, transforming high-level features into detailed user stories and acceptance criteria.
β’ Systems Analysis & Data Mapping: Perform data discovery, analysis, and modeling to understand how data flows through systems (e.g., SQL queries, API payload analysis).
β’ Solution Validation (UAT): Develop test scenarios and acceptance criteria; support or lead User Acceptance Testing (UAT) to validate that solutions meet defined requirements.
β’ Liaison Function: Act as the primary technical liaison between business units and IT, facilitating communication to ensure alignment on project goals
Knowledge & Skills
β’ Documentation: Extensive experience writing BRDs, FRDs, Use Cases, and Functional Specifications.
β’ Technical Knowledge: Proficiency in SQL for querying databases, data mapping, and analysis.
β’ SDLC/Agile Methodologies: Familiarity with Agile, Scrum, or Waterfall frameworks.
β’ Tools: Proficient in Jira, Confluence, Microsoft Visio, Microsoft Excel, and wireframing tools (e.g., Figma).
β’ Analytical Skills: Strong analytical and critical thinking skills, with the ability to break down complex problems and interpret large data sets.
β’ Communication: Excellent written and verbal communication skills, with the ability to bridge technical and non-technical teams






