Innovatix Technology Partners
Technical Business Analyst
⭐ - Featured Role | Apply direct with Data Freelance Hub
This role is for a Technical Business Analyst in Plano, TX, for 10 months at a pay rate of "TBD". Key skills include API fundamentals, SQL, data modeling, and familiarity with Java. Hybrid work requires 2-3 days in-office weekly.
🌎 - Country
United States
💱 - Currency
$ USD
-
💰 - Day rate
Unknown
-
🗓️ - Date
March 7, 2026
🕒 - Duration
More than 6 months
-
🏝️ - Location
Hybrid
-
📄 - Contract
Unknown
-
🔒 - Security
Unknown
-
📍 - Location detailed
Plano, TX
-
🧠 - Skills detailed
#Logging #Swagger #REST (Representational State Transfer) #Normalization #POSTMAN #Scala #XML (eXtensible Markup Language) #Security #JSON (JavaScript Object Notation) #Data Modeling #Java #SQL (Structured Query Language) #Observability #Business Analysis #SQL Queries #Schema Design #Documentation #API (Application Programming Interface) #Kafka (Apache Kafka) #Spring Boot
Role description
Job title: Technical Business Analyst
Location: Plano, TX
Mode of work: Hybrid, 2-3 days per week
Duration: 10 months
Skills Required:
API fundamentals (REST/HTTP)
Understand REST principles, HTTP methods (GET/POST/PUT/DELETE), status codes, headers, caching, idempotency.
API specification & documentation (OpenAPI/Swagger)
Ability to read and help author API contracts (OpenAPI), define endpoints, request/response schemas, examples, and error models.
Data modeling & JSON/XML proficiency
Strong grasp of JSON structures, schema design, serialization concepts, and when XML may be relevant.
SQL and database concepts
Write and interpret SQL queries, understand joins, indexes, transactions, normalization, and how APIs interact with persistence layers.
Integration concepts & patterns
Familiarity with synchronous vs asynchronous integration, webhooks, messaging basics (e.g., Kafka/RabbitMQ concepts), and common integration pitfalls.
Java & Spring ecosystem awareness
Not necessarily coding, but understanding how Java APIs are commonly built (Spring Boot, controllers, services, dependency injection, config).
Authentication & authorization (OAuth2/JWT)
Know common security flows, token concepts, scopes/roles, and how APIs enforce access control.
API testing tools & techniques
Use Postman/Insomnia, understand test cases for endpoints, contract testing basics, mock servers, and interpreting logs/errors.
Non-functional requirements for APIs
Performance (latency/throughput), scalability, reliability, observability (logging/metrics/tracing), rate limiting, and SLAs/SLOs.
Versioning & lifecycle management
API versioning strategies, backward compatibility, deprecation policies, and change management across consumers.
Job title: Technical Business Analyst
Location: Plano, TX
Mode of work: Hybrid, 2-3 days per week
Duration: 10 months
Skills Required:
API fundamentals (REST/HTTP)
Understand REST principles, HTTP methods (GET/POST/PUT/DELETE), status codes, headers, caching, idempotency.
API specification & documentation (OpenAPI/Swagger)
Ability to read and help author API contracts (OpenAPI), define endpoints, request/response schemas, examples, and error models.
Data modeling & JSON/XML proficiency
Strong grasp of JSON structures, schema design, serialization concepts, and when XML may be relevant.
SQL and database concepts
Write and interpret SQL queries, understand joins, indexes, transactions, normalization, and how APIs interact with persistence layers.
Integration concepts & patterns
Familiarity with synchronous vs asynchronous integration, webhooks, messaging basics (e.g., Kafka/RabbitMQ concepts), and common integration pitfalls.
Java & Spring ecosystem awareness
Not necessarily coding, but understanding how Java APIs are commonly built (Spring Boot, controllers, services, dependency injection, config).
Authentication & authorization (OAuth2/JWT)
Know common security flows, token concepts, scopes/roles, and how APIs enforce access control.
API testing tools & techniques
Use Postman/Insomnia, understand test cases for endpoints, contract testing basics, mock servers, and interpreting logs/errors.
Non-functional requirements for APIs
Performance (latency/throughput), scalability, reliability, observability (logging/metrics/tracing), rate limiting, and SLAs/SLOs.
Versioning & lifecycle management
API versioning strategies, backward compatibility, deprecation policies, and change management across consumers.
