Software Engineer (Python, React, Azure) - 2 Openings

Delavan Holdings•Delavan, WI

3d•Onsite

About The Position

Delavan Holdings is hiring two Software Engineers in Delavan, WI to build internal applications, system integrations, and AI-assisted automation in Python, TypeScript, and React on Azure. This is a full-time, on-site role where you will work directly with the teams who use the software you ship. You will turn real operating-company problems into working software, including internal tools, integrations between line-of-business systems, and AI-assisted automations that remove manual work. The Office of the CTO is building a small, senior technology team at the holding company that serves every operating company in the portfolio, and this is one of five roles being added to it. This is a hands-on building role where you will work directly with the people who use what you ship, prototype fast, validate, harden what sticks, and retire what does not. One of the more interesting parts of the job involves taking automations that non-technical teams build with Claude and deciding which of those deserve to become real systems, then rebuilding them as production-grade software without losing what made them useful in the first place.

Requirements

3 or more years of experience in software engineering, full-stack development, or systems integration, shipping working software
Working proficiency in Python and in TypeScript or JavaScript, with hands-on React experience building and maintaining web applications front to back
Strong SQL, ideally PostgreSQL, and experience with an ORM such as SQLAlchemy, Prisma, or Entity Framework, including designing schemas and diagnosing slow queries
Experience integrating systems through REST APIs, webhooks, and file exports, with common authentication patterns such as OAuth, API keys, and service accounts
Comfort with a modern development workflow: Git and GitHub, code review, an editor such as VS Code, and writing tests as a routine part of the work
Experience with Azure services and deployment patterns
Sound security and data governance habits: least-privilege access, secret management, and careful handling of sensitive data across multiple entities
A pragmatic, iterative working style, with good judgment about when scrappy is appropriate and when it is not
Strong written and verbal communication, and genuine willingness to sit with non-technical operators and understand their work before writing code

Nice To Haves

Hands-on production experience with LLM APIs, retrieval-augmented generation, or agent frameworks, with judgment about where AI genuinely helps and where it does not
You have been the technical lead on a project, owning architecture decisions and guiding other engineers
You have set engineering standards on a team: code review practice, testing expectations, CI/CD, or documentation
You have mentored other engineers, formally or informally
You have been the first or second engineer somewhere and know how to build for a team that does not exist yet
Experience with event-driven architectures such as queues, pub/sub, or streaming, for example with Redis
Experience deploying and operating production systems, including containers, serverless, CI/CD, and monitoring
You have worked under financial-reporting controls or audit requirements such as change logging and access review
You have trained users and driven adoption of something you built, rather than handing it over and moving on
Background in automotive retail, hospitality, logistics, or multi-entity or holding company environments

Responsibilities

Build and ship internal tools and applications end to end, across front end, back end, and data, that solve concrete operating-company problems
Prototype quickly, validate with real users, harden what sticks, and replace or retire what does not
Integrate line-of-business systems using their APIs, exports, and webhooks, building the custom glue where off-the-shelf options fall short
Build AI-assisted automations and agent workflows where they materially reduce manual effort, applying the same engineering discipline as any other software
Take automations that non-technical users built with Claude and rebuild them as production-grade, scalable software, preserving the original intent and logic while adding the reliability, security, and maintainability production requires
Work directly with operating-company stakeholders to understand a problem, then translate loose requirements into shippable software with a fast feedback loop
Keep everything in GitHub with code review, and write tests proportionate to what the solution touches
Take work through design, build, test, and release, deploying through staged Azure environments with controlled releases
Participate in sprint planning, backlog refinement, standups, reviews, and retrospectives, keeping work current in Asana and raising blockers early
Document what you build: what it does, what it connects to, how it authenticates, and how it deploys
Handle credentials, access, and data responsibly across entities, following least-privilege access, keeping secrets out of code, and respecting entity boundaries and data governance
Design for resilience and adaptability, preferring simple architectures and open, portable formats that survive tool and vendor changes
Support and monitor what you ship: reproduce, diagnose to root cause, fix, communicate status to affected teams, write the RCA, and run the lessons-learned review
Track the impact and reliability of what you build, share reusable patterns and components with the team, and help prioritize which problems to take on next