← Back to projects

Enterprise workflow work

Enterprise Medical Insurance Workflow App

Electron desktop workflow application with Angular and Java microservices

  • Java ·
  • Spring Boot 3 ·
  • Angular ·
  • Electron ·
  • PostgreSQL ·
  • MinIO
Summary

Quick overview

Contributed to an NDA-covered enterprise medical/insurance workflow desktop application used by insurance operations teams. The system combined an Electron shell, Angular frontend, Java/Spring Boot microservices, REST APIs, PostgreSQL, MinIO-backed document storage, and XML-based document generation.

Workflow architectureDocument generationInterview topics

Details are anonymized and summarized without exposing internal code, customer data, or proprietary implementation details.

Project snapshot

Context, responsibility, outcome, and takeaway

Context

The application supported document-heavy business processes where employees completed structured forms, moved cases through review and approval states, and generated insurance or medical-related PDF outputs such as invoices, medical forms, contracts, and case documents.

My role

I worked on Java/Spring Boot REST endpoints, PostgreSQL migrations, workflow/state transitions, Angular management pages, XML-based document generation flows, and Mockito unit tests. I also supported a junior developer through technical discussions, debugging help, project-flow explanations, and implementation guidance.

Result

The work contributed to an enterprise workflow system with structured case handling, role/permission-based processes, document generation, and operational screens, while also helping a junior developer become more confident inside the project.

Takeaway

Enterprise workflow systems need careful alignment between state transitions, permissions, document generation, frontend screens, and backend services because small changes can affect real operational processes.

Document generation

XML templates, generator service, and PDF outputs

01

Structured form data

02

XML template payload

03

Document generator service

04

Generated PDF output

Enterprise workflow shape

How desktop screens, Java services, workflow state, and document output connected

01

Electron app

02

Angular screens

03

Spring Boot APIs

04

PostgreSQL state

05

Document generator

06

PDF output

Implementation notes

Expandable details for the technical story

Application shape

The system was delivered as an Electron desktop application with an Angular frontend. The frontend communicated with backend Java/Spring Boot microservices through REST APIs, while PostgreSQL handled relational data and MinIO-backed storage supported document-related flows.

Workflow work

The application supported structured case handling, including review, approval, cancellation, and modification-request states. My work included endpoint changes, migrations, and workflow/state transition adjustments inside an existing enterprise architecture.

Collaboration and support

The project required understanding a complex existing codebase, working within an Agile delivery process, and supporting a junior developer through technical discussions, debugging help, project-flow explanations, and implementation guidance.

Technical focus

Core responsibilities and engineering details

  • Implemented and adjusted REST endpoints in Java/Spring Boot microservices
  • Wrote PostgreSQL migrations for workflow and document-related changes
  • Worked on case/workflow state transitions such as review, approval, cancellation, and modification requests
  • Built Angular management screens inside an Electron desktop application using existing internal UI components
Additional technical details 4 more points
  • Worked with XML structures and templates used by a separate document generator microservice
  • Supported document-heavy flows involving invoices, medical forms, contracts, generated PDFs, and external document viewing integrations
  • Wrote Java unit tests with Mockito and worked inside an Agile delivery process
  • Helped a junior developer understand project flow, debug issues, and reason through implementation choices
What I can explain in an interview

Concrete topics this project supports

  • Electron desktop delivery with Angular screens connected to Java/Spring Boot microservices
  • REST endpoint implementation and PostgreSQL migrations in an existing enterprise architecture
  • Workflow/state transition logic for review, approval, cancellation, and modification-request cases
  • XML-based document templating and integration with a separate document generator service
  • Document-heavy business flows involving generated PDFs, medical forms, contracts, and invoices
  • Mockito unit testing, Agile delivery, and support for a junior developer through debugging and implementation guidance