Resham Acharya

1. Role Name & Department

Role: Full Stack Developer – Admin Panel, DevOps & Database

Department: Technology / Platform Engineering

---

2. Reports To

Reports To: IT Manager – Shahid Shaikh

---

3. Role Purpose (1–2 lines)

Own the Admin Panel, deployments, and database so internal teams (Ops, CX, Vendor, Finance, Marketing, CEO) can work smoothly with accurate, reliable, and up-to-date data – with safe, predictable releases.

---

4. Key Result Areas (KRAs)

KRA 1: Admin Panel Stability & Usability

Ensure the Admin Panel is fast, stable, and supports day-to-day work for Operations, CX, Vendor Team, Finance, and Marketing without frequent issues.

KRA 2: DevOps & Deployment Pipeline

Maintain CI/CD pipelines, environments, and deployment processes so releases are frequent, safe, and reversible.

KRA 3: Database Design, Integrity & Performance

Design and maintain clean database schemas (e.g., masterlead, customer, orders, vendors) with correct relationships and good performance.

KRA 4: Internal Tools Feature Delivery

Ship new Admin Panel features/reports/controls requested by business teams within agreed timelines.

KRA 5: Monitoring, Access & Security

Set up proper monitoring, logging, and access controls for Admin & DB to keep data secure and traceable.

---

5. KPIs (5–8 measurable numbers)

1. Admin Panel Uptime

   • Availability % during working hours for the internal teams.

   • Target aligned with platform uptime (e.g., ≥ 99.5%).

2. Deployment Success Rate

   • % of deployments without rollback or major post-release issue.

   • Target: ≥ 95%.

3. Change Lead Time – Admin Features

   • Average time from approved request (by Shahid/CEO/Ops head) → live in Admin for small/medium features.

4. DB Incident Rate

   • of incidents caused by schema changes, migrations, or wrong queries per month (aim to minimize).

5. Backup & Recovery Health

   • % of successful automated backups.

   • of restore tests done per quarter.

6. Pipeline Health (CI/CD)

   • Ratio of successful pipeline runs vs failures.

   • Average time to fix broken pipeline issues.

7. Internal User Issue Volume (Admin-related)

   • of P1/P2 Admin issues raised by Ops/CX/Finance/Marketing per month (track and reduce trend).

8. Admin Feature Delivery vs Plan

   • % of planned Admin-related tasks delivered within the month/sprint.

---

6. Core Processes Owned – SOPs

Resham is owner / co-owner for these SOPs:

1. Admin Panel Development SOP

   • How new Admin features (screens, filters, actions, reports) are requested, estimated, developed, tested, and released.

   • Includes role-based access (who can see what in Admin).

2. DevOps & CI/CD SOP

   • Pipelines for web, backend, apps (where relevant).

   • Environment strategy: dev, staging, production.

   • Release steps, approvals, canary/rollback process.

3. Database Design & Migration SOP

   • Standards for schema design (naming, relations, indexes, constraints).

   • How migrations are planned, reviewed, tested, and executed.

   • Keeping analytics needs in mind (Ashwini’s dashboards, GA4 exports, etc.).

4. Access & Permissions SOP (Admin & DB)

   • Creation/removal/change of access for new joiners/exits (with HR & Shahid).

   • Role-based Admin access for Ops, CX, Vendor Team, Accounting, Marketing, CEO.

5. Monitoring & Logging SOP

   • What metrics and logs are tracked (errors, slow queries, downtime).

   • How alerts are configured and who gets notified.

6. Internal Stakeholder Request SOP

   • How Ops, CX, Vendor, Finance, Marketing raise Admin or data-related requests (new filters, status changes, exports, KPIs).

   • How they are triaged and prioritised with Shahid.

7. Data Quality & Integrity SOP

   • Routine checks for orphaned records, inconsistent statuses, broken relations between masterlead, customer, orders, vendors, etc.

   • Basic data correction process with proper approval.

---

7. Weekly / Monthly Reporting

Weekly Reporting

To:

• IT Manager – Shahid

• Plus visibility (when relevant) to Ops Head, CX Lead, Vendor Head, Finance, CEO

Format: Short Slack / Notion update

Include:

• Admin Panel changes shipped this week

  • New features, filters, reports, status changes, tools for Ops/CX/Vendor/Finance.

• Deployments done

  • What was released (web/backend/app if pipeline involved you).

• Incidents & fixes (Admin/DB/DevOps)

  • P1/P2 issues, root cause summary, what’s fixed.

• Infra / pipeline / DB work

  • Any improvements to performance, indexes, queries, backups, monitoring.

• Next week focus

  • Top 3–5 tasks (admin features, infra tasks, DB work).

---

Monthly Reporting

To:

• Shahid

• Ibrahim (CEO)

• Heads of Ops, CX, Vendor, Finance (since they use Admin heavily)

Format: 1–2 slides / short doc section

Include:

• Admin Panel: major improvements shipped

  • New tools/reports that helped Ops/CX/Vendor/Finance.

• DevOps & Deployment Summary

  • releases, rollback incidents, pipeline stability.

• Database & Backup Health

  • Backup status, restore tests, any major schema work.

• Incident Summary (Admin/DB/Infra)

  • Count by severity, patterns, key RCAs & prevention steps.

• Next Month Roadmap

  • Planned Admin features, infra upgrades, DB improvements.