Keith JungIntegrations Lead
Resume

Jiwon (Keith) Jung  ·  Integrations Lead, legal tech

I work in between.

Clients to data. Tools to tools. Automation to automation. Wherever an integration is needed, that’s where I come in, from the first scoping call to the system that keeps running after launch.

01 · The gap

Every system works on its own. The hard part is the space between them.

Clients keep their data in one place. Teams work in another. Automations fire into a third. Most of the value sits where those places meet, and that’s the part I own.

02 · What I connect · 1 / 3

Clients ⟷ Data

Law firms stay in the case system they already use, so the integration has to come to them. I scope requirements directly with each firm, ship the API layer, and stay with it after launch.

  • Salesforce Litify
  • Filevine
  • Monday.com
  • REST APIs
  • Client scoping
02 · What I connect · 2 / 3

Tools ⟷ Tools

Two platforms rarely agree on what a “matter” is. I reconcile the data models, own the mapping, and watch delivery so a broken sync surfaces on a dashboard instead of on a client call.

  • Webhooks & retries
  • Elasticsearch
  • SQL
  • ETL
  • HubSpot
02 · What I connect · 3 / 3

Automation ⟷ Automation

Intake that routes itself. Dashboards that refresh themselves. Alerts that reach the Account Executive before the client picks up the phone. I chain the pieces so the whole workflow runs end to end.

  • Python
  • Data pipelines
  • Executive dashboards
  • Alerting
  • A/B testing

03 · In production

730M+ records in. 137M+ out. Nobody copy-pasting.

What runs today, built from the client’s problem to a shipped system, and monitored after launch.

Integration · Live

Case management integrations

Salesforce Litify, Filevine and Monday.com each have their own idea of a case. I scope with each firm, build the API layer, reconcile the models, and monitor every delivery.

  • Salesforce Litify
  • Filevine
  • Monday.com
  • REST APIs
  • Elasticsearch
730M+records in
137M+records out
Automation · Growth

Self-service intake, A/B tested

Leads were stuck in a call queue. With Marketing, I shipped a self-service intake form and ran the test behind it, with media spend per matter held equal.

Indexed to control
Media spend100%
Rep talk time per lead50%
Cost per signed case$614
−49%cost per signed case
−50%rep talk time per lead
Monitoring · Try it

Delivery monitoring, so clients never have to ask

Elasticsearch checks on every integration, SQL-backed executive dashboards, and a live status view so Account Executives answer client questions on the spot. Client reporting went from days to same-day. Break something and watch what happens:

Client CMS
API layer
CMS write
Status view
Delivered 18,432Failed 0Status Healthy
Days → same dayclient reporting
Data · Decisions

NLP risk signals for underwriting

On mass-tort dockets (Talc, AFFF, Camp Lejeune), the evidence sat in unstructured case documents and every firm documented differently. I built Python NLP models that read the documents and turn them into cashflow and collateral health signals. The underwriting team uses them in live decisions.

  • Python
  • NLP
  • Unstructured documents
  • Risk modeling

04 · Under the hood

Built on math. Tested in the field.

A mathematics and computer science foundation, machine learning research, and eighteen months leading a squad. The spec sheet:

Integrations
REST API design, webhooks and retries, Salesforce Litify, Filevine, Monday.com, HubSpot
Data
SQL, Elasticsearch, ETL and data pipelines, executive dashboards, A/B testing
Intelligence
Python, pandas, NumPy, TensorFlow, Keras, NLP, predictive risk models
People
Customer discovery and scoping, partnering with Account Executives and Client Success, incident communication, squad leadership
Also speaks
C++, R, Google Cloud Platform
Foundation
B.S. Mathematics and Computer Science · University of Illinois Chicago

Release history

  1. 2024.10 → nowIntegrations LeadLegal technology startup

    Owns client integrations from scoping to launch and monitoring. Builds the internal tools teams use to decide: dashboards, status views, risk signals.

  2. 2024.05 → nowTeam Lead, triple-negative breast cancer MLResearch project

    Consolidated multi-source patient data without dropping conflicting rows, then fine-tuned a TensorFlow model by transfer learning. First place at the Korean Society of Laboratory Medicine Summer Symposium.

  3. 2024.01 → 2024.05Neural networks for PDE solversResearch collaboration

    Trained models on cell averages, paired with finite volume methods, to cut compute cost and step past CFL limits.

  4. 2020.09 → 2022.03Military Police Sergeant31st Infantry Division, Republic of Korea Army

    Squad Leader for eighteen months. Assigned roles by individual strength and held one standard. Team awarded “Top Team”.

  5. 2020.08 → 2020.09Software Solutions Engineer (intern)ASCENT AI

    REST API integrations and data cleaning on Google Cloud Platform, contributing to a 32% sales increase.

  6. 2020.05 → 2020.07Research Intelligence (intern)NICE Data and Research

    Converted Excel and JSON sources to SQL through an ETL process for a data-mining project that drove a 28% sales increase.

05 · Connect

Got two things that should be talking?

A client and their data. A tool and the one next to it. An automation that stops where another should start. Tell me about it.