Affyn
Software Development
11-50 Employees
0.0 (Glassdoor)
Claimed
Manages Culture Code and Employee Benefits
About Affyn
A mobile play-to-earn metaverse in which earnings our users make in the virtual world can also be utilised in the real world, thus creating a closed-loop economy within the integrated ecosystem.
Affyn Culture Code
Move Fast
Top
The team shipped out 2 successful major releases in the past 3 months. While we value velocity, we do not compromise on quality. Our support teams are able to raise tickets to the engineering teams quickly and fixes are tested and pushed out expeditiously. We are pragmatic in the choice of our technologies and do not chase technologies blindly.
Learning Oriented
Top
Engineers are empowered to explore new technologies and bring it to the team for discussion. Thus, all are encouraged to stay updated on the latest in the market and share. A channel in our discord is dedicated for us to share what we read and discovered, and more technical matters are shared and brought up at the weekly standup. Engineers are also encouraged to attend conferences and tech meetups to keep abreast of latest technologies.
Product Love
Top
Our engineering teams are housed under the Product arm of Affyn. Engineers are heavily involved in the visioning and implementation phases. They identify pain points, gaps and have a large say on the Product roadmap and prioritization of features. Outside of Product, we work closely with various teams (e.g. Marketing and Operations) to automate our business processes and utilize tech to generate greater impact and results from marketing campaigns.
Great Code Quality
Top
Documentation for backend APIs are generated automatically using docgen or OpenAPI Specifications. Code documentations are hosted on Confluence for ease of sharing between engineering teams.
As our teams deal with large amount of data (i.e. billions of records), the teams often hold discussions on time and space complexity in our Sprints.
We practice secure coding and engage third parties to audit our smart contracts and perform penetration tests on our products before every release.
As our teams deal with large amount of data (i.e. billions of records), the teams often hold discussions on time and space complexity in our Sprints.
We practice secure coding and engage third parties to audit our smart contracts and perform penetration tests on our products before every release.
Leading-Edge Technologies
Top
We employ multiple tech stacks across our products (e.g. MongoDB, ExpressJS, ReactJS, NodeJS (MERN Stack) for Marketplace, Unity for Games and Solidity for Blockchain Smart Contracts) and currently have dev and production workloads on multiple clouds (AWS, Azure and GCP).
Diversity, Equity and Inclusion (DEI)
When we hire, we look at competencies and how the candidates are able to perform in the team.
We hardly spoke about DEI not because we do not practise it but is because it is our second nature in the way we hire, appraise and reward. It is already in our DNA.
To help involve everyone, we have Chill Friday during office hours. 40% of the management is made up of Women leaders.
A diversified team in Affyn, ranging from different nationalities, age group, interest and personality.
We hardly spoke about DEI not because we do not practise it but is because it is our second nature in the way we hire, appraise and reward. It is already in our DNA.
To help involve everyone, we have Chill Friday during office hours. 40% of the management is made up of Women leaders.
A diversified team in Affyn, ranging from different nationalities, age group, interest and personality.
Continuous Delivery
The team uses AWS CodePipeline and Serverless Framework to deploy our backend codes to AWS Elastic Beanstalk, AWS Lambda and API Gateway. Our frontend code repositories are tied to AWS Amplify. Any changes on a branch will trigger an automatic deployment to the respective environment. Deployments are straightforward and we apply rolling updates to our Production setups to avoid downtime.
Data-Driven
We are led by data-driven leaders with rich experiences in using data to make strategic and informed business decisions. Together with various stakeholders, the teams define use cases, critical paths and events to ensure that our data instruments capture accurate and meaningful data to aid us in understanding our users' journey and the flows around it.
Open Communication
Our leaders discuss and create a preliminary set of OKRs for the teams. The OKRs together with the rationale behind decisions are next shared with the teams and feedback are sought from all members before decisions are made. These OKRs are hosted centrally for quick and easy access.
In Product, an all-hands session is conducted every fortnight and at the company level, a townhall (a.k.a "chill out friday") is conducted on a monthly basis to introduce new initiatives, co-workers and forge stronger bonds and friendships across departments.
In Product, an all-hands session is conducted every fortnight and at the company level, a townhall (a.k.a "chill out friday") is conducted on a monthly basis to introduce new initiatives, co-workers and forge stronger bonds and friendships across departments.
Affyn Culture Code QnA
<div>Requirements are first solicited and placed into the Product Backlog in the form of user stories. Confirmations (a.k.a. acceptance criteria) are appended to each user story. Our PM and designers will next work on the wireframes and workflows and present it to the stakeholders. Once requirements are finalized, our engineers will start setting up the necessary infrastructure and development begins. Our Sprints are 2 weeks long and after each Sprint, a Sprint Review is conducted to ensure that the team is heading in the right direction. Tests are performed and before each major release, our products and codes are sent for auditing and penetration testing. When we receive the green light, we will prepare to go live.</div>
<div>Bugs are prioritized based on the criticality and urgency levels. If a bug is critical, the team will be informed to work on it. If it is not critical, the team may choose to fix it a later date or push it to the next release.</div>
<div>We set coding standards to ensure our codes are clean, readable and manageable. We ensure that our codes are well documented and often automatically generated and published centrally for easy viewing.</div>
<div>This depends on the criticality and urgency of the ticket.</div>
<div>Newcomers are paired up with a senior engineer who will ensure that the necessary software (IDEs, packages, access to GitHub, AWS etc.) and hardware are setup properly. The senior engineer will also walk through the necessary infrastructure, deployments, code solution files with the newcomer in the first few days.</div>
<div>Our engineers perform daily standup that ensures work and progress are made in a transparent manner.</div>
<div>We manage our Product Backlog on Jira. Estimations are done by our engineers and prioritization is done by the Product Owner in consultation with the engineering teams.</div>
<div>AARs are usually conducted a few hours or the next day following a release. It is a chance for us to evaluate what went right and what went wrong. We identify areas where we can improve and set out to achieve them at the next available opportunity.</div>
<div>We do not involve engineers in unnecessary meetings and ensure that they have uninterrupted hours in the weeks leading up to major releases.</div>
