Technical Analyst

Description

Job Summary: This role serves as the bridge between business and technical teams, translating requirements into technical artifacts and ensuring mutual understanding for unambiguous implementation. Key Responsibilities: 1. Translate functional and regulatory requirements into precise technical artifacts. 2. Collaborate with architects to document design decisions. 3. Support functional validation of integration flows. **Act as the bridge between business and project technical teams, translating functional and regulatory requirements into precise technical artifacts: user stories, flow diagrams, integration specifications, and supporting documentation. The TA ensures that the development team has sufficient context to implement without ambiguity, and that the business understands the scope and technical implications of each decision.** * **Create or analyze user stories or requirement documentation.** * **Participate in refinements with the client and the working team.** * **Maintain constant communication with the client and the working team.** * **Produce high-level and low-level solution diagrams for both team and business consumption (e.g., sequence diagrams, activity diagrams, etc.). Preparation of information security documentation.** * **Develop user manuals, technical manuals, and general documentation to support requirement understanding.** * **Document third-party integration contracts: event structures, required fields, response codes, and anti-fraud business rules.** * **Collaborate with the Solution Architect to translate architectural decisions (CDC, Outbox, Circuit Breaker) into documentation understandable to business stakeholders.** * **Support functional validation of flows, verifying that integrations cover documented business scenarios (including failure cases, retries, and fail\-open/fail\-close decisions).** Required Technical Stack: * **Data formats:** **JSON, XML – reading, structural validation, and contract documentation** * **Diagramming:** **draw.io or similar – UML diagrams (sequence, activity, components)** * **Messaging:** **ActiveMQ / message queues – conceptual understanding of asynchronous flows, DLQ, and retries** * **Databases:** **SQL (read/validation queries); basic understanding of relational models** * **Patterns:** **Conceptual understanding of Event\-Driven, Circuit Breaker, idempotency, and retry** * **Security:** **Basic knowledge of TLS/mTLS, tokenization, and handling of PII/PCI data** * **Version control:** **Git – basic level (reading branches, PRs, understanding changes)** * **Desirable:** **Experience in banking or fintech projects; familiarity with CNBV regulation; basic observability concepts (logs, basic metrics)** Experience and Skills * **SQL knowledge** * **Knowledge of communication protocols** * **Experience documenting integration flows between systems (REST APIs, messaging, or similar).** * **Abstraction ability** * **Communication with team and client** * **Analytical thinking, initiative, and problem-solving ability.** * **Analytical capability, attention to detail, verbal and written communication with clients.** * **Ability to explain technical concepts simply to serve as a bridge between business and technical teams** * **Basic understanding of APIs and common HTTP status codes** * **Knowledge and experience with REST, SOAP** * **Knowledge of Material Design** * **Basic knowledge of Google Drive (Docs and Sheets)** * **Basic database knowledge** * **Understanding of JSON structure** * **Jira usage** * **Postman usage** * **Charles usage** * **Basic knowledge of design tools.** * **Understanding of JSON and XML structures; ability to review and document API contracts.**