Lennart B.

Quality and result oriented back-end developer

Zeewolde, Flevoland, Netherlands

About

Quality and result oriented Java back-end developer with over 12 years of experience with business applications. Eager to learn and create meaningful software for a company with a purpose. Enjoys implementing simple solutions for complex challenges.

Experience

  • Software Engineer at ANVA
    Mar 2023 - Present · 3 yrs 4 mos

  • Software Engineer at Philips
    Aug 2019 - Feb 2023 · 3 yrs 7 mos

    About: In 2017, Philips acquired Forcare, a leading innovator in open-standards-based interoperability software solutions for data flows between medical systems and information sources at the departmental and enterprise levels, as well as Health Information Exchanges across health systems. Forcare provides highly complementary capabilities for Philips, and enable Philips to deliver more effective, seamlessly integrated informatics solutions that improve clinical workflow, enhance patient care and optimize enterprise management. Primary responsibilities: - Refining and implementing new features. - Review code of peers. - Investigating and fixing bugs. - Maintaining our CI/CD builds. Secondary responsibilities: - Triage incoming defects, as part of the Defect Management Board. - Improve the development process with the Tech Enabler Guild. - Interview new candidate and improve the onboarding process. - Release activities at the end of every quarter. Tools: Java, Gradle, Git, Docker, Spring Core/Boot, Tomcat, SQL, Hibernate JPA, Jenkins, Amazon EC2, Amazon RDS, Packer, Terraform, Scrum, Agile, Atlassian Jira, Atlassian Bitbucket, Github, IntelliJ IDEA. Achievements: - Participated in the IHE Europe Connectathon in 2021. I had to quickly fix several bugs throughout the event, but in the end, all required tests passed. - Create a Spring Boot microservice that reads and updates patient privacy consents via FHIR. - Created a Jenkins build that propagates new versions of our 75+ internal libraries using the Bitbucket search API. This build is used daily and saves all developers a lot of risk-prone manual work. - Set up a Black Duck source code scan and automatically generate a HTML license report using a Groovy script. This allows us to easily check which legal licenses are in use and prevent us from using something that is blacklisted.

  • Software Engineer at Oracle
    Jun 2010 - Jul 2019 · 9 yrs 2 mos

    About: In 2010, most of the Dutch healthcare payers were already using Oracle Health Insurance's software solutions and the development of a new product was started, that focuses on the international market, using the knowledge gained from the old product in combination with the latest state-of-the-art technology. Our mission is to automate claim processing, reduce human error, lower the operating cost of healthcare payers, and ultimately decrease the premium of their members. Primary responsibilities: - Individually design and implement new functionality. - Investigate and resolve bugs and critical customer issues. - Peer code reviews. Secondary responsibilities: - CI/CD using Maven and Jenkins - Maintaining our many servers and database infrastructure. - 24/7 standby shifts. Tools: Java, SQL, PL/SQL, Maven, Groovy, Jenkins, Spring Core, EclipseLink JPA, SVN, Liquibase, Oracle Database, Oracle Weblogic, Oracle Coherence, Atlassian Jira, Atlassian Crucible, IntelliJ IDEA. Achievements: - Develop the core algorithms for the claim pricing and adjudication functionality (Java and PL/SQL), with a huge test suite (JUnit, Mockito, and MakeItEasy) to cover the many configurable variables. This was a major requirement to go live with our launching customer, Harvard Pilgrim Health Care. - Work together with the implementation consultants to implement complex customer scenarios using the product's Dynamic Logic feature, i.e. pair-programming configurable Groovy snippet. - Create a Maven MOJO that visualises the dependencies between our components and internal libraries. The graph became more and more important as the code base grew and was regularly printed to hang on the wall. - In 2017, I traveled to Abu Dhabi for a day, to train a customer in one of the application’s more intricate features. The training was well-received and they even asked for a weekly one hour (remote) meeting to ask questions about the topic.