Senior System Analyst

Job Responsibilities

• Own system analysis for a Maydon Tech product, starting with one product and growing to others in the portfolio (rental, parking, property management), from the business requirement to a release-ready specification.
• Elicit, analyse and document functional and non-functional requirements together with product owners, designers, engineers and business stakeholders.
• Translate business processes and rules into clear system behaviour: use cases, user stories and testable acceptance criteria, including edge cases and error handling.
• Model the system: processes, data models, state transitions, user roles and permissions, and interactions between services.
• Design and document integrations with external systems such as government services, payment providers, banks, hardware and partner platforms.
• Write and maintain API specifications together with the Tech Lead, and keep them consistent across backend, web and mobile.
• Make sure every piece of work is ready for development before it starts: requirements are complete, technical questions are resolved and dependencies are known.
• Support developers and QA during implementation and testing, answer questions about requirements, and check the result against the specification.
• Maintain accurate system documentation and the product knowledge base, so they describe how the system actually works.
• Set and improve system analysis standards, templates and practices across Maydon Tech.
• Own the analysis part of the product development process: the Definition of Ready, how requirements are handed to design, engineering and QA, and the specification templates.
• Help the Head of Product improve the rest of the product development process by describing how it works today, finding bottlenecks and proposing changes.
• Review other analysts' work and mentor junior and middle analysts.
• Identify risks, gaps and inconsistencies in requirements and solutions early, and raise them before development starts.
• Take part in discovery, backlog refinement, planning, system design sessions and release readiness.

Education

• A bachelor's or master's degree in Computer Science, Information Systems, Applied Mathematics, Engineering or a related field is a plus but not required.
• Equivalent hands-on experience and a portfolio of real specifications are valued more than formal education.
• Courses or certifications in system or business analysis (for example IIBA, BABOK-based programmes, or a recognised system analysis school) are a plus.

Work Experience

• 5+ years in system analysis in product or technology companies, with at least 2 years at senior level.
• Proven experience specifying integration-heavy systems: payments, banking, government services, marketplaces or B2B SaaS.
• Hands-on experience writing API specifications that developers built from without rework.
• Experience specifying products with several user roles and complex state (for example applications, contracts, bookings, payments).
• Experience working inside an Agile product team with designers, developers and QA, on both web and mobile products.
• Experience setting up analysis standards or a documentation process in a team that had none, or improving a weak one.
• Experience improving how requirements move through a product team (Definition of Ready, handoffs to development and QA) is a plus.
• Experience mentoring or reviewing the work of other analysts is a strong advantage.

Hard Skills

• Requirements engineering: user stories, use cases, acceptance criteria (including Given/When/Then), non-functional requirements and edge-case analysis.
• Modelling: UML (sequence, activity, state and class diagrams), BPMN 2.0 and ER diagrams.
• Process mapping: describing as-is and to-be processes and writing clear process documentation.
• API design and documentation: REST and gRPC principles, OpenAPI/Swagger, JSON, status codes and error models, versioning, idempotency and pagination.
• Integration patterns: synchronous and asynchronous calls, webhooks, message queues and events, retries and failure handling.
• Data: relational data modelling and confident SQL in PostgreSQL to check data and answer questions without waiting for a developer.
• Testing tools: Postman or similar, to check APIs against the specification.
• Understanding of client-server architecture, microservices or modular monoliths, authentication and authorisation (OAuth 2.0, OpenID Connect, tokens).
• Working tools: ClickUp, Jira, Confluence, Notion, Figma and draw.io or Miro.

Soft Skills

• Ownership: treats the specification as a product and stays with the feature until it is in production and working as specified.
• Structured, precise writing in Russian or Uzbek, plus English good enough to read technical documentation and write specifications.
• Asks the questions others skip and says "this is not ready" before development starts, not after.
• Clear communication with both technical and non-technical people, including the C-level.
• Ability to challenge a weak requirement or a risky technical shortcut with arguments, without ego.
• Teaches and gives clear, kind, actionable feedback on other people's work.
• Works well in ambiguity and with changing priorities, and keeps the documentation honest when things change.
• Reliable self-management: raises blockers early and keeps promised dates.

Desirable Criteria

• Experience integrating Uzbek government and financial services: OneID, MyID, E-IMZO, Didox, soliq.uz, egov / cadastre, CLICK, Payme, Paynet or bank APIs.
• PropTech, rental, real estate, marketplace or FinTech domain experience.
• Experience preparing documentation for a security or certification review.
• Experience with .NET or Go backend teams, or a developer background.
• Potential to grow into a Lead System Analyst role as Maydon Tech adds analysts per product.

Candidate's assessment

• Interview 1 – Intro & Experience (Head of Product, 45 min): motivation, ownership, communication, and a walk through one real specification from the candidate's past work.
• Interview 2 – Technical Interview (Head of Product and Tech Lead, 60 min): requirements, modelling, API design, integrations and SQL, tested on short practical cases. Optional, if the interview leaves doubts: a test task of up to one working day, where the candidate specifies one realistic feature with stories, acceptance criteria, a state model and an API contract, then defends it in a 30-minute call.
• Interview 3 – Final Stage & Offer: expectations, 90-day probation goals, growth path and compensation.