Front-end engineer (Schhuty Division)

Application deadline date has been passed for this Job.
Full-Time Employee
  • Post Date: 2019-08-22
  • Career Level Staff
  • Offerd Salary ¥6 - ¥8 Million
  • Experience 2 Years
  • Number of employee 1 Person
  • Gender Required Both
  • INDUSTRY Internet & Gaming
  • Qualification Associate Degree
  • Working Hour 10 to 19
  • Trial Period 3 months
  • Department Assign Shufty Division
Job Description

Work Flow 

・ Do you decide what you want to make? A planning meeting will be held at the start of the iteration, and together with participants from all occupations, including engineers, we will decide what to make by discussing the issues to tackle. In addition to the iterations, we participate in designer-driven design and user interviews, and based on these discussions, we extract the issues and incorporate measures for their improvement into the schedule. 

・ Estimation and schedule management Estimates of story points are made with engineers and project owners as participants, and the scope of iteration is determined. Task allocation is basically done without checking the status of the engineer leader or the member, or consulting with the leader that he / she has determined that the member’s priority is high. The schedule is being checked by the entire team, centered on the project owner, so that the overall plan and progress of the project can be seen. Larger schedules (milestones, etc.) are gathered by members such as business unit managers, project owners, and development team leaders, and are checked and adjusted on a monthly / quarterly basis. 

・ Development Flow Periodic development is carried out in accordance with the Agile Development Process, with 1 iteration taken as 2 weeks for estimation, planning, development, release, and retrospection. At the end of the iteration, we conduct a large-scale meeting with the head of the business unit as the leader and conduct a retrospective review of all team members. The direction of the entire project is mainly based on sharing such as “whether it was a change like the project” or a retrospective such as “there was no point where you felt any improvement in the work of iteration” This is useful for reviewing and understanding the work within the team. 

Engineers are reviewing each other based on GitHub’s Pull Request. Basically, it is possible to merge from one person with OK, and it is automated so that it will not be merged unless the specification / operation check and automatic test are passed. The design review basically has the discretion of each person in charge and is secured by the source code review. For example, it is necessary to have a knowledgeable person’s review of important functions related to settlement. 

In addition, the design review will be conducted using Prott and adding a member’s comment on the job type centered on the designer. -At the same time, create a test code for performing unit / function tests when implementing the software test function, and execute it using CircleCI. Static analysis is also automated, and the complexity of the source code is quantified and shared within the team using a static analysis tool called PhpMetrics. In addition, Sider and ESLint are trying not to be born with a source code that deviates from the coding standards. In addition, Bugsnag also monitors errors. 

Manual testing is performed in two stages, with the first stage being a specification test environment with Pull Request and the second stage being a combined test environment with release timing.


・ Coding experience of HTML5 / CSS3 / JavaScript 

・ Development experience of teams including designers 


・ Development experience using client sites MVC and MVVM framework , UI design, and design interest Someone ・ Performance improvement experience on the front site 

・Interest in the growth hack ・ Web application development experience ・ Basic knowledge on object-oriented programming 

・ Those who are trying new technologies that fear failure ・ Opening of the source such as GitHub Participation in source activities

Selection process

Document selection 


<Primary interview> Time required 1.5 hours * A simple technical test is required. 

And pressurized Gate like (Shufuti Division Web Director) 

– Higa like (Shufuti Division Web Director) 

, Iwasaki (Shufuti Division Engineer) 

<final interview> over 1 hour 

, star-like (President) 

Kobayashi like ( Director recruitment and public relations Kansho officer) , tenement-like (Director Shufuti Division)