Whippy

Introduction

Hello — I have been a programmer for the past 10 years in Node.js, Elixir, and Ruby, with an appetite to learn and try new things; I mostly learned through R&D. I love to contribute to open source and tend to dive into strange, complicated problems. I still have plenty to learn, but I ship answers in production.

About the company

Whippy builds conversational engagement tooling and ATS integrations for staffing teams. The integration surface spans onboarding, credential validation, sync orchestration, role/access controls, reporting migration, and operational alerting.

My role

I own ATS integration onboarding/sync and reporting migration work across TempWorks (primary), with reusable patterns for Avionte and Aqore.

• Built self-serve onboarding flows for staffing integrations (notably TempWorks, with Avionte/Aqore patterns): stepped forms, validation, config-to-auth/settings transforms, and connection-test APIs so customers can verify credentials before go-live.
• Implemented onboarding completion that persists typed integration settings, triggers full-sync orchestration, and exposes step/status APIs consumed by the product (including dashboard-v2 proxy patterns).
• Shipped per-integration custom object controls (toggles, settings embeds, enqueue paths) so background sync runs only for customer-selected entity types across TempWorks/Avionte/Aqore.
• Extended TempWorks sync coverage with interest codes, richer contact profile fields (communication + birthday-related data), and call/communication modelling with configurable outbound activity labeling.
• Delivered last-message activity sync from TempWorks into Whippy with scheduled pulls, range-based jobs, and before-activity jobs to power recruiter engagement signals in-product.
• Added onboarding-level data retention and archiving policy configuration (custom data archiving policies) across multiple ATS integrations, aligned with sync and dashboard behaviour.
• Introduced custom roles and invite-time role assignment (schema, APIs, registration/acceptance paths) so orgs can provision access before first login.
• Shipped assign-roles APIs with OpenAPI coverage and expanded audit logging for role-change actions.
• Led migration of usage and campaign reporting from legacy message records to a unified messages model across reports and background workers.
• Built cross-system reporting comparison and billing-oriented usage comparison (automated runs, Slack delivery, S3 artifacts) to validate and operationalise the new reporting path.
• Wired operational notifications (Slack) for integration sync-failure workflows across TempWorks, Avionte, and Crelate so teams get fast signal when integrations break.
• Built the core domain for Whippy’s Forms Builder, including the lifecycle for form creation, updates, versioning, and publishing behavior.
• Shipped public-facing Forms APIs (public listing and public show) to support externally accessible form discovery and rendering.
• Designed and delivered form response capabilities end-to-end, including submission processing, response retrieval APIs, and response filtering workflows.
• Implemented form-response-to-conversation integration by turning submissions into inbound messages, enabling response activity to flow directly into customer communication timelines.
• Added form submission notification workflows with formatted email/SMS response outputs, including richer rendering for rating/star and signature-type fields.
• Built cross-organization form reuse by implementing copy/clone capabilities for forms across organizations.
• Delivered form URL/link management features (environment/domain-aware URL resolution and stable ID-based URL strategy) to improve portability and consistency of form links.
• Added campaign/contact-aware filtering for form responses, improving reporting and operational workflows for teams using forms at scale.
• Introduced protective controls for form attachment upload paths (rate-limiting and validation flow hardening) to support safer high-volume usage.
• Expanded Forms API quality and adoption readiness through strong docs/typespec coverage and public API alignment for downstream consumers.

Technologies