Skip to résumé

Senior Software Engineer - Integrations Platform · Frontera

Senior Software Engineer - Integrations PlatformFrontera

I build integrations that make outside systems usable without hiding where the data came from or how it changed. At Frontera, the part I’m excited about is turning partner-specific records into data that product teams, clinicians, and ML engineers can use and trust.

U02

Service history

Technomancy IT LLC · Present

Founder / Product Engineer / Systems Lead

Turn incomplete client needs into running software, owning the interface, API, data model, delivery, and direct support. Build access-controlled AI and SaaS integrations for Slack, Google Workspace, Atlassian, and internal systems. Use authenticated MCP service boundaries, tenant-aware permissions, and observability where appropriate. Built full-stack software and supported the development environments used by data-science and ML engineers on a long-term sensor project.

Deep dive

Client work typically puts me on both sides of the handoff: I build the interfaces and integrations, then support the systems as people use them. The sensor engagement put me alongside the data-science team, with responsibility for full-stack work and DevOps support rather than training or validating their models.

Front Range Internet Inc. · 2015-2020

Senior Systems Engineer / Datacenter Architect

Led NOC escalations, built diagnostics for operators, maintained PHP and JavaScript web services, and developed and replaced production billing software.

Deep dive

I led first-line NOC operations and took technical escalations. During the ownership transition I held sole systems-engineering responsibility for approximately a year while the NOC continued to cover first-line incidents.

Office Evolution · 2014-2015

Systems / Software Engineer

Connected CRM, onboarding, and provisioning across roles. Built Linux-based network provisioning and a front-desk tool to reset Wi-Fi passwords and handle routine troubleshooting.

Deep dive

I built a Linux-based device that mapped each office to its own VLAN and provisioned bandwidth and access. Front-desk staff had a tool to reset Wi-Fi passwords and handle routine troubleshooting.

PlumChoice / Everon · 2012-2014

Network & Systems Engineer

Supported managed-service clients, diagnosed endpoint and network issues, and built diagnostic tooling for recurring incidents.

Deep dive

Managed-service work included endpoint and network troubleshooting, recurring diagnostics, and on-call support for customer incidents.

IBM · 2010-2012

Infrastructure and Systems Focal

Automated backup, audit, and compliance workflows. Wrote Perl, Bash, VBA and PHP scripts and built an internal backup tool adopted by executives and other staff.

Deep dive

The backup tool was built for internal use and replaced a licensing expense. Scripting also supported routine audit and infrastructure work.

U03

Systems and projects

Proofmark · client engineering

Proofmark: Document and identity integration workflows

Designed document lifecycle flows and explicit verification and fallback paths across React, tRPC and PostgreSQL. The workflow included webhooks, embedded signing and audit history.

Deep dive

The client contribution joined signer identity, document routing, verification, audit history, and PDF fields. The workflow included webhooks and embedded signing, with signer access, document state, and subsequent verification kept explicit.

Proofmark ↗

NuPrice · long-term client engagement · 2019–2021

NuPrice: Marketplace data and repricing integrations

Integrated Amazon marketplace and competitor data into the merchant repricing workflow. Built user-defined rules and automated price decisions, and owned monitoring, analytics, billing and ongoing technical support.

Deep dive

Owned a long-term client’s marketplace repricing product from ingestion and merchant-defined rules through monitoring, subscriptions, and support. The work began alongside my time at FRII; I was the client’s technical owner, not the founder of the client company.

U04

Inventory

  • TypeScript, Node.js, tRPC and PostgreSQL
  • Partner APIs, webhooks, data ingestion and transformation
  • OAuth/OIDC, SAML/SCIM and tenant-aware access
  • Data quality, audit trails and operational observability
  • Docker, CI/CD and production incident troubleshooting
U05

Cover note

I build integrations that make outside systems usable without hiding where the data came from or how it changed. At Frontera, the part I’m excited about is turning partner-specific records into data that product teams, clinicians, and ML engineers can use and trust.

Read full cover letterClose cover letter

Hi Frontera team,

What caught my eye is that you put integrations inside ML & Data. The mapping decisions made at the boundary determine what the rest of the organization can actually know. I’d like to own that work at Frontera, where getting the handoff right can save a care team from reconciling the same information by hand.

For NuPrice, I built and ran a marketplace repricing product that took in Amazon marketplace and competitor data and applied rules merchants configured themselves. I also owned monitoring, account and subscription workflows, and support. Supporting the product meant understanding the incoming data, the configured pricing rule, and what the customer saw. I brought the same attention to explicit state and handoffs to Proofmark, where I worked on signing identity, document routing, audit history, and integrations via webhooks and embedded signing.

My experience is with marketplace and SaaS systems rather than EHRs. I’d start by walking through real partner records with Clinical Operations and ML/Data, so we can agree on what the data actually means before standardizing it. I’d use AI with approved inputs to surface candidate mappings and unusual cases, then make the mappings reviewable and testable rather than letting the model decide what gets accepted. I wouldn’t put patient data into unapproved tooling.

Thanks, Chad Koslovsky