Technical Business Analyst

About the project:

We’re building a fast-growing professional networking platform and are now entering an exciting new scaling phase — evolving from an early MVP into a robust, modern microservices-based architecture.

About the role:

We need a Strong Business Analyst who can take a vague client request (e.g., "Make an AI Matching Engine") and turn it into a concrete mathematical specification for developers. You will also wear the Project Manager hat, managing the Kanban board and ensuring the team has no blockers.


Your day to day tasks:

70% Business Analysis: Requirements elicitation, API logic definition, solution design, designer collaboration.
30% Project Management: Sprint/Kanban planning, risk management, stakeholder reporting.

 Business Analysis & Solution Design

•   Translate "Magic" into Logic: The client wants "AI." You need to define the exact weighted formula (e.g., Rank = 30 points, Visa = 20 points).
•   Data Modeling: Work with the Lead Architect to define data schemas (e.g., How do we structure a "Job Vacancy" in MongoDB so it filters correctly?).
•   Feature Specification: Write detailed User Stories and Epics. You are not just writing "As a user..."; you are defining error states, edge cases, and acceptance criteria.
•   Designer Collaboration: Brief the UX/UI designer. Ensure their beautiful designs are actually buildable within our data structure.

Project Management

• Own the Board: Manage the Jira/ClickUp board using Kanban/Scrumban. Ensure tickets move from "To Do" to "Done."
• Risk Management: Identify risks before they become fires. (e.g., "We can't build the Chat UI because the Backend API spec isn't ready").
• Rituals: Lead planning sessions and retrospectives. Keep them short and effective.
• Transparency: Provide "Brutally Honest" weekly reports to stakeholders. We value clarity over optimism.

You're perfect candidate for this role if you own these qualifications:

• 3+ years as a Business Analyst in software development (Mobile/Web).
• You can read a JSON payload. You understand the difference between SQL and NoSQL. You know what an API endpoint is.
• Proven experience running Kanban or Scrumban teams.
• You don't just document requirements; you challenge them. If a client asks for a feature that breaks the architecture, you propose a better alternative.
• English: B1 (Excellent written and good verbal communication).

Nice to have:

• Experience with Marketplace products (Two-sided markets).
• Experience documenting migration projects (Legacy -> Microservices).
• Familiarity with Figma (for reviewing designs).

Interested? Send your CV!