We are looking for a **Technical Business Analyst** who lives at the intersection of business strategy and software engineering. You won’t just be "taking notes"—you will be the primary translator between business stakeholders and our development team.
The ideal candidate can dive deep into technical specifications, query a database to validate a hypothesis, and then pivot to explain a complex system architecture to a non\-technical executive without using a single drop of jargon.
*Key Responsibilities**
**Requirements Engineering:** Elicit, analyze, and document detailed business and technical requirements. Transform vague "wants" into crisp, actionable **User Stories** and **Functional Requirement Documents (FRDs)**.
**Technical Bridging:** Work closely with Architects and Developers to ensure technical designs align with business goals. You should be comfortable discussing **APIs, data models, and system integrations**.
**Data Analysis:** Use **SQL** to perform data mapping, migration analysis, and gap analysis. You should be able to look at a schema and understand how data flows through the lifecycle of a feature.
**Process Modeling:** Create detailed process maps, sequence diagrams, and workflow visualizations to identify bottlenecks and optimize system logic.
**Backlog Management:** Partner with Product Owners to groom the backlog, ensuring that technical debt and functional enhancements are prioritized effectively.
**UAT \& Validation:** Define acceptance criteria and support the QA team in functional testing to ensure the delivered solution meets the "Definition of Done."
**Required Skills \& Qualifications**
**Experience:** 3–5\+ years of experience as a Business Analyst, System Analyst, or in a similar technical role within an **Agile/Scrum** environment.
**Technical Fluency:** \* Strong proficiency in **SQL** (joins, subqueries, and data profiling).
Solid understanding of **RESTful APIs**, JSON, and XML.
*Preferred "Bonus" SkillsWhat Success Looks Like in This Role**1\. **Clarity:** Developers rarely have to ask "What does this mean?" when looking at your tickets.2\. **Accuracy:** Features are launched with minimal "re\-work" because the edge cases were caught during the requirements phase.3\. **Trust:** You become the "go\-to" person for both the business and dev teams when someone needs to know how a specific feature actually works under the hood.
Experience with **Cloud Infrastructure** (AWS, Azure, or GCP).
Knowledge of **Python** or other scripting languages for data manipulation.
Industry\-specific certifications (e.g., **CBAP, CCBA, or CSPO**).
Prior experience in \[Insert Industry, e.g., Fintech, Healthcare, SaaS].