Junior Product Owner

We are an international team of young and ambitious professionals united by a passion for innovations and belief in the decentralized world. And now, we are looking for a Junior Product Owner who will strengthen our team and contribute to the success of our products and the bright future of Web3.

Responsibilities:

Develop existing blockchain/fintech products with a strong focus on our B2B clients. This involves:

• Close interaction with founders, CTO, and direct supervisor, so there's little room for major mistakes.
• When it comes to a number of possible user scenarios, products are fairly restricted. In the beginning, there will be few B2C user interviews, funnel optimizations, etc. Main growth opportunities for the company will be found in integrations with new payment systems, optimizations in compliance/KYC/anti-fraud systems, and other areas.
• Cultivate an understanding of the needs of B2B clients and the market we operate in.

Key Skills:

• Tech savvy: we expect you to be able to grasp the main technical aspects and understand at the PRD development stage how everything will be implemented and be able to discuss this at a high level with the CTO. If something is unclear, you don't hesitate to ask colleagues.
• Understanding of the ownership concept: You're given a feature, and you're fully responsible for it. This includes:
  1) Refining requirements with the CTO/supervisor/founders to achieve the fastest possible time-to-market. We give you a specific business pain point and a proposed solution - you fine-tune it with us. If the feature is small in scope, you handle it independently, but you'll need to defend its implementation.
  2) If necessary, you do both market research and read through API documentation to get an understanding on what needs to be on the technical level.
  3) Design collaboration with colleagues from the design department.
  4) Answer product questions that arise from the technical team during feature development.
  5) Acceptance testing - after the QA team validates that there are no bugs, you'll conduct testing and validate that everything is done according to the initial vision.
  6) As needed, draft instructions for support and merchants - FAQs, how to troubleshoot if something goes wrong, etc.

Ideal Candidate Experience (one of the three options):

1. You're making a career switch from a technical role (developer or QA) to product management. Education doesn't matter - whether you have it or not, and what type.

2. You have a technical education (and you've been coding throughout your studies), you worked in the IT industry, but not in your specialization (project manager, BA, technical support, etc.).

3. You don't have a technical education or coding experience, but:

• You're keen on blockchain and web3 - and we'll verify this in real-time.
• You will learn to code in your free time - we don't expect you to become a developer, but we expect you to be able to do basic frontend/backend/DB things, as it's crucial for us that you understand the mindset of your technical colleagues and what exactly they are doing.

For the third case, we expect you to provide us with a Cover Letter describing the most interesting trends in crypto for you and the token distribution in your portfolio (why these specific tokens, how your opinion about your portfolio changed, why, and how you responded).A significant plus would be if you've completed one or all of the courses from GoPractice, Krasinsky's unit economics, or Zamesin's JBTD.

Reason for Technical Skill Requirements:

At this stage of the company's development, we follow a technology-driven approach. Clients' major needs are clearly defined, and their satisfaction is often achieved through non-trivial blockchain solutions or by expanding our offering through technical integration of new payment methods, service providers, etc. The speed and quality of decisions made by people without a technical background were found to be below our requirements due to a lack of understanding of the technical implementation.

Why We're Looking for a Junior, Not a Middle/Middle+ product owner:

• To support several current products, there will be a small team consisting of 1 backend developer, 1 frontend developer, 1 QA, and if necessary, 1 designer. In terms of maintaining existing products, this is roughly sufficient as other colleagues are occupied with different tasks.
• The level of product uncertainty is very low (what to do, why, how much money is in there, etc.) - as described above, given the limited user scenarios, there's minimal room for error. Additionally, there's guidance from colleagues.

In conclusion, there's little room for imagination (we're not building spaceships, we're making money) due to limited resources under your control, yet you have a definite business impact. The more money we make and the more confidence we feel in you, the more responsibility and resources we will provide you with.

Your KPIs for 1-3-6 months:

1 Month: Familiarization

• Immersion into your product domain.
• Building connections with team members.
• You're handed a backlog of simple yet necessary features.
• You deliver at least 1 feature to production.
  You begin work on the concept of 1 complex feature.

3 Months: First Tangible Business Impact - this determines whether your probationary period was successful or not.

• You have fewer blind spots regarding the products.
• There's tangible delivery from you with a clear business impact for the company - the first major feature.
  You engage in iterative improvement of products, progressively releasing essential minor features for internal users (support, compliance, etc.) and external users (B2B merchants, B2C customers, etc.).

6 Months: Comfort Zone

• You have more deliverables with a clear business impact for the company.
• Thanks to your improvements, we can see changes in revenue or product metrics when comparing figures from the time of your hiring to now.
• You feel comfortable within your area of responsibility.
• We feel comfortable knowing you have the products under control and have a clear roadmap.

Test case

• There is one, and it's mandatory.