★QA Engineer | Japan's Only Product

• Business Level Japanese Required

★Hybrid Work & Flextime

★Start-up Company

★New Business

★In-house Products

◆ Annual Salary: 6 million ~ 10 million yen.

【About the company】

The company provides a service that allows anyone to easily create demo content by cloning and customizing software with no-code. The service communicates the true value of a product immediately, delivering its original value to customers without needing a production environment. The platform also enables per-content access analysis.

The company helps clients realize "customer communication through product demos" in a variety of scenarios, such as maximizing lead generation, standardizing sales demo skills, streamlining the order process, and creating templates for customer success onboarding.

In the future, the company plans to comprehensively cover all processes related to software sales and utilization in the AI era. By digitizing this process, they aim to create a world where "the concepts of selling and using software no longer exist, and everyone can simply enjoy the value of technology."

【 Job Description】

1. The World the Company Aims to Create

The company is tackling the fundamental problem inherent in software: "The value that should be communicated is not being communicated."

No matter how excellent a product is, if its value—"what it is good for" and "why I need it"—is not properly delivered, that value remains undiscovered.

Even with the evolution of AI, this unfortunate "waste" will not solve itself naturally. In fact, as general-purpose technologies like LLMs spread, the relationship between products and users becomes even more complex, and "how it is communicated" becomes increasingly important.

The company's mission is to design an experience that is "communicated" rather than merely "told."

Starting from the Intent, they want to construct the experience itself, creating a world where users can naturally "understand, utilize, and feel the value" of the product.

As a result, they are seriously aiming for a future where:

・The true value of SaaS and AI products reaches users worldwide.

・Companies and customers connect without misunderstanding, achieving results for both parties.

・New products penetrate society faster and more broadly.

1. Expected Role of the Position

The company provides a demo platform. If customers are unable to play or edit a demo, it could significantly impact sales and key performance indicators (KPIs).

In other words, the service's quality is highly susceptible to both positive and negative perceptions. For a service that demands such high quality, simply testing before release is insufficient. Quality must be prioritized in every phase.

QA Involvement Across All Phases

The QA engineer is expected to consider the following throughout the development process:

・Planning Phase: Will the design impact other features at the planning stage?

・Code Testing: Testing against the code.

・Risk Analysis: Analyzing defects to determine where risks lie.

In this manner, the engineer will be expected to identify quality risks from a QA perspective in every single phase. They will work together with the team to devise mechanisms to prevent defects from leaking into the production environment.

1. Responsibilities

・Requirements definition and specification formulation for new features from a quality perspective.

・Test design and execution.

・Maintenance of the automated testing environment.

・Data collection and analysis for quality tracking.

1. Development Environment

Composition

Customer-facing web app (SPA)

Operations-facing web app (MPA)

Chrome extension

Backend: Kotlin (Ktor), PostgreSQL, Redis

Frontend: TypeScript, React, Chakra UI

Chrome extension: TypeScript, React

Infrastructure: Google Cloud (primarily Cloud Run)

Other: Shifting to a development framework utilizing generative AI like Claude

1. Development Team Communication Cycle

The team structure includes four main types of communication forums:

・Weekly Planning: A meeting where the team discusses the development plan for the upcoming week.

・Weekly Product Meeting: A forum for sharing product-related information. It is held jointly by the business and engineering sides. Members freely share customer feedback, features planned for upcoming releases, and other topics from their respective viewpoints.

・Weekly Development Meeting: A meeting where each member brings general development topics for discussion, aiming to achieve technical improvements and smooth team communication.

・Weekly Design Meeting: A forum for discussing necessary architecture, table design, and business logic with team members when implementing new features or components.

【 Requirements】

【Required】

3+ years of combined practical experience in the following two areas:

・Practical experience in planning, analysis, design, and execution as a QA Engineer

・Design, development, implementation, and testing experience as a Development Engineer

【Preferred】

Experience in developing and testing web services

Experience in developing and maintaining automated tests

Project management

Security vulnerability assessment

【Ideal Applicants】

Communicate effectively at the right time

Communicate appropriately whether via text or in person

Consciously create documentation that is easy for others to understand

Conducts business communication in person

【Working Time 】

Flextime System

【Holidays】

Saturday/Sunday/National Holiday

Annual Paid Leave

New Year Holiday

【 Welfare 】

Full Social Insurance

Commuting Allowance

Telecommuting System