Вакансии MAYDON TECH: работа в IT и digital
Вакансии компании MAYDON TECH в IT и digital за последние 30 дней. Направления найма, города и форматы работы. Дубли объединены. HireSeeker — независимый агрегатор вакансий.
Найдено: 4. Обновлено .
Города с вакансиями
- Ташкент4
Страны с вакансиями
- Узбекистан4
Форматы работы
- Офис4
Job Responsibilities
Own end-to-end delivery across Maydon Tech products, so that work ships on time, with agreed quality, and with stakeholders aligned across product, design, analysis, engineering and QA.
Run a single intake for all requests: collect, clarify and queue them, and make sure nothing reaches the team outside the agreed process.
Run the delivery cadence: sprint planning, backlog refinement, daily syncs, reviews and retrospectives, in a Scrum or Scrumban setup that fits the team.
Own release management: the release calendar, release readiness with QA, release notes, and coordination of deployments and rollbacks.
Track progress, dependencies and risks across products and teams, and remove blockers before they delay delivery.
Prepare a short weekly delivery report for the Head of Product and the C-level: what shipped, what is in progress, risks and decisions needed.
Create, monitor and report delivery metrics such as cycle time, throughput, predictability and unplanned work.
Keep tasks, boards and documentation in ClickUp accurate, so anyone can see the real status of the work.
Coordinate with external vendors and contractors on scope, timelines and follow-up.
Coordinate with Customer Operations (support and moderation) on incidents and escalations to the product team.
Continuously improve the delivery process together with the Head of Product: workflows, Definition of Done, handoffs and team rituals.
Support product launches with launch checklists, internal testing coordination and go-to-market readiness.
Education
Bachelor’s or Master’s degree in Engineering, Computer Science, Business, or related field is a plus but not required.
Equivalent hands-on experience and a track record of delivery in tech or product teams is equally valued.
Project management certifications (PMP, Scrum Master, Kanban, Agile PM) are a plus but not mandatory.
Work Experience
2–4 years of experience in project or delivery management in tech or product companies.
Hands-on experience running Scrum, Kanban or Scrumban in a development team.
Proven track record of delivering web and mobile products with cross-functional teams of 8–20 people.
Experience owning releases end to end, including coordination with QA and DevOps.
Experience working in startups or fast-paced environments with changing priorities.
Experience managing several products or projects at the same time is a plus.
Experience leading a small team (for example support or operations) is a plus.
Hard Skills
Agile delivery: Scrum, Kanban and Scrumban, and choosing what fits the team.
Sprint planning, backlog refinement, capacity planning and delivery tracking.
Release management: release planning, readiness checklists, release notes, rollback plans.
Strong proficiency with PM tools, ClickUp preferred (Jira, Notion, Asana are also fine).
Delivery metrics: cycle time, throughput, velocity, burndown, predictability.
Risk and dependency management, documentation and meeting facilitation.
Understanding of the SDLC, Git workflows, QA and testing cycles, environments and CI/CD.
Soft Skills
Leadership through influence: earns the team's respect through clarity, accountability and fairness.
Clear communicator with technical and non-technical people, including the C-level.
Ownership mindset: treats delivery results as their own, not only the process.
Holds the line on agreed rules and priorities, politely and consistently, with everyone.
High emotional intelligence: understands team dynamics, motivation and conflict resolution.
Structured, proactive and solution-oriented.
Comfortable with ambiguity and fast-changing priorities.
Desirable Criteria
Experience in PropTech, FinTech, marketplaces or SaaS products.
Experience with products that integrate government services or payment providers.
Experience setting up a delivery process in a team that had none.
Worked closely with founders or C-levels in startup or scale-up stages.
Fluent Uzbek and Russian, and working English.
Candidate’s assessment
Interview 1 – Experience & Culture Fit (Head of Product, 45 min): delivery experience, communication, ownership, and how the candidate handles pressure, conflict and changing priorities.
Interview 2 – Delivery Case (Head of Product and Tech Lead, 60 min): Agile practice, planning, releases and metrics. Includes a case where the candidate plans the delivery of a feature across backend, web and mobile, flags risks and dependencies, and suggests process improvements.
Interview 3 – Final Stage & Offer: expectations, 90-day probation goals, growth path and compensation.
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.
Job Responsibilities
- Functional testing of web and mobile products
- Regression testing before releases
- Exploratory testing of complex scenarios
- UI/UX consistency testing (design vs implementation)
- API testing and validation (Postman / Swagger)
- QA documentation system: Test Cases, Checklists, Bug Reporting Standards, Test Plans (for complex modules), Edge Cases Matrix
- Participate in product lifecycle: Grooming, Planning, Release readiness
- Cross-functional collaboration: Product Team, Design Team, Engineering Team
- Automation (growth track): Basic understanding of automation, API tests / E2E tests (Playwright / Cypress)
Education
- Bachelor’s or Master’s degree in Computer Science, Engineering, or related field (preferred)
- Equivalent hands-on experience is equally valued
- QA certifications are a plus but not required
Work Experience
- 1–3+ years as a Manual QA Engineer
- Experience working in a product/data-driven team (not only outsourcing)
- Experience testing complex systems (multi-role, state-based logic)
- Experience participating in or improving QA processes
Hard Skills
- Strong Manual Testing skills
- Test design techniques: Equivalence Partitioning, Boundary Value Analysis, Decision Tables, State Transition Testing
- API Testing: Postman / Swagger
- Bug tracking: Jira
- Understanding of: Client-server architecture, REST APIs, Basic SQL
- QA documentation: Writing test cases, Creating checklists, Structuring bug reports
- Basic knowledge of automation: Selenium / Cypress / Playwright (at least conceptual level)
- Understanding of: SDLC / STLC, Agile workflows
- Debugging tools: Chrome Dev tools, Charles Proxy, Httptoolkit
Soft Skills
- Strong system thinking
- High attention to detail
- Ability to ask the right questions
- Clear and structured communication
- Ability to challenge decisions constructively
- Proactive mindset (does not wait for tasks)
- Ability to work in ambiguity (important for current stage)
- Ownership and responsibility
Desirable Criteria
- Experience working in QA processes
- Experience working in startups or fast-growing teams
- Experience with complex domain logic (roles, contracts, workflows)
- Hands-on experience in test automation
- Experience with CI/CD pipelines
- Understanding of UX principles
- Experience working closely with Product & Design
Candidate’s assessment
Interview 1 – QA Fundamentals & Process Thinking:
Manual testing depth, understanding of QA lifecycle (SDLC/STLC), ability to design test cases and checklists, and thinking in terms of edge cases, states, and system behavior.
Interview 2 – Technical & Process Interview:
API testing (Postman/Swagger), test design techniques, understanding of system architecture, and ability to design QA processes, integrate QA into product lifecycle, and define regression and release validation strategy. May include a case task where the candidate creates a checklist, writes 5–10 test cases, identifies bugs in a given flow, and provides structured bug reports demonstrating clarity, depth, and attention to detail.
-
Design, build and maintain backend services in Go: clean, idiomatic, readable code
-
Design gRPC and REST APIs, keep their contracts stable, and version them when they change
-
Write efficient PostgreSQL queries, design schemas, and write safe, reversible migrations
-
Use goroutines, channels and context correctly: no leaks, proper timeouts and cancellation
-
Handle errors explicitly, with retries and idempotency where calls can repeat
-
Write unit and integration tests for business logic and failure cases
-
Add structured logging, metrics and health checks so problems can be seen and diagnosed
-
Keep the services secure: validate input, authenticate callers, keep secrets out of code and logs
-
Profile and optimize CPU, memory and database load when needed
-
Write short technical docs for the APIs and services you own
-
Review teammates' pull requests and keep the code consistent
Education:
- Bachelor’s or Master’s degree in Engineering, Computer Science, Business, or related field is a plus but not required
Work Experience:
-
1–3 years of commercial backend development in Go
-
Built or maintained at least one production service in Go (REST or gRPC)
-
Worked with PostgreSQL: queries, indexes, migrations
-
Used Docker. Basic Kubernetes is a plus, not required.
-
Integrated a third-party API (payments or webhooks is a plus)
-
Used Git and pull requests in a team
Required Hard Skills:
-
Go: goroutines, channels, context, error handling, standard library
-
REST API design, plus a working knowledge of gRPC and Protobuf
-
PostgreSQL: SQL queries, joins, indexes, transactions, migrations
-
Docker: writing a Dockerfile and running services locally
-
Git: branches, pull requests, resolving conflicts
-
Testing: unit tests in Go (testing package, table-driven tests)
-
HTTP basics: status codes, JSON, authentication (JWT)
-
Linux basics: terminal, reading logs
Nice To Have Hard Skills:
-
Kubernetes basics (pods, deployments, logs via kubectl)
-
Integrating payment providers (Click, Payme, Uzum) or webhooks
-
Message queues (RabbitMQ, Kafka, NATS)
-
Redis
-
CI/CD with GitHub Actions
-
Prometheus or Grafana
-
Experience with Helm, ArgoCD or other GitOps tools.
-
Experience with HashiCorp Vault or another secrets manager.
-
Experience with parking, access control, IoT or hardware integrations (barriers, cameras, ANPR).
-
Experience with payment providers and fiscal requirements.
-
Experience with networking: tunnels, VPNs (IPsec), load balancers.
-
Some C#/.NET
Soft Skills
- Takes responsibility for results, not just closing tasks
- Asks for help early instead of staying stuck
- Communicates clearly about progress and blockers
- Accepts code review feedback calmly
- Learns new tools quickly
- Pays attention to detail, especially in payment logic
- Works well in a small team
Desirable Criteria
- Experience with Kubernetes (basic: pods, deployments, kubectl logs)
- Experience integrating payment systems (Click, Payme, Uzum) or webhooks
- Experience with message queues (RabbitMQ, Kafka or NATS)
- Experience with Redis
- Experience with CI/CD (GitHub Actions)
- Familiarity with Helm, ArgoCD or Vault
- Experience with monitoring (Prometheus, Grafana)
- Experience with IoT or hardware integration (barriers, cameras, number-plate recognition)
- Basic knowledge of C#/.NET
- Technical English (reading documentation)
Candidate’s assessment
1. CV review: we review your CV and GitHub (if you have one) within 3 working days.
2. Short call (20–30 min): we talk about your experience and the role.
3. Technical interview (60 - 120 min): Go basics, concurrency, PostgreSQL, REST/gRPC, plus a short live coding task
4. Final interview (30 min): a meeting with the team lead about how you work, plus our offer
Вакансии по профессиям
Как составлена подборка
Показываем активные предложения IT и digital, опубликованные за последние 30 дней. Дубли объединяем. Условия и наличие вакансии могут измениться после обновления: проверяйте их перед откликом.