> Markdown version of [/jobs/ext/4426240-software-engineer](https://www.wearedevelopers.com/jobs/ext/4426240-software-engineer). 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).

---

# Software Engineer

- **Company:** LAKE EFFECT DATA LLC
- **Location:** Holland, MI, United States
- **Salary:** $45,000.0 - $60,000.0
- **Contract:** Permanent contract
- **Skills:** Application Programming Interfaces (APIs), Amazon Web Services, Microsoft Azure, Cloud Computing, Databases, Cron, Data Transmissions, Software Debugging, Next.js, Systems Integration, Web Applications, ReactJS, Cloudflare, Integration Frameworks, Nintex, Api Design, Serverless Computing
- **Published:** October 7, 2026
- **Apply:** https://www.indeed.com/viewjob?jk=11203c6986296aaf

## About the Role

* Experience building and shipping web applications (React or similar)
 * Comfort working in existing codebases: reading, debugging, and extending them
 * Familiarity with databases and SQL as used inside applications
 * Experience using and building APIs
 * Strong problem-solving and attention to detail
 * Able to work independently and clarify ambiguous requirements

Preferred Qualifications:

 * Next.js or similar modern web stack
 * Workflow automation and scheduled jobs (n8n, Azure Functions, cron, or similar)
 * Cloud and hosting: Azure, AWS, Vercel, Cloudflare, or similar
 * Auth, email, or other third-party integrations
 * Monitoring and troubleshooting in deployed environments
 * Clear technical writing: runbooks, architecture notes, requirement summaries

## Description

* Turn technical and business requirements into working apps, integrations, and workflows
 * Build and maintain web applications and small tools (data transfer, scheduled jobs, internal utilities)
 * Debug, test, and improve existing code
 * Connect systems through APIs and third-party services
 * Write the documentation needed to implement, hand off, and operate what you build
 * Work with technical and business stakeholders to close gaps before and during build, * Apps and tools that do the job they were scoped for, and keep doing it
 * Existing systems improved without introducing new ambiguity
 * Integrations and workflows that other people can operate
 * Documentation that matches what was built and speeds the next change