Founding full-stack engineer
BEAT
BEAT was an internal Slack-based engagement platform that connected lightweight participation workflows to backend services and analytics used for organizational health reporting.
A lightweight internal product with operational signal value.
BEAT lived inside a familiar internal interface while still feeding into structured reporting and organizational insight. The value came from linking engagement behavior to usable data, not just collecting interactions.
Engagement and org-health signals are hard to gather if the workflow is too heavy.
The product needed to meet users where they already were, reduce participation friction, and still provide clean enough data for leadership-facing reporting.
Workflow and backend design with reporting in mind from the start.
Slack interaction flow
Worked on a product shape that made participation simple inside an already adopted internal surface.
AWS backend services
Connected front-end interactions to services and data pathways that could support analytics and reporting.
Signal design
Helped define what to capture so the system generated useful signals rather than interaction noise.
Operational usefulness
Built the workflow with organizational-health reporting in mind, not as a disconnected side project.
Low-friction participation feeding structured analytics.
- Slack as the user-facing participation layer.
- AWS backend services to process workflow events and persist signal data.
- Analytics-oriented design so engagement data could be rolled up into reporting views.
Make internal products easy to use but still structurally useful.
- Start in a familiar internal tool instead of requiring a separate destination.
- Design event capture around reporting needs from the beginning.
- Keep the workflow lightweight enough to improve participation quality.
Constraints
Internal engagement tools fail quickly if they feel like overhead, so the system had to be both lightweight and analytically useful.
Impact
Created a usable path from lightweight participation to clearer organizational-health reporting and internal visibility.
Next
I would deepen the reporting layer with more comparative analytics and trend visibility by team, period, and participation mode.