Jacob Scott Hamling
Software + analytics developer building practical systems for insurance and financial workflows.
I build internal web apps, automation, and applied modeling tools that reduce turnaround time, improve data quality, and enable better decisions. I’m especially interested in product-grade workflow design, clean data pipelines, and measurable business impact.

About
A concise view of what I build and what I optimize for.
I like projects where engineering quality directly translates into business outcomes: fewer handoffs, cleaner data, and faster decisions. My work has centered on internal workflow systems (portals, approvals, auditing), automation modernization, and applied modeling for operational support.
- Education
- University of Iowa
- Programs
- Informatics · Economics · RMI
- GPA
- 3.6/4.0
- Primary interests
- Workflow systems · Data tooling
- Gamma Iowa Sigma (Insurance & Risk Management Fraternity)
- Economic Student Association
- Tippie Tech
- Applied AI Student Organization
Skills
Grouped by category with a conservative proficiency signal based on repeated project usage.
Labels are intentionally conservative and updated as I ship work.
- Shipping internal tools with clear workflow states and auditability
- Data validation + quality improvements that reduce downstream rework
- Integrations that handle nested data and auth patterns cleanly
- Sharper UI/UX systems for internal portals
- More repeatable deployments and CI habits
- Stronger evaluation discipline for modeling MVPs
Projects
A curated mix of work and personal builds, organized for quick scanning.
- Workflow states: submit → review → comment → approve with live status visibility.
- In-browser PDF preview/approval to streamline document review and reduce tooling overhead.
- Central dashboard for request status, agent details, and audit history.
- Audited and rewrote legacy PowerShell scripts in preparation for JAMS 2022 migration.
- Removed obsolete scripts/configs to reduce system clutter and improve stability.
- Helped enable a cleaner foundation for reporting modernization.
- Analyzed historical policy records to surface key risk signals (payment history, policy age, agent activity).
- Trained an Azure ML Studio model and evaluated performance (88% accuracy reported).
- Designed to support proactive retention outreach.
- Repeatable runs with normalized CSV outputs.
- Grouping by geography/time/age bands for analysis-ready datasets.
- Designed for monthly refresh workflows and longitudinal analysis.
- Full-stack app planning with user flows and feature structure.
- Designed around lightweight social + discovery mechanics.
- Built to be iterated as a portfolio-grade product concept.
- Interactive branching story mechanics with reusable functions.
- Emphasis on readable state management and modular design.
- Good demonstration project for core Python fundamentals.
Experience
Roles with measurable impact and concrete deliverables.
- Developed an internal Policy Portal to submit, review, and approve policy change requests in real time; replaced paper/email workflows and reduced turnaround time by 80%.
- Built an integrated in-browser PDF preview + approval flow with commenting and finalization.
- Created a centralized dashboard for tracking request status, agent details, and audit history to reduce follow-up communication.
- Automated validation and data-entry workflows to improve submission quality and cut manual correction work by 40%+.
- Contributed to early migration work for 150+ legacy automation workflows (JAMS 2014 → JAMS 2022) by auditing and rewriting PowerShell scripts to improve reliability.
- Identified and deleted 300+ obsolete scripts and unused configuration files to reduce clutter and improve stability.
- Supported groundwork for transitioning reporting/document delivery to Power BI dashboards for 100+ employees.
- Supported machine learning initiatives in Azure ML Studio by developing/training a policy cancellation predictor; achieved 88% prediction accuracy and enabled early identification of at-risk policies.
- Diagnosed and resolved bugs, optimized performance, and maintained Blazor internal applications for smooth cross-department workflows.
Contact
Best channel: email. I respond quickly to project and internship outreach.
If you're reaching out about a role, project collaboration, or want to discuss my work in workflow systems and data tooling, email is the fastest path. Include a short goal and any constraints—I’ll reply with direct next steps.
When you email, the most helpful details are:
- What you’re trying to achieve (outcome)
- Constraints (deadline, data systems, stakeholders)
- Links (job post, repo, document) if relevant