We are looking for an experienced, dependable developer to maintain and support a handful of existing SaaS platforms. This is not a role focused on rebuilding our platforms or launching large new products from scratch. We need someone who is comfortable stepping into existing codebases, understanding how the systems work, resolving bugs, maintaining integrations, improving reliability, and occasionally developing small features. You will work directly with the CTO, Kyle Hendrix, who will provide priorities and product direction. You will be responsible for the technical execution and ongoing health of the platforms.
Investigating and resolving customer-reported and internally identified bugs
Maintaining existing frontend and backend applications
Troubleshooting API, database, integration, and deployment issues
Developing occasional small features and platform improvements
Monitoring and improving application stability and performance
Maintaining third-party integrations and API connections
Managing deployments across staging and production environments
Reviewing logs and identifying the root cause of technical issues
Performing security, dependency, and framework updates when needed
Testing changes thoroughly before releasing them
Documenting technical decisions, fixes, and system changes
Keeping GitHub repositories, branches, and pull requests organized
Communicating technical issues and recommendations in clear, simple language
React
Next.js
Vue
Node.js
Python
Supabase
PostgreSQL
Cloudflare
Vercel
GitHub
Third-party APIs and webhooks
You do not need to be an expert in every technology listed. However, you should have strong full-stack experience, be comfortable working across multiple systems, and be able to learn an unfamiliar codebase without needing everything rebuilt in your preferred framework.
The right developer has demonstrated experience maintaining an existing SaaS application after its initial development.
You should be someone who:
Takes ownership of technical problems from investigation through resolution
Communicates clearly and responds consistently during working hours
Can independently diagnose issues across the frontend, backend, database, hosting environment, and integrations
Understands the difference between a temporary patch and a proper fix
Avoids unnecessary complexity and overengineering
Works carefully within an existing architecture
Tests changes thoroughly before deployment
Documents completed work so future maintenance is easier
Can explain technical issues to a nontechnical product owner
Is comfortable prioritizing reliability and maintainability over constantly introducing new technology
Can provide realistic estimates and communicate quickly when requirements or timelines change
Role Structure:
Part-time
Remote and open to applicants worldwide
Paid hourly
Must have consistent availability during U.S. business hours
Normal business-hours support only
No regular overnight or on-call requirement
Work will include ongoing maintenance, bug fixes, technical improvements, and occasional small features
The number of hours may vary based on current development and maintenance needs. We are looking for someone interested in building a long-term working relationship rather than completing a single short-term project.
Success in this role means:
Bugs are investigated and resolved efficiently
Production issues are communicated clearly
Changes are tested before release
The platforms remain stable and reliable
Technical debt is addressed thoughtfully without unnecessary rewrites
Small features are delivered without disrupting existing functionality
Documentation improves over time
The product owner always understands what is being worked on, what was completed, and whether any risks remain
Please submit the following:
A brief introduction describing your experience maintaining existing SaaS applications
Examples of SaaS products or production applications you have maintained
The technologies you are strongest in from the list above
Your current hourly rate
Your weekly availability
The U.S. business hours during which you can consistently be available
A brief example of a difficult production bug you diagnosed and resolved
An explanation of how you test changes before deploying them to production
Please begin your application with the words “Maintenance First” so we know you read the complete posting.
