> Markdown version of [/jobs/ext/4336447-senior-backend-engineer-golang](https://www.wearedevelopers.com/jobs/ext/4336447-senior-backend-engineer-golang). Every page supports `.md` or `Accept: text/markdown`. Links point to the HTML versions so they work for humans too. Agent guide: [/agents.md](https://www.wearedevelopers.com/agents.md).

---

# Senior Backend Engineer (Golang)

- **Company:** Kunai
- **Location:** Chicago, IL, United States
- **Experience:** Expert
- **Salary:** $140,000.0 - $170,000.0
- **Contract:** Permanent contract
- **Skills:** Application Programming Interfaces (APIs), Amazon Web Services, Data Integrity, Data Mining, Cloud Services, Management of Software Versions, Scripting, Backend, Event Driven Architecture, Build Management, Ripple (payment Protocol), Apache Kafka, Legacy Systems, Web Api, Golang
- **Published:** October 17, 2026
- **Apply:** https://www.chicagocareersite.com/job.asp?id=3455052599&tx=JK9589FFR&pt=1&aff=0B19D771-A501-4A5E-8338-2A822B784D54&utm_source=Job%20Feed&utm_medium=textkernel&utm_campaign=DE&utm_term=0B19D771-A501-4A5E-8338-2A822B784D54

## About the Role

* 5+ years of backend engineering experience, with Go as your primary/preferred language
 * Experience building integration, abstraction, or platform layers that sit between legacy systems of record and modern consuming applications
 * Comfort working with transactional systems and/or payments
 * Experience with event-driven architectures like Kafka and CDC pipelines
 * Prior exposure to legacy core banking systems is a plus, though we don't expect Go engineers to write Profile/PSL themselves
 * Experience provisioning cloud services in AWS or other providers, * Bachelor's Degree, in lieu of a degree, demonstrating in addition to the minimum years of experience required for the role, three years of specialized training and/or progressively responsible work experience in technology for each missing year of college is required

## Description

You'll join as a Senior Backend Engineer working primarily in Go. You'll partner closely with our Profile Engineer, who owns the core-side implementation in FIS Profile's proprietary scripting language (PSL), while you build the integration layer that sits in front of it. You won't be writing new product-facing API endpoints - your focus is the layer underneath: data extraction, modeling, and the access patterns that let other teams' applications consume this data safely.

What you'll do

 * Design and build Go services that transform data surfaced from our core banking system into a consistent model usable by any downstream application
 * Partner with our Profile engineer and data engineers to define clean extraction points from the core - you won't write PSL yourself, but you'll need to understand enough of the data model and business-process mapping to design the right abstraction around it
 * Build and maintain the access layer (APIs and/or event streams) that lets other teams integrate with this data without touching the core directly
 * Enforce data integrity, access boundaries, and schema versioning so changes in the core don't ripple out to every consuming application
 * Integrate with existing API endpoints maintained by other teams - this role extends and consumes APIs, it does not originate new product-facing endpoints
 * Help define whether new data products are served via batch, event-driven (e.g. Kafka/CDC), or real-time APIs, depending on freshness requirements
 * Collaborate with data engineers on the same team to make new data products viewable/queryable downstream