Full-Stack Web Application Developer
Glandorf, OH
Job Opportunity: Full-Stack Web Application Developer with Altimate Outdoor
In 1982, Steve and Jane Alt started a small spouting company in Glandorf, Ohio, on a simple idea: honest work, done with integrity, was worth building a life around. Forty-plus years later, that company is Altimate Outdoor — and what started in spouting has grown into one of Ohio's premier outdoor living builders. StruXure pergolas, custom cabanas, outdoor kitchens, MagnaTrack retractable screens, screened-in patios. Two showrooms (Glandorf and Powell), nearly 60 people, five-star reviews, and a team that takes the work personally.
Ross and Jill Alt carry that legacy forward today, openly rooted in their Christian faith and the belief that every person — every craftsman, every designer, every team member, every family we serve — deserves to be treated that way. We're not asking you to share that faith. We are asking you to be the kind of person who can thrive in a company built on it.
We run on EOS. We have two 2026 company-wide goals that say it plainly: execute our technology strategy and execute our company-wide AI strategy. We can't do either without the right person owning the software side of the business.
That's this role.
We're hiring our first full-time, in-house developer to own our internal and customer-facing web applications. Not a ticket-taker. Not someone who lights up about AI prompts and calls it engineering. A real builder who can sit next to a designer for thirty minutes, watch them fight the system, and then go build the thing that fixes it.
If that sounds like the role you've been waiting for, keep reading.
How we operate — The Altimate Way
We have five values. They're not posters on a wall. They're how we make decisions, how we hire, and how we'll evaluate you.
"We serve with integrity and dedication, with optimism, persistently. That is the Altimate Way." — Jim Ledbetter
Translated into how this role gets done:
Service. Humbly put others first. You serve the team before you serve yourself. You build for the designer who has to live in the screen all day, not for the architecture diagram that looks good in a portfolio.
Integrity. Do the right thing, especially when no one is watching. You ship code you'd be proud to put your name on whether anyone reads it or not. You own mistakes quickly and cleanly. You don't quietly cut corners.
Dedication. Act with honor and excellence. You treat this like a calling, not a job. You bring your best on the days no one's watching. You finish the install before you leave the site.
Optimism. Hope in the face of challenge. When a deploy breaks or a project goes sideways, your default is "here's what we're going to do," not "here's why this happened."
Persistence. Show up and push on. You stay with the hard problems. You come back to a feature until it's right, not just done.
And we live by a pledge: if something isn't right, we make it right. Every time. No exceptions. Apply that to software and you've got the job description in one sentence.
What you'll actually be doing:
You'll own the web applications our team relies on every single day — sales, designers, installers, operations, leadership, and eventually our customers. That includes our CRM-style internal system, the integrations that pull leads in from our website, dealer networks, Google, Houzz, Angi, and the rest, the dashboards leadership uses to make decisions, and the AI-driven workflows we're going to build to keep our team focused on customers instead of paperwork.
You'll have a Rock or two on every quarterly plan. You'll be in the room when leadership decides what to build, what to buy, and what to leave alone. You'll see your work change how actual humans do their jobs.
A real week might look like this:
Shipping a feature that takes twenty clicks a day off a designer's quote workflow
Hunting down why one specific lead source isn't recording properly — and fixing it
Sitting in on a production meeting to understand a workflow before you build anything for it
Pushing a release at 6:30 a.m. so it's done before the team logs in — because you know better than to break Monday morning lead intake
Writing a one-pager explaining the tradeoffs on a build-vs-buy decision so leadership can actually make it
Driving up to Glandorf or Powell once a quarter to see the work, meet the team, and watch how things really happen
Who this is for:
You're probably a great fit if:
You've shipped real production software that real people depend on, and you've been on the hook when it broke
You can talk to a non-technical person without making them feel stupid, and turn what they say into a buildable spec
You like the idea of being the technical person who actually understands the business, not the one hiding in a Slack channel
You use AI coding tools because they make you faster, but you can also tell us exactly where you don't trust them
You'd rather own three systems and make them excellent than touch twelve and own none
You've built internal tools, CRMs, dashboards, scheduling apps, or anything else real operators use to run a real business — bonus if it was for a contractor, home services, or remodeling business
You're the kind of teammate other people want to work with — humble enough to listen, dedicated enough to finish, persistent enough to come back when something isn't right
You're comfortable working at a faith-rooted company even if your own background is different
Bonus on top of bonus: you've worked inside an EOS shop and know what an L10, a Rock, IDS, and an Accountability Chart actually feel like
Who this isn't for:
We'd rather be honest now than waste your interview slot. Skip this one if:
Your portfolio is mostly demos, tutorials, or AI-generated prototypes you've never had to support after launch
You think architecture diagrams are the fun part and everything after is a chore
You need a team of senior engineers around you to feel productive
You'd describe yourself as "more of a frontend person" or "more of a backend person" — we need someone comfortable everywhere
You're allergic to a workplace where faith is named openly
You're looking for a place to coast for two years and put a logo on a resume
The technical bar:
You should be solid on most of this and confident across the front end and back end:
Front end: JavaScript/TypeScript, plus React, js, Vue, or equivalent
Back end: Node.js, Python (Django/FastAPI), C#/.NET, PHP/Laravel, Ruby on Rails, or equivalent — pick your weapon, just be good with it
Database: PostgreSQL, MySQL, or SQL Server. You can write SQL without a GUI helping you
Cloud and deploys: AWS (preferred) or comparable, Git, CI/CD, real production deployment experience including the part where things go wrong
Integrations: APIs, webhooks, and the messy reality of connecting CRMs, schedulers, email/SMS, and the tool the marketing team picked without asking you
AI-assisted coding and AI workflows: Claude, Cursor, or Copilot for development speed — and real opinions about how to use AI in the business, not just the IDE
Bonus points for:
AWS