Groups
Within each function, people are organised into groups — smaller clusters of people working in related areas. For example, within Engineering you might be in the backend group, the Flutter group, the frontend group, or the DevOps group.
Your group is your professional home at Arillus. It is entirely separate from the project team you’re assigned to at any given time.
What a Group Is For
Section titled “What a Group Is For”- Growing in your field — deepening your expertise in a specific area, not just doing whatever the current project demands
- Staying current — discussing trends, tools, new approaches, and what’s happening in your domain
- Learning from peers — sharing what you’ve picked up on projects, reviewing each other’s work, solving problems together
- Career development — your Group Lead owns your career growth at Arillus
Group Lead
Section titled “Group Lead”Every group has a Group Lead. In the Career Philosophy, the Group Lead represents the People Leverage path — they’ve chosen to create impact by growing the people around them rather than purely through their own individual output.
A Group Lead is not a people manager in the traditional sense. They are still an active practitioner in their function — still coding, still contributing technically, still growing in their craft. The difference is that they’ve added a second lever: the people in their group.
What the Group Lead is responsible for:
- Your appraisals — running your performance reviews, collecting feedback from your project teams, and calibrating it against your level expectations
- Your growth plan — working with you on what you’re developing, what you need to get to the next level, and how to get there
- Your day-to-day growth support — the person you go to with career questions, skill gaps, or anything that isn’t project-specific
- Keeping the group sharp — facilitating group discussions, organising knowledge-sharing sessions, making sure the group stays current
Important: a Group Lead may not be the most technically experienced person in the group — and that’s expected and fine. Their strength is knowing how to grow people and own their careers. On technical depth questions, they will often turn to the most technically strong member of the group. It is entirely normal for a Group Lead to consult a newer but highly skilled member during technical discussions or appraisals.
What a Group Is Not
Section titled “What a Group Is Not”Your group is not your project team. The people you work with day-to-day on a project are assembled for that project and will change. Your group is stable — it’s the consistent thread through your time at Arillus, regardless of which projects you move through.
Group discussions and sessions are not project standups. They’re about your field, not your sprint.
A group is also not a club where you optionally meet and talk about whatever is happening in the industry. That framing makes it feel like a side-hustle — something you can dip into when you feel like it and skip when you’re busy. It isn’t. The group is a professional structure with real ownership, real accountability, and a direct line to how you grow and how you’re assessed at Arillus.
