- Career Level Staff
- Offerd Salary ¥6 - ¥8 Million
- Experience Less than 1 Year
- Number of employee 1 Person
- Gender Required Both
- INDUSTRY Internet & Gaming
- Qualification Associate Degree
- Working Hour 10 to 19
- Trial Period 3 months
・ How to decide what to make A planning meeting is held at the start of the iteration, and together with the participants of all occupations including engineers, we decide what to make.
In addition to the iterations, we also participate in designer-sponsored design sprints and user interviews, and based on these discussions, we identify the issues, and incorporate measures to improve them into the schedule.
・ Estimation and schedule management The story points are estimated with engineers and product owners as participants, and the scope in the iteration is determined.
Allocation of tasks is basically done while the engineer leader confirms the status of the member, but if the member determines that the priority is high, he consults with the leader and may start. The schedule is checked by the entire team, mainly from the product owner, and the progress of each plan and project can be seen. Larger schedules (such as milestones) are gathered by members such as business unit managers, product 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 and estimated, planned, developed, released, and retrospectively implemented.
At the end of the iteration, a large-scale meeting was held with all job types led by the division manager, and all team members looked back. The review of the overall direction of the project, focusing on sharing such as “what changes have been made to the product” and “returning something about the iteration work”? , And help understand the work within the team.
・ Code review Engineers review each other based on GitHub Pull Request. Basically, it is possible to merge if OK is given from one person, but it is automated so that it will not be merged if it does not pass the specification / operation check and automatic test. Design review is basically done at the discretion of each person in charge and is secured by source code review. For example, critical functions related to settlement require review by a person with a wealth of knowledge.
In addition, the design review is conducted using Prott, in which the member comments regardless of the job type, with a focus on the designer.
-At the same time, create test code to perform unit / function test when implementing software test function and execute it with CircleCI. Static analysis is also automated, and the complexity of the source code is quantified using a static analysis tool called PhpMetrics. In addition, Sider and ESLint are trying not to generate source code that is out of coding standards. Manual testing is performed in two stages. The first stage is a specification test environment for each pull request, and the second stage is a combined test environment for each release timing.
Anyone with experience below
・ Experience using web languages and web frameworks
・Experience with team development
・Experience developing web applications ・
Interest / experience with growth hack
・ UI design, design Interest / Experience
・ Development experience using client side MVC and MVVM framework
・ Infrastructure construction / operation experience using cloud IaaS
・ Development flow improvement experience ・ Website performance improvement experience
・ Basic knowledge of object-oriented programming
・ Failure For those who can challenge new technologies without fear of
・ GitHub, etc.
■ Selection step Document selection:
Time required 1.5 hours
* Some technical tests may be conducted.
(Web Director, Shufty Division)
(Web Director, Shufty Division)
(Engineer, Shufuti Division)
<Final Interview> Time required: 1 hour
(Director, Shukhty Division Director)