Home / Roles & Responsibilities
Leadership Roles
Functional Lead
| Aspect | Details |
| Reports To | CEO, COO, CTO |
| Scope | All delivery teams |
| Key Responsibilities |
- Cross-team oversight and coordination
- Business alignment and stakeholder management
- Go/no-go decisions for releases
- Escalation point for all teams
- Resource allocation across teams
|
| Decision Authority | Release approval, escalation resolution, cross-team priorities |
Technical Lead
| Aspect | Details |
| Reports To | CTO |
| Scope | All technical decisions across teams |
| Key Responsibilities |
- Architecture decisions and technical standards
- Code quality oversight
- Cross-team technical dependencies
- Technical release approval
- RCA facilitation and process improvement
- Rollback decisions
|
| Decision Authority | Architecture, code quality, technical go/no-go, rollback |
Product Owner
| Aspect | Details |
| Reports To | CEO, COO |
| Key Responsibilities |
- Backlog management and prioritization
- Stakeholder alignment
- Acceptance criteria definition
- PRD ownership
- Sprint goal definition
- Story acceptance/rejection
|
| Decision Authority | Backlog priority, acceptance criteria, feature approval |
Development Team Roles
Scrum Master (Team Lead)
| Aspect | Details |
| Reports To | Functional Lead, Technical Lead |
| Scope | Single Scrum team |
| Key Responsibilities |
- Facilitate all Scrum ceremonies
- Remove blockers for the team
- Coach team on Agile practices
- Protect sprint from scope changes
- Report progress to Functional Lead
|
Backend Developer
| Aspect | Details |
| Key Responsibilities |
- API development
- Database design and optimization
- Third-party integrations
- Backend testing (unit, integration)
- Code reviews
|
Frontend Developer
| Aspect | Details |
| Key Responsibilities |
- UI implementation from designs
- UX integration
- Frontend testing
- Responsive design implementation
- Code reviews
|
Project Coordinator
| Aspect | Details |
| Reports To | Scrum Master (Team Lead) |
| Scope | Single Scrum team |
| Key Responsibilities |
- Sprint progress tracking and metrics
- Meeting coordination and scheduling
- Status reporting and dashboards
- Cross-team communication support
- Documentation and process maintenance
- Resource and timeline tracking
|
Quality Assurance Roles
QA Lead
| Aspect | Details |
| Reports To | Technical Lead |
| Key Responsibilities |
- QA strategy and standards
- Release sign-off (can block releases)
- Regression test suite ownership
- Bug severity classification (with Tech Lead)
- QA team management
|
| Decision Authority | Release sign-off, QA process, test coverage |
QA Engineer
| Aspect | Details |
| Key Responsibilities |
- Test case creation and execution
- Bug documentation and tracking
- Regression testing
- Exploratory testing
- Quality advocacy
|
Operations Roles
DevOps Lead
| Aspect | Details |
| Key Responsibilities |
- Infrastructure management
- CI/CD pipeline maintenance
- Monitoring and alerting setup
- Rollback procedure execution
- Environment management (staging, production)
|
| Decision Authority | Infrastructure decisions, environment configuration |
Note: Production deployment is triggered automatically when Tech Lead merges to main. DevOps maintains the infrastructure and CI/CD pipelines that enable this flow.
Support Roles
Client Success Manager (CSM)
| Aspect | Details |
| Key Responsibilities |
- Key account relationships
- First point of contact for client issues
- Raises issues to #sequifi_support Slack channel
- Incident communication to clients
- Feature adoption
|
Project Coordinator - Support (Tier 1)
| Aspect | Details |
| Key Responsibilities |
- First responder in #sequifi_support channel
- Bug logging with reproduction steps
- Initial triage and priority assessment
- Escalation to Tier 2 (Support Engineer + QA)
- On-call coordination
|
| Response Time | 15 minutes |
Support Engineer (Tier 2)
| Aspect | Details |
| Key Responsibilities |
- Hotfix development and testing (with QA)
- Root cause investigation
- Provide workarounds
- Technical analysis and documentation
|
| Response Time | 30 minutes |
Support Lead
| Aspect | Details |
| Key Responsibilities |
- Support team oversight
- Client SLA management
- P0 escalation coordination
- Process improvement
|
Design Role
UX/UI Designer
| Aspect | Details |
| Key Responsibilities |
- User research and journey mapping
- Wireframes and prototypes
- Visual design and component specs
- Design handoff to development
|
RACI Matrix - Bug Fix Process
R = Responsible | A = Accountable | C = Consulted | I = Informed
| Activity |
Tech Lead |
Developer |
QA Lead |
QA Eng |
CSM |
PC (Support) |
| Client reports issue |
- |
- |
- |
- |
R |
I |
| Post to #sequifi_support |
I |
- |
I |
- |
R |
I |
| Bug triage & logging |
I |
I |
I |
- |
- |
R |
| Bug classification |
A |
- |
C |
- |
- |
R |
| Developer assignment |
A/R |
I |
- |
- |
- |
- |
| Fix development |
C |
A/R |
- |
- |
I |
I |
| Code review |
A |
R |
- |
- |
- |
- |
| QA testing |
- |
- |
A |
R |
- |
- |
| QA sign-off |
I |
- |
A/R |
C |
I |
I |
| Production deploy |
A/R |
- |
C |
- |
I |
I |
| Post-deploy monitor |
C |
R |
C |
R |
I |
R |