6 templates for companies that run on software without selling it: in-house business applications, mobile, vendor platform, application support, low-code, and contract. With BLS pay data, the FLSA computer employee exemption, and the IP clause generic templates skip. Download as DOCX.
The first developer I hired was not building a product. He was building the things that kept the company running: a quoting tool the sales team lived in, a bridge between two systems that refused to talk to each other, and a small mobile app customers used to book time with us. Every job description I could find online described a product engineer at a software company. None of them described him.
That mismatch is common, because most people who write software are not employed by software companies. The Bureau of Labor Statistics projects that employment of software developers, quality assurance analysts, and testers will grow 15 percent from 2024 to 2034, with roughly 129,200 openings a year on average, and a large share of those roles sit inside manufacturers, clinics, agencies, and distributors that will never sell a line of code.
Application developer is the title those employers reach for, and it is the first job title O*NET lists under the federal software developer occupation. At FirstHR we write hiring templates for that side of the market. The six below cover the versions small companies actually hire, and the rest of the library sits in our hiring templates section.
TL;DR
An application developer builds, customizes, and maintains the applications a business runs on rather than a product it sells. Federal data folds the title into Software Developers, SOC 15-1252, median $135,980 a year (BLS OEWS, May 2025). Most qualify as exempt computer employees, but support-heavy versions do not. Six templates below, downloadable as DOCX.
What an Application Developer Actually Does
An application developer designs, builds, tests, and maintains software applications for a specific business purpose. The defining feature is not the technology, it is the relationship to the user: the people who depend on the application usually work at the same company, and the requirements arrive as complaints rather than as specifications.
That changes the shape of the job. Product engineers spend most of their time on new capability. Application developers split the week between building, integrating, and keeping existing things alive, and the ratio is the single most useful thing you can state in a posting.
In-house business applications
The most common version
The developer builds and maintains the tools your own team uses: quoting, scheduling, inventory, internal portals, and the integrations between them. The users sit down the hall, and the requirements arrive as complaints rather than specifications.
Customer-facing mobile or web app
Ships to an app store
The application is something customers touch, which adds release cycles, store review, crash monitoring, and privacy disclosure to the job. Ownership of the developer account and the signing keys matters as much as the code.
Vendor platform extension
ERP, CRM, and their neighbors
The developer works inside a platform you bought: custom objects, workflows, reports, and integrations. Platform certifications matter more than general programming range, and upgrade testing is a permanent part of the job.
Product engineering at a software company
A different posting
If the application is the product you sell, you are hiring a product engineer and competing in the product engineering market. Our software developer templates fit that case better than the ones on this page.
Say What Share of the Week Is Maintenance
The most common reason a developer hire fails at a small company is a surprise about maintenance. The posting described building an application, and the job turned out to be sixty percent defect triage, user questions, and integrations that broke when a vendor changed an API. Neither side lied. Nobody said the number. Write it into the posting: how many applications exist today, how many users they serve, and roughly what portion of the week goes to keeping them running. Candidates who want that work will tell you so, and the ones who do not will leave you alone.
Application Developer vs Software Developer vs Programmer
There is no formal difference between an application developer and a software developer, and the federal classification treats them as one occupation. The 2018 Standard Occupational Classification revision merged the separate Software Developers, Applications code into a single Software Developers occupation, SOC 15-1252, which is why no current wage table lists application developers on their own.
What survives is a difference in market signal. The title you post sorts candidates before anyone reads the responsibilities, so choose it deliberately rather than copying whatever the last posting used. Our software developer templates cover the product engineering case, and the computer programmer templates cover the narrower code-and-test version of the work.
Title
What it usually signals
BLS classification and May 2025 median
Application developer
Builds and maintains the applications a business runs on, often inside a non-software company
Software Developers, 15-1252: $135,980
Software developer
Broad development work, frequently on a product the employer sells
Software Developers, 15-1252: $135,980
Software engineer
Same occupation, with a stronger pull toward product companies and systems design
Software Developers, 15-1252: $135,980
Computer programmer
Writes, modifies, and tests code against a design someone else produced
Computer Programmers, 15-1251: $100,390
Web developer
Websites and web applications, front end through delivery
Web Developers, 15-1254: $92,650
QA analyst or tester
Tests applications and documents defects rather than building features
Software QA Analysts and Testers, 15-1253: $104,300
Systems analyst
Analyzes business problems and designs the system response, less hands-on coding
Computer Systems Analysts, 15-1211: $105,850
One practical consequence: if you post software engineer at a company that is not a software company, you will attract product engineers who find the maintenance half of the role disappointing, and you will replace them within two years. If you post web developer for a role that is mostly integrations, you will get portfolios full of marketing sites.
What Belongs in an Application Developer Posting
A good application developer posting does four jobs at once: it describes the real work, it filters people who want a different job, it protects you on classification and ownership, and it closes the candidate. Most postings do only the first, and they do it in generic language that could describe any employer.
The parts developers read first
The actual stack, named, not implied
Whether this is new build, maintenance, or both
Team size and who else writes code here
Remote, hybrid, or on-site, stated plainly
The parts that filter applicants
Years of experience tied to a specific kind of work
Platform or vendor certification, marked required or preferred
Integration and database expectations
On-call, release windows, and support load
The parts that protect you
FLSA classification stated on the posting
Intellectual property assignment mentioned up front
Essential functions written plainly
Equal opportunity statement
The parts that win the hire
Salary or a good-faith range
What the developer will own outright
Decision-making autonomy and access to users
A named person and a real timeline to apply
The omission that costs small companies most is the stack. Naming your languages, platforms, databases, and the systems you integrate with is not a detail, it is the first filter a developer applies. Our guide to writing a job description covers the general structure, and the specifics below are what this role adds on top.
6 Application Developer Job Description Templates
Download all six as one file or copy them individually. Each follows the same structure: company overview, position summary, key responsibilities, required qualifications, nice to have, a classification and ownership note, an equal opportunity statement, and how to apply. The bracketed fields are the only parts you need to change.
Download All 6 Application Developer Job Description Templates
In-house, mobile, business platform, application support, low-code, and contract. All in one download.
In-House Application Developer
Internal business tools
The baseline version: internal applications, integrations, and the support that comes with owning them. Start here and add your stack.
Mobile Application Developer
iOS, Android, or both
For a customer-facing app: release management, store review, crash monitoring, and the account and signing-key ownership question.
Business Applications Developer
ERP, CRM, platform work
For extending a platform you already bought: custom logic, reports, integrations, upgrade testing, and vendor certification requirements.
Application Support Developer
Maintenance and enhancement
For keeping working software working: defect triage, root cause analysis, small enhancements, and the classification trap that comes with it.
Low-Code Application Developer
Internal tools, fast
For turning spreadsheets and manual handoffs into governed internal applications, with an honest note on when the exemption does not apply.
Contract Application Developer
Scope of work, not a posting
For a fixed engagement: deliverables, acceptance criteria, IP assignment, and the misclassification warning small companies most often ignore.
Template 1: In-House Application Developer
The baseline version for a company that runs on software without selling it: internal applications, integrations, releases, and the second-line support that comes with owning them.
Application Developer Job Description (In-House Business Applications)
APPLICATION DEVELOPER JOB DESCRIPTION
Company: __ ([City, State])
Reports to: [IT Manager / Operations Director / Founder]
FLSA status: Exempt (computer employee; see classification note)
Compensation: $_ per year
ABOUT [COMPANY NAME]
[Company Name] is a [industry] company in [City, State] with [team size] people.
We are not a software company. We run on a set of applications that our team
depends on every day, and we are hiring a developer to own them: build the new
ones, improve the ones we have, and keep the whole set connected.
POSITION SUMMARY
The Application Developer designs, builds, tests, and maintains the business
applications this company runs on. The role covers new internal tools,
enhancements to existing applications, integrations between systems, and the
day-to-day support that keeps them all working.
KEY RESPONSIBILITIES
•Gather requirements from the teams who will use the application, in their
language rather than in technical specifications
•Build and ship features in [language / framework / platform]
•Design and maintain integrations between [system A], [system B], and
[our data warehouse / accounting system / CRM]
•Write and maintain automated tests, and fix defects reported by users
•Review database schemas and queries for correctness and performance
•Document what you built so the next person can maintain it
•Handle release, deployment, and rollback for the applications you own
•Provide second-line support for issues the help desk cannot resolve
•Take part in [on-call rotation / release windows], if applicable
REQUIRED QUALIFICATIONS
•[Number] years building and maintaining business applications
•Working command of [language], [framework], and [SQL / relational databases]
•Experience with version control, code review, and a deployment pipeline
•Ability to talk to non-technical colleagues and turn a vague request into a
scoped piece of work
•[Bachelor's degree in computer science or equivalent practical experience]
NICE TO HAVE
•Experience in [our industry] or with [regulated data / payment flows]
•[API design / cloud platform / reporting and BI tooling]
•Experience being the only developer on a team
CLASSIFICATION AND IP NOTE (read before posting)
Most full-time application developers qualify as exempt computer employees when
the primary duty is systems analysis, design, development, or testing, and the
employee is paid at least the standard salary level on a salary basis or at
least $27.63 per hour. Job title alone never establishes the exemption; duties
and pay do. Put an intellectual property assignment in the offer letter or
employment agreement so the company owns the code, and confirm your state rules
on invention assignment before you write the clause. This is general
information, not legal advice.
EEO STATEMENT
[Company Name] is an equal opportunity employer and provides reasonable
accommodations for the essential functions of this role.
COMPENSATION AND HOW TO APPLY
Compensation: $_ per year, [benefits summary], [equity, if any]
To apply, email __ with your resume and a short note about
an application you built and still maintain.
Template 2: Mobile Application Developer
For a customer-facing app on one or both mobile platforms, with release management, store review, crash monitoring, and the account ownership question stated up front.
Mobile Application Developer Job Description
MOBILE APPLICATION DEVELOPER JOB DESCRIPTION
Company: __ ([City, State])
Reports to: [Product Manager / Engineering Lead / Founder]
For extending a platform you already bought: custom logic, reports, integrations, upgrade testing, and vendor certification requirements marked required or preferred.
Business Applications Developer Job Description (ERP, CRM, Platform)
BUSINESS APPLICATIONS DEVELOPER JOB DESCRIPTION
Company: __ ([City, State])
Reports to: [IT Manager / Finance Director / Operations Director]
FLSA status: Exempt (computer employee) in most cases; see classification note
Compensation: $_ per year
ABOUT THIS ROLE
[Company Name] runs its business on [our ERP platform], [our CRM], and
[our HR system]. Off-the-shelf configuration got us most of the way. We are
hiring a Business Applications Developer to build the rest: custom objects,
reports, workflows, and the integrations that move data between them.
POSITION SUMMARY
The Business Applications Developer extends and integrates our vendor platforms,
builds reporting and automation on top of them, and acts as the technical owner
for [platform] releases and upgrades.
KEY RESPONSIBILITIES
•Configure and extend [platform] with custom objects, fields, and logic
•Build reports and dashboards for [finance / sales / operations]
•Design and maintain integrations between [platform] and [other systems]
•Manage sandbox, testing, and release process for platform changes
•Test and remediate customizations ahead of each vendor upgrade
•Maintain user roles, permissions, and data access rules with [IT / security]
•Document customizations so the company is not dependent on one person
•Train power users and write the internal how-to material
REQUIRED QUALIFICATIONS
•[Number] years developing on [platform] or a comparable enterprise platform
•[Vendor certification: name the specific one you require, or mark preferred]
•Experience with the platform’s own scripting or configuration language
•Integration experience: APIs, middleware, or file-based data exchange
•Ability to explain a technical constraint to a finance or sales audience
NICE TO HAVE
•Data migration experience
•Experience in a company of our size, where one person owns several platforms
•[Reporting / BI tooling] beyond the platform’s built-in reports
CLASSIFICATION NOTE
The FLSA computer employee exemption reaches systems analysis, program design,
and development. It does not reach an employee whose primary duty is operating
software, entering data, or providing routine help desk support, even in a role
that carries a technical title. If most of the week is user administration,
password resets, and data entry rather than design and development, classify the
role as non-exempt and track hours. Decide on the actual duties, not the title
on the posting. This is general information, not legal advice.
EEO STATEMENT
[Company Name] is an equal opportunity employer and provides reasonable
accommodations for the essential functions of this role.
COMPENSATION AND HOW TO APPLY
Compensation: $_ per year, [benefits summary], [certification budget]
To apply, email __ with your resume and the platforms you
have built on.
Template 4: Application Support Developer
For keeping working software working: defect triage, root cause analysis, small enhancements, and reliability improvements. Read its classification note before you set the pay.
Application Support Developer Job Description (Maintenance and Enhancement)
•Meet the response and resolution targets in our internal service standard
REQUIRED QUALIFICATIONS
•[Number] years supporting or maintaining production applications
•Strong debugging skills in [language] and [SQL]
•Comfort reading code you did not write and did not choose
•Clear written communication with the people who reported the problem
•[Bachelor's degree in a technical field or equivalent practical experience]
NICE TO HAVE
•Experience with [our stack] or a similar legacy environment
•Incident management or on-call experience
•Automation of repetitive support work
CLASSIFICATION NOTE (read this one carefully)
This is the role where classification most often goes wrong. The computer
employee exemption covers systems analysis, program design, development, and
testing. It expressly does not cover employees engaged in the operation of
computers or in routine help desk work, and the exemption also requires either
the standard weekly salary on a salary basis or at least $27.63 per hour. A
developer who spends the week diagnosing defects and writing fixes is doing
exempt work. A person who spends the week resetting passwords, running scripted
checks, and escalating tickets is not. Split the role honestly, and if the
support half dominates, make it non-exempt and pay overtime past forty hours in
a week. This is general information, not legal advice.
EEO STATEMENT
[Company Name] is an equal opportunity employer and provides reasonable
accommodations for the essential functions of this role.
COMPENSATION AND HOW TO APPLY
Compensation: $_ per year, [benefits summary], [on-call differential]
To apply, email __ with your resume and a description of
the hardest defect you have tracked down.
Template 5: Low-Code Application Developer
For turning spreadsheets and manual handoffs into governed internal tools, with an honest note on when the computer employee exemption does not reach configuration work.
Low-Code Application Developer Job Description
LOW-CODE APPLICATION DEVELOPER JOB DESCRIPTION
Company: __ ([City, State])
Reports to: [Operations Director / IT Manager / Founder]
•Apply data access rules so people see only what they should
•Test with real users before rollout and iterate on their feedback
•Document each application: owner, purpose, data sources, and dependencies
•Retire tools that stopped being used instead of leaving them running
•Escalate to a traditional development approach when the platform is the wrong
fit, rather than forcing it
REQUIRED QUALIFICATIONS
•Demonstrated applications built on [platform] or a comparable low-code tool
•Understanding of relational data: tables, keys, and why duplication hurts
•Process mapping and requirements gathering with non-technical colleagues
•Judgment about when a low-code tool stops being the right answer
•[No formal degree required: state your position explicitly]
NICE TO HAVE
•Scripting in [language] for the parts the platform cannot do
•Experience with governance: naming, ownership, and access review
•Background in [our industry] operations
CLASSIFICATION NOTE
Do not assume the computer employee exemption applies here. It is written around
systems analysis, program design, development, and testing at a level of skill
the regulation describes as theoretical and practical application of highly
specialized knowledge, and it also carries a pay floor. A configuration-focused
role built on drag-and-drop tools may or may not clear that bar, and the safe
answer for a borderline role is non-exempt with tracked hours and overtime.
Assess this one on the real duties before you write a salary on the posting.
This is general information, not legal advice.
EEO STATEMENT
[Company Name] is an equal opportunity employer and provides reasonable
accommodations for the essential functions of this role.
COMPENSATION AND HOW TO APPLY
Compensation: $_ per [year / hour], [benefits summary]
To apply, email __ with your resume and a walkthrough of an
internal tool you built.
Template 6: Contract Application Developer
Written as a scope of work rather than a job posting, with deliverables, acceptance criteria, and intellectual property assignment. Pair it with our employment contract template if you decide the role should be permanent instead.
Contract Application Developer Job Description and Scope of Work
CONTRACT APPLICATION DEVELOPER SCOPE OF WORK
Company: __ ([City, State])
Engagement type: Independent contractor, [fixed scope / time and materials]
Term: [start date] to [end date], or until deliverables are accepted
Rate: $_ per [hour / deliverable / milestone]
Point of contact: __
ENGAGEMENT SUMMARY
[Company Name] is engaging a contract application developer to deliver
[application or component]. This document describes the deliverables, the
acceptance criteria, and the terms. It is written as a scope of work rather than
a job posting, because the relationship is a contract, not employment.
DELIVERABLES
•[Deliverable 1]: description, and what "done" means
•[Deliverable 2]: description, and what "done" means
•[Deliverable 3]: description, and what "done" means
•Source code delivered to our repository, with build and deploy instructions
•Written handover documentation covering architecture and known limitations
•[Number] weeks of defect correction after acceptance, at no additional charge
ACCEPTANCE CRITERIA
•Each deliverable meets the written specification agreed at kickoff
•Automated tests pass in our environment, not only the contractor’s
•No open defects rated [severity level] or above
•Handover session completed with [named internal owner]
CONTRACTOR REQUIREMENTS
•Demonstrated delivery of comparable applications, with references
•Own equipment, own tools, own working hours
•[Insurance requirements, if any]
•Signed contractor agreement, IP assignment, and confidentiality agreement
before any work begins
INTELLECTUAL PROPERTY
All work product, including source code, documentation, and designs, is assigned
to [Company Name] on creation. Absent a written assignment, a contractor
generally retains copyright in what they create, even when you paid for it, so
this clause is not optional. Confirm that any third-party or open-source
components are identified and licensed for our intended use.
CLASSIFICATION WARNING (read before signing)
Calling someone a contractor does not make them one. If you set the schedule,
direct the method, supply the equipment, integrate the person into your team
indefinitely, and treat the engagement as ongoing employment, a tax or labor
agency can reclassify the relationship and assess back taxes, unpaid overtime,
and penalties. A genuine contractor controls how the work gets done, carries
business risk, and typically serves other clients. If what you actually need is
a permanent developer, hire an employee and use one of the other templates on
this page. This is general information, not legal advice.
HOW TO SUBMIT A PROPOSAL
Send a proposal to __ with your approach, timeline, rate,
and two references from comparable engagements. Proposals due [date].
Overtime, Exemptions, and Who Owns the Code
Most full-time application developers are exempt from overtime under the computer employee exemption, but the exemption is narrower than the title suggests and it carries a pay test of its own. Getting it wrong is expensive in both directions: unpaid overtime on one side, and an unnecessary salary floor on the other.
The rule lives in the general rule for computer employees, which requires either the standard weekly salary on a salary basis or an hourly rate of at least $27.63, plus a primary duty of systems analysis, program or system design, development, documentation, testing, or modification. The Department of Labor summarizes the same test in Fact Sheet 17E and states that job titles never determine exemption status.
The computer employee exemption has its own pay rule
Sections 13(a)(1) and 13(a)(17) of the Fair Labor Standards Act exempt computer systems analysts, programmers, software engineers, and similarly skilled workers when the duties test is met and the employee is paid either the standard salary level on a salary basis or at least $27.63 an hour. That hourly alternative is unusual and it is specific to this exemption: nowhere else can you pay by the hour and still claim an overtime exemption. The duties side is narrower than most employers assume. It reaches systems analysis, program and system design, development, documentation, testing, and modification. It does not reach an employee whose work depends on computers but is not development work. The Department of Labor also states plainly that job titles do not determine exemption status. This is general information, not legal advice.
Support and help desk work is the usual failure point
The regulation excludes employees engaged in the operation of computers or in routine help desk and troubleshooting work from the computer exemption, and that is exactly where small companies get caught. A single hire often carries a mixed load: some genuine development, plus password resets, user administration, hardware questions, and ticket triage, because there is nobody else to do it. If the development half is the primary duty, the exemption is available. If the support half is what fills the week, the role is non-exempt, hours have to be tracked, and overtime is owed past forty in a week. Write the split into the job description before you hire, then check it again after six months, because these roles drift toward support without anybody deciding that they should.
Without a written assignment, you may not own the code
Employers routinely assume that paying for software means owning it. For employees creating work within the scope of employment, the work-made-for-hire rule usually gets you there, but for independent contractors it generally does not: absent a signed written assignment, the contractor retains copyright in what they wrote. Custom software is also not one of the narrow categories that can be a commissioned work made for hire, so the assignment has to be explicit. Put an intellectual property assignment in every offer letter and every contractor agreement, signed before work starts rather than after delivery. Check your state law too, since several states limit assignment of inventions an employee develops entirely on their own time without company resources. This is general information, not legal advice.
Access, offboarding, and the single-developer risk
The application developer at a small company usually holds production database access, deployment rights, cloud console credentials, app store accounts, and the code signing keys. That concentration is normal and it is manageable, but only if you set it up at hire rather than at departure. Register every account, repository, domain, and store listing to a company identity, not a personal one. Keep an inventory of what the developer can reach. Require code in a company-owned repository from the first commit rather than on a laptop. Then build the reverse of that list into offboarding so access ends the day employment does. The worst version of this story is a company that cannot deploy a fix because the only person with the keys left three weeks ago.
If a role sits near the line, our breakdown of exempt versus non-exempt classification works through the tests in order. For an engagement you are planning to run on a contract, read 1099 versus W-2 classification first, because a contractor you direct like an employee is the most common and most expensive version of this mistake.
What to Pay an Application Developer
There is no separate federal wage figure for application developers, because the occupation was folded into Software Developers in the 2018 classification revision. Benchmark against that occupation, then adjust down toward the lower percentiles if you are a non-technology employer outside a major technology metro.
Software Developers, National Wage Percentiles
According to the Bureau of Labor Statistics Occupational Employment and Wage Statistics survey (May 2025), software developers (SOC 15-1252) earned a median of $135,980 per year, or $65.38 per hour. The 10th percentile earned $82,460, the 25th $105,210, the 75th $171,980, and the 90th $214,670 (U.S. Bureau of Labor Statistics, OEWS national estimates).
Benchmark
National figure (BLS OEWS, May 2025)
How to use it
Software developers, median
$135,980 per year
The headline occupation that covers application developers
Software developers, 10th percentile
$82,460 per year
Realistic floor for an early-career in-house role outside a tech metro
Software developers, 25th percentile
$105,210 per year
Common landing zone for a first developer hire at a small company
Software developers, 90th percentile
$214,670 per year
Senior product engineering at large technology employers
Computer programmers, median
$100,390 per year
Closer benchmark for code-and-test work against someone else’s design
Software QA analysts and testers, median
$104,300 per year
For a testing-weighted role rather than a building one
Web developers, median
$92,650 per year
For a web-only application scope
Computer systems analysts, median
$105,850 per year
For an analysis-heavy role with less hands-on development
Two adjustments matter more than the national median. First, the percentile ladder is wide enough that the same job title spans $82,460 to $214,670, so pick a percentile deliberately and say why. Second, publish a good-faith range wherever pay transparency laws apply, and compete on ownership, autonomy, and access to users rather than on matching technology company salaries you cannot match.
Companies Using FirstHR Onboard 3x Faster
Join hundreds of small businesses who transformed their new hire experience.
Screen on evidence of maintained work rather than on the technology list. Ask each candidate to describe an application they built and still support, then follow the answer down two levels: what broke, what they changed, and what they would do differently now. That conversation separates people who ship from people who list.
The second thing worth buying is one hour of an outside technical opinion. A trusted developer friend or a paid advisor sitting in on a deep screen catches things a non-technical interviewer cannot, and it costs a fraction of a bad hire. Our guide to finding developers for a small company covers sourcing when you have no technical network to draw on.
A Take-Home That Nobody Would Do for Free Is Not a Screen
Long unpaid exercises filter for availability, not ability, and the strongest candidates simply decline them. Keep any practical exercise short, pay for it if it runs beyond an hour, and make it resemble your real work: a small integration, a defect in a codebase they did not write, or a data model for something your business actually does. Then discuss the result live. What a candidate says about their own solution is worth more than the solution.
Hiring an Application Developer Without an HR Department
Small company developer hiring fails in three predictable places: nobody can evaluate the candidate, the title attracts the wrong pool, and the first week is wasted because access was never provisioned. Each has a fix that costs almost nothing.
You are hiring a developer and nobody at the company can evaluate one
This is the honest starting position at most small companies: the founder or the operations lead is hiring for a skill set nobody in the building has. The usual reaction is to lean on the resume, the degree, and the list of technologies, which is exactly the part of an application a candidate controls completely. A better structure costs less than a bad hire. Ask each candidate to describe an application they built and still maintain, and follow the answer down two levels of detail. Bring in a trusted technical friend or a paid advisor for one hour of the process. Use a short paid exercise that resembles your real work rather than an abstract puzzle. And check references with people who used the software, not only with people who managed the developer.
The job title you post decides which candidate pool you get
Application developer, software developer, software engineer, and programmer overlap heavily in practice, but they sort candidates differently. Post software engineer at a non-software company and you attract product engineers who will be disappointed by the integration and maintenance half of the role, then leave. Post application developer and you reach the large group of people who build the systems businesses run on and who consider that work a career rather than a stepping stone. Say plainly in the first paragraph that you are not a software company, name the stack, and state how much of the week is new build versus maintenance. Self-selection is cheaper than screening.
The developer starts and nothing is ready for them
A developer with no repository access, no environment, no accounts, and no context spends the first week waiting. Technical onboarding needs a sequence and an owner, and at a small company that owner is usually the person who did the hiring. FirstHR was built for that person. The onboarding wizard runs the same sequence for every hire, e-signature handles the offer letter, the intellectual property assignment, and the confidentiality agreement, document management keeps the signed copies against the employee profile, and task workflows assign the access provisioning to whoever actually grants it, with due dates before day one. Applicant tracking is coming soon to FirstHR. Note that FirstHR is an onboarding and HR platform, not a payroll provider.
Once the offer is signed, the work shifts to a repeatable onboarding checklist, and for this role specifically our developer onboarding guide covers the sequence from repository access through the first shipped change.
Key Takeaways
Application developer usually describes someone building and maintaining the applications a business runs on, not a product the employer sells, and the split between new build and maintenance is the most useful thing a posting can state.
Federal data has no separate application developer occupation: the 2018 classification revision folded it into Software Developers, SOC 15-1252, and O*NET lists Application Developer as a reported title under it.
The median wage for that occupation was $135,980 a year (BLS OEWS, May 2025), with a 10th percentile of $82,460 and a 90th of $214,670, so pick a percentile deliberately rather than quoting the median.
The FLSA computer employee exemption needs a development primary duty plus either the standard salary on a salary basis or at least $27.63 an hour, and it excludes routine help desk and computer operation work.
Without a signed written assignment, an independent contractor generally keeps copyright in code you paid for, so sign the intellectual property assignment before work begins for both employees and contractors.
Register repositories, cloud consoles, domains, and app store accounts to the company rather than to an individual, and build the reverse of that list into offboarding.
A developer hire brings more paperwork than most: the offer, the intellectual property assignment, the confidentiality agreement, and a provisioning list that has to be done before day one. FirstHR runs that sequence with e-signature, document storage against each employee profile, and task workflows assigned to the people who actually grant access. Applicant tracking is coming soon to FirstHR.
Frequently Asked Questions
What does an application developer do?
An application developer designs, builds, tests, and maintains the software applications an organization uses or sells. In practice the title is used most often by companies that run on software without selling it: the developer owns internal business applications, the integrations between systems, a customer-facing mobile or web app, or the customizations layered on top of a purchased platform. The work splits differently from product engineering. Expect a meaningful share of the week to go to maintenance, defect resolution, small enhancements, and conversations with the colleagues who use the application, rather than to greenfield feature development. Federal wage data does not track the title separately: O*NET lists Application Developer as a reported job title under the Software Developers occupation, SOC 15-1252.
What is the difference between an application developer and a software developer?
There is no formal distinction, and the federal classification treats them as one occupation. The 2018 Standard Occupational Classification revision merged the old code for Software Developers, Applications into a single Software Developers occupation, SOC 15-1252, and O*NET lists Application Developer as a reported job title under it. The difference is one of practice and market signal. Application developer usually describes someone building and maintaining the applications a business runs on, often inside a company that is not a software company. Software developer and software engineer skew toward product work at technology companies. That matters when you write the posting, because the title you choose determines which candidate pool sees it and what they expect the job to be.
How much does an application developer make?
According to the Bureau of Labor Statistics Occupational Employment and Wage Statistics survey (May 2025), the median annual wage for software developers, the occupation that covers application developers, was $135,980, or $65.38 per hour. The range is wide: the 10th percentile earned $82,460 and the 90th percentile earned $214,670. Adjacent classifications sit lower, with computer programmers at a median of $100,390, software quality assurance analysts and testers at $104,300, and web developers at $92,650. National medians are heavily weighted toward technology employers in expensive metros. For a non-technology company hiring an application developer, benchmark against employers of your size and location rather than the national figure, and publish a good-faith range where pay transparency rules require one.
Are application developers exempt from overtime?
Usually yes, but not automatically. The Fair Labor Standards Act computer employee exemption covers computer systems analysts, programmers, software engineers, and similarly skilled workers whose primary duty is systems analysis, program or system design, development, documentation, testing, or modification, and who are paid either the standard salary level on a salary basis or at least $27.63 an hour. The hourly alternative is unique to this exemption. Two limits matter for small companies. The exemption does not cover employees engaged in the operation of computers or in routine help desk and troubleshooting work, so a mixed developer and support role has to be judged on which half dominates the week. And the Department of Labor is explicit that job titles never determine exemption status. This is general information, not legal advice.
Who owns the code an application developer writes?
For an employee creating software within the scope of employment, the work-made-for-hire rule generally puts ownership with the employer, and a written intellectual property assignment in the offer letter removes any argument. For an independent contractor it is the opposite default: absent a signed written assignment, the contractor retains copyright in the code even though you paid for it, and custom software is not one of the narrow categories that can qualify as a commissioned work made for hire. Get the assignment signed before work starts. Several states also limit assignment of inventions an employee develops entirely on their own time without company resources, so check your state rules before writing the clause. This is general information, not legal advice.
Should I hire an application developer as an employee or a contractor?
Hire an employee when the work is ongoing, when you direct how it gets done, and when the applications need an owner rather than a delivery. Use a contractor for a defined project with deliverables, acceptance criteria, and an end date. The mistake that costs money is running a contractor like an employee: setting their schedule, supplying their equipment, directing their methods, and renewing the engagement indefinitely. That pattern invites reclassification and back taxes, unpaid overtime, and penalties. If you go the contract route, write a scope of work rather than a job posting, sign the intellectual property assignment and confidentiality agreement before any work begins, and require the source code in your repository with handover documentation as part of acceptance.
How do I hire an application developer with no technical team and no HR department?
Run a fixed sequence and lean on structure rather than instinct. Write a posting that names your stack, states plainly that you are not a software company, and describes how much of the week is new build versus maintenance, because that self-selection saves more time than any screening step. Ask every candidate to walk you through an application they built and still maintain, then follow the answer down two levels of detail. Buy one hour of a trusted technical advisor for the deep screen. Use a short paid exercise that resembles your actual work. Check references with the people who used the software, not only with the manager. Then run onboarding as a checklist: signed offer, intellectual property assignment, confidentiality agreement, account and repository provisioning, and a 30-60-90 plan. Applicant tracking is coming soon to FirstHR.
