More about the work
Developer knowledge MCP
Engineering context was spread across repositories, documentation and change history. Coding assistants needed a controlled way to discover related concepts and inspect the source behind them.
- Developed a custom Python and FastMCP server with domain routing, knowledge-graph traversal, source search and Git history tools for coding assistants.
- Connected prebuilt knowledge graphs to repository source files, with tool prompts for tracing integrations and following changes across engineering domains.
- Built the FastAPI OAuth authorization service and React sign-in/admin interface, including Google sign-in, access approval and revocation.
- Added regression tests for authorization, redirect validation, token revocation, transport protection and Git tooling.
Coding clients connect to an authenticated MCP resource server. Python and NetworkX load domain-specific graph snapshots; graph tools discover relationships, source tools read current repository files, and local Git tooling supplies change history. A separate FastAPI authorization service manages OAuth with PKCE and user access stored in DynamoDB.
Python · FastMCP · NetworkX · FastAPI · React · OAuth · PKCE · DynamoDB · Git
- Bearer-token validation checks current approval status and a token epoch so revoked access is rejected.
- Source-file paths are resolved within configured repository roots, and reads are paginated.
- Graph snapshots need rebuilding as repositories change; current source and Git history provide complementary evidence. The illustration is a simplified tool flow, not a live deployment diagram.
GitHub review automation
Pull-request review needs more than a model response. The service must collect complete evidence, track changing commits and distinguish a code finding from a provider or infrastructure failure.
- Developed a Python account-wide review workflow and an organization-wide event-driven runtime, with bounded diff analysis and resumable evidence collection.
- Implemented OpenAI and Anthropic provider fallback, durable job state, leases, duplicate-action protection and model-usage audit records.
- Added exact-head checks and deterministic policies for review submission and merge eligibility, with independent controls for progress, reviews and merges.
- Added regression coverage for incomplete evidence, stale jobs, provider failures, repository requirements and ambiguous GitHub responses.
Signed GitHub webhook deliveries and recovery events enter queue-backed workflows. Lambda tasks and Step Functions collect source, diff and CI evidence and run bounded review chunks. DynamoDB stores generations, leases and action identities; S3 holds artifacts. Deterministic code rechecks current GitHub state before permitted writes. The retained local runner uses LangGraph and SQLite.
Python · OpenAI · Anthropic · GitHub APIs · LangGraph · Lambda · Step Functions · SQS · DynamoDB · S3 · CloudFormation
- The organization runtime scopes work to PRs created within a rolling seven-day window; recent activity does not reset their age.
- Operational failures or incomplete evidence produce a hold. Review and merge actions have separate gates.
- Merge functionality is implemented, but the dated deployment record does not establish a live bot-initiated merge. No review-accuracy or productivity metric is claimed.
AI recruiting workflows
Recruiting workflows bring together unstructured resumes, candidate records and AI-assisted research. Those pieces need dependable boundaries between tools, background processing and the application.
- Built LLM-powered recruiting agents using OpenAI and Anthropic APIs, Claude Agent SDK and MCP, with validated tool calls, persistent run state and streamed progress.
- Added unit and integration tests and fixture-based regression checks for tool allowlists, arguments, bounded outputs and contact-data redaction.
- Migrated resume parsing and candidate scoring to Python AWS Lambda, integrating document parsing, SQS, PostgreSQL and Ashby.
The recruiting coordinator uses an in-process FIFO with database leases. A separate candidate-processing path sends SQS messages to Python Lambda workers. Shared message contracts and structured logs connect processing to stored candidate records and the ATS integration.
TypeScript · Python · OpenAI · Anthropic · Claude Agent SDK · MCP · PostgreSQL · AWS Lambda · SQS · Ashby
- Tool-contract regression checks are distinct from measured model-quality evaluations.
- The illustration groups related workflows; it does not imply that the coordinator itself is an SQS queue.
Integration management platform
Integration teams need a shared view of what is required, who is responsible and what supports completion. Templates, company-specific work and access permissions must agree across the interface and database.
- Developed React workflows and Express APIs for database-backed checklists, template versions, assignments and confirmations.
- Implemented company and task access profiles, timeline views and audit records for changes to responsibilities and completion state.
- Built resumable multipart evidence uploads with S3 checksum verification and database-backed file metadata.
- Added infrastructure and release checks covering application runtime, database migrations and deployed service health.
A React application and Clerk authentication connect to Express APIs and PostgreSQL records managed with Drizzle. Versioned definitions and company tasks drive the workflow views. Private S3 objects store uploaded evidence. CDK defines application runtime, scheduled workers and delivery resources.
React · TypeScript · Express · Clerk · PostgreSQL · Drizzle · S3 · AWS CDK · ECS / Fargate
Deployment and observability tooling
Standardized controlled Linux and Windows automation deployment, state capture and rollback checks, CI regression wiring and shared structured logging. This was related platform work across automation services, rather than a feature of one application.
Python · PowerShell · systemd · Task Scheduler · CI/CD · Structured logging
- Removed standard checklist definitions and items are deleted in the inspected implementation, with audit events recorded; universal history retention is not claimed.
- Upload checksum verification validates transfer integrity. Malware scanning is not part of the current implementation.
- This case describes source-supported implementation; deployment health and adoption figures have not been verified for this portfolio.
CRM and enrichment
Deal-sourcing applications depend on both a useful interface and consistent records across research providers, a database and a CRM. This work spans the product workflows and the data paths beneath them.
- Developed React and TypeScript deal-sourcing and CRM workflows with backend API integration, server-side filtering and inline editing.
- Consolidated and hardened Python and SQL enrichment pipelines linking Salesforce, research providers and PostgreSQL.
- Added incremental synchronization, batch upserts and processing checkpoints to the structured-data workflows.
Application APIs support filtered views and record editing. Separate enrichment jobs collect provider data and apply batch upserts, using checkpoints for incremental processing and CRM synchronization.
React · TypeScript · REST APIs · Python · SQL · PostgreSQL · Salesforce
Call-to-CRM automation
Implemented and extended webhook and queue-based call processing, calendar matching, idempotency claims and manual account or route recategorization. This is related operations automation rather than the same enrichment pipeline.
Python · Webhooks · SQS · Lambda · Salesforce · Google Calendar
Browser research integration
Built an outbound TypeScript and Playwright bridge with a validated skill registry, protected persistent browser context, run leasing, cancellation and application coordination.
TypeScript · Playwright · Browser automation · Run leases
Account scoring and deliverability
Hardened weighted account scoring, vertical-focus matching, incremental score updates and mailbox/domain monitoring, alongside provider matching and deployment support. Weighted scoring is not presented as a trained model; simulated inbox-placement values remain explicitly simulated.
Python · SQL · Salesforce · PostgreSQL · Structured logging
- The pipeline work includes consolidation and hardening of existing systems.
- The diagram is an explanatory model of the data flow, not a proprietary interface or a production topology.
Shared mailbox systems
A shared mailbox needs to reconcile application state with external email providers while supporting attachments, drafts and asynchronous work. Authentication and message state are part of the same user experience.
- Designed backend APIs and asynchronous mailbox workflows for Gmail and Microsoft Graph.
- Implemented OAuth integration, attachment and draft workflows, read-state reconciliation and duplicate-send safeguards.
Provider adapters connect authenticated accounts to background synchronization and application APIs. Reconciled message state supports the shared inbox, while draft and attachment operations use the respective provider APIs.
TypeScript · Node.js · REST APIs · OAuth · Gmail API · Microsoft Graph · Background synchronization
- Read-state reconciliation keeps provider and application views aligned.
- Duplicate-send safeguards address repeated send attempts; they are not a claim of universal exactly-once delivery.
Multi-tenant finance helpdesk
A finance team handles several companies through one application. Staff identity, company access, connected mailbox identity and ticket state need distinct boundaries, while inbox work remains fast and familiar.
- Developed company-scoped inbox and ticket interfaces, member-access workflows and backend APIs.
- Implemented Google and Microsoft OAuth mailbox connections with background synchronization and provider recovery.
- Built tenant-scoped database transactions and conversation row-level security, plus mailbox-scoped message identity and send-operation safeguards.
- Added protected reply and attachment paths, email HTML sanitization and synchronization diagnostics.
React and Clerk provide the staff interface and identity boundary. Express APIs apply company access rules and tenant-scoped PostgreSQL transactions. Gmail and Microsoft Graph adapters synchronize mailbox content through queue-backed workers. Ticket and send-operation records connect inbox work to asynchronous processing.
React · TypeScript · Express · Clerk · PostgreSQL · Drizzle · Gmail API · Microsoft Graph · OAuth · SQS
- Staff sign-in and provider mailbox authorization are separate concerns; current source includes Google and Microsoft OAuth flows.
- Tenant-scoped transactions and implemented row-level security are specific controls, not a universal security guarantee.
- Duplicate-operation protection does not prove exactly-once delivery by an external email provider.
Financial report distribution
A form-based reporting process needed a service that could accept files, retain submission state and send the right report links to configurable recipients without keeping the browser open.
- Replaced an n8n form workflow with a TypeScript upload interface and API, including multipart S3 uploads and submission history.
- Implemented DynamoDB-backed submissions, company routing, form types and editable email templates.
- Built queue-backed Lambda processing and Google sign-in with Gmail report delivery.
- Defined the service infrastructure in CDK and added upload-validation and email-formatting regression coverage.
The browser uploads multipart files to S3 through API-authorized upload sessions. The API records submissions and queues processing. A Lambda worker loads routing and templates from DynamoDB, copies files to the distribution bucket and sends report links through Gmail.
TypeScript · S3 · Lambda · SQS · DynamoDB · Google OAuth · Gmail API · AWS CDK
Meeting prep-pack automation
Ported and extended calendar-driven preparation and sending phases, CRM enrichment, browser capture, HTML pack generation and day-scoped storage. This is a separate meeting workflow that shares the need for background preparation and scheduled delivery.
Python · Google Calendar · Salesforce · Browser automation · SMTP · Task Scheduler
- The current source uses S3 distribution and Gmail delivery; older documentation describing Drive, Sheets or SES is not used here.
- Distribution objects are addressed by report links; this case does not claim that all distributed files are private.
- No throughput, delivery-time or business-impact metric is presented.
3D perception
My earlier computer-vision work explored how images can become useful spatial representations, including human pose, reconstruction and mesh generation.
- Developed computer-vision components for digital twins, mesh generation and real-time 3D human pose estimation on Windows.
- Worked on reconstruction using COLMAP and researched mobile NeRF reconstruction.
- During earlier robotics research, developed stereo-camera 3D reconstruction and point-cloud registration using ICP, connecting ROS, Unity and an industrial robot.
Across these earlier projects, image inputs were used for pose estimation or reconstruction. Geometry and point-cloud representations connected perception work to digital-twin and robotics applications.
Python · C++ · OpenCV · Open3D · COLMAP · ICP · ROS · Unity · PyTorch · ONNX
- This case study brings together earlier computer-vision and robotics contributions rather than describing one combined product.
- The animation is an Open3D tutorial demonstration of ICP registration, not a captured project result. No accuracy or frame-rate benchmark is presented.
