Team
Different disciplines, one product team
HexFa brings together product leadership, software engineering, development, architecture, data and operations. Eleven people, working on one set of products rather than on eleven separate briefs.
- Leadership
- Company direction and technical direction
- Engineering
- Architecture, mobile, web and delivery
- Data
- Analysis and data driven product work
How we are organised
One team, not a row of specialists
Everybody here works across part of the product family rather than on one product in isolation. A decision taken in the mobile app is taken in front of the person who maintains the web side of it, which is why a change in one product tends to arrive in the others.
It also means the person who hears about a fault is usually the person who can fix it. That is the shortest version of support anybody can offer, and it is the main reason the team is arranged this way.
The team
Everybody, and what they do
Everybody, listed with the job each of them holds. The line under a role says what that job is and nothing more than that.
-
Amir Dehdarian
CTO
Technical direction and product engineering leadership.
-
Alireza Ghahraman
CEO
Company direction, product priorities and business leadership.
-
Hamed Maleki
Tech Lead
Leads implementation work and day to day engineering coordination.
-
Fatemeh Alavi
Mobile Team Lead
Leads mobile product development and mobile delivery.
-
Sajad Maleki
Senior Developer
Builds and maintains product features.
-
Fatemeh Sadeghi
Senior Developer
Builds and maintains product features.
-
Fatemeh Seyedsafar
Senior Developer
Builds and maintains product features.
-
Amin Javan
Software Architect
Shapes software structure and technical consistency.
-
Zahra Sabourian
Data Scientist
Works with data analysis and data driven product work.
-
Zahra Hosseini
Data Specialist
Works with product data and how it is prepared.
-
Samira Irandoost
Data Assistant
Supports the data work across the products.
Every picture here is an illustration drawn for this site rather than a photograph. Personal email addresses and profile links are not published, because none has been supplied and we would rather show none than show one we made up. The address in the closing section reaches the whole team.
How the team works
Three kinds of work, and the same people
- Design We work out what the screen has to do before anything is built.
- Build The people who designed it write it, so nothing is handed over half explained.
- Keep it working The same people stay with a product once it is in use, and fix what use finds.
Why it is arranged this way
The person who built it answers for it
A product that is designed by one group, written by another and maintained by a third loses something at every handover. We keep the three together, so the reasoning behind a decision is still in the room when that decision turns out to be wrong.
It also means the person who hears about a fault is the person who can fix it, which is the shortest version of support anyone can offer.
Shared ground
What the whole team works across
- Voice and video PTTHex and RoomHex, from a push to talk channel to a full shared room.
- Operations ManageHex, from the floor plan of a venue to the orders coming off it.
- AI under an organisation's control SayHex, where the organisation decides who may use what.
- Phones and the web Android, iOS and the browser, tested on all three rather than on the convenient one.