QA Engineer

About the role

We're rebuilding how quality works here, and we're being upfront about the starting point: our automated coverage is thin, testing sits more separately from development than we want, and we have almost no data about our own quality.

You'll change that. You'll build the automation framework our developers contribute to, coach them until testing is a normal part of their work, and establish how we measure quality in the first place. Unit tests already belong to the developers — our direction is for that ownership to extend further, with you building the foundation and the capability that makes it realistic.

What you'll do

• Enhance and own the test automation framework developers write in — fast, stable, and easy enough that people actually use it
• Build CI quality gates, test data, and environments so a developer can test properly without waiting on anyone
• Make quality measurable by design: define success metrics for every meaningful change, establish the baseline, track the impact, and use the data to guide decisions, validate outcomes, and drive further improvements
• Pair with and coach developers on test design — the goal is the team testing more
• Join refinement and design early, and push on requirements that can't be tested as written
• Build deep product expertise and use it to focus effort on the risks that actually matter
• Do exploratory and risk-based testing where human judgement beats a script

What we're looking for

• 6+ years in software testing, with real depth in both automation and exploratory testing
• You've enhanced or substantially rebuilt a test framework, not only written tests inside someone else's
• Strong programming ability, and comfort creating and debugging CI pipelines yourself
• Data literacy: you can define a metric, build the collection for it, and say when it's lying
• A track record of changing how other engineers work, through coaching and influence rather than authority
• Curiosity about the product and the people using it, not just the code

Our stack: TypeScript, GitHub Actions, Docker. Coming from Python, Java, C# or Go is fine — we'd rather have the engineering judgement and let you pick up the language.

Level

Open to mid and senior.

• Mid: you build the framework, pair daily, and improve your team's scope.
• Senior: you set the approach across teams, coach experienced engineers, and identify the systemic problems before anyone asks.

 

Working Conditions

Employment Status

Full-time

• Probationary period: First 3 months after joining the company. (During this period your contract conditions will be the same as that of a permanent employee.)

Work Hours and Work Place

• Working hours: flextime system (Start 7am-10am, Core time 10:00am-2:00pm, End 2pm-10pm)
• Hybrid work style of coming to the office and working remotely. Many of us come to the office about half a day a week. You can come to the office at your free time, avoiding crowded train times.
• We have no plans to go back to office commuting altogether. We will continue to do hybrid work, mainly remote work.

Holidays

• Two days off per week (as well as national holidays)
• Paid leave, congratulatory and bereavement leave, sick leave

Salary

• 12 months salary and bonuses paid in summer and winter.
• Based on skills, experience, and abilities
• Reviewed 2 times a year

 Benefits

• Various social insurance benefits included
• Work from home available
• Support programs for self-improvement and career development (language learning, etc.)
• Commuting allowance
• Lunch or Dinner support

 

Selection Process

1. Document screening
2. Solve our coding challenge
3. Interview with engineers (2 times)
4. Interview with our CEO, CTO and HR

※Please understand that replies will be delayed due to the vacations over the year-end and New Year's holidays.