Roles & Responsibilities

Roles & Responsibilities

We outline developer roles at MasterFabric: what each role does, what ownership means, and how we structure teams. We aim for clarity so you know what is expected of your role and how you contribute to the team and the product.

Developer Roles

We recognize the following developer roles. Many developers span multiple roles (e.g., full-stack, or backend + DevOps). We align expectations based on your primary focus.

Frontend Developer

• Focus — UI, UX implementation, client-side logic, and integration with backend APIs.
• Ownership — Component design, state management, performance, accessibility.
• Typical stack — React, Next.js, TypeScript, CSS/Tailwind, design systems.
• Responsibilities — Build UI that meets designs, ensure responsiveness and a11y, integrate with APIs, write tests.

Backend Developer

• Focus — APIs, databases, business logic, and server-side infrastructure.
• Ownership — API contracts, data models, security, scalability.
• Typical stack — NestJS, Node.js, Python, PostgreSQL, Redis. See Backend Stacks.
• Responsibilities — Design and implement APIs, manage data, ensure security and performance, document contracts.

Full-Stack Developer

• Focus — Both frontend and backend. Often owns features end-to-end.
• Ownership — End-to-end feature delivery, integration, and consistency across the stack.
• Responsibilities — Build features across UI and API, ensure integration quality, contribute to architecture decisions.

Mobile Developer

• Focus — iOS, Android, or cross-platform mobile apps.
• Ownership — App performance, store compliance, crash monitoring, analytics. See Mobile.
• Typical stack — React Native, Swift, Kotlin, Flutter.
• Responsibilities — Build and ship mobile apps, handle store submissions, monitor crashes and analytics.

DevOps / Platform Developer

• Focus — CI/CD, infrastructure, deployment, and platform tooling.
• Ownership — Pipelines, hosting, monitoring, developer experience.
• Responsibilities — Maintain CI/CD, manage environments, improve developer workflows. See Cloud Native.

Ownership

We expect developers to own their work:

• Scope — You own your assigned features and tasks. You drive them to completion and communicate blockers.
• Quality — You ensure your code is tested, reviewed, and documented. You fix bugs you introduce.
• Handover — When you leave a project or task, you hand over clearly. See Project Handover.

Team Structure

• Squads — We work in small squads (typically 3–6 people) focused on a product area or client project.
• Lead — Each squad has a tech lead who owns technical decisions, architecture, and alignment with other squads.
• Roles in squad — A squad usually has a mix of frontend, backend, full-stack, and sometimes mobile or DevOps.