Application Developer Job Description

An Application Developer builds and maintains the software that people open to get work done: a claims portal at an insurer, a permit system at a city, a student records app at a university, a banking app on a phone. The federal occupation system files the title squarely under software developers. The BLS 2018 SOC direct-match title file places "applications developer" in code 15-1252, Software Developers, so federal pay and employment figures for the title are the figures for software developers as a group.

Day to day, the job is a loop of requirement, design, code, test and ship. A request arrives from a business owner or product manager, often vague. The developer turns it into a plan: which screens change, which tables need new columns, which API calls are involved, what can break. Then comes the code itself, written in whatever stack the shop runs, with unit tests alongside it and a pull request that a teammate reviews before anything merges. After release, the same developer watches logs and error dashboards, takes the escalated ticket when a batch job fails at 2 a.m., and writes the fix.

Missouri State University's class specification for its Application Developer title is a useful picture of the in-house version of the role. It says the position creates and maintains computer software and associated documentation, participates in the systems design process, and takes on projects ranging from maintenance to major modifications to new systems. Its listed duties include working with the requesting user and a systems analyst to plan each request, debugging problems, testing and reviewing programming changes, coding job scheduler chains, and following security standards on new or purchased systems.

The platform owners also set part of the agenda. On mobile, Apple sets minimum SDK requirements for apps uploaded to App Store Connect, and Google Play sets a minimum target API level for new apps and app updates. Each new floor means an upgrade sprint: bump the SDK, fix deprecated APIs, retest permissions and notifications, and resubmit.

Security work sits inside the job rather than beside it. The OWASP Top 10:2025, which the OWASP Foundation calls a standard awareness document for developers and web application security, puts Broken Access Control first and lists Software Supply Chain Failures at A03 and Mishandling of Exceptional Conditions at A10. For an application developer that translates into concrete habits: checking authorization on every endpoint, pinning and scanning third-party packages, and making sure an exception fails closed instead of leaking data.

Accessibility is the other standing requirement. Semantic markup, keyboard paths, labeled form fields, sufficient color contrast and captioned media are all decisions made by the people who build the screens, so an accessibility defect belongs in the same backlog, and the same sprint, as any other bug.

A bachelor's degree in computer science, information systems, software engineering or a related field is the usual starting credential. BLS says software developers typically need a bachelor's degree in computer and information technology or a related field. Public employers sometimes write the requirement more flexibly: Missouri State University's Application Developer specification requires an associate's degree or an equivalent combination of education and experience, and lists a bachelor's degree with an emphasis in computer-related courses as preferred.

As a rough guide, an entry-level application developer has one to two years of internship, co-op or project work behind them, and a developer trusted to own a module or a small system has roughly three to five years of production experience. Treat those as rules of thumb rather than a hiring standard; the title covers everything from a junior on a large team to the sole developer at a small agency.

Technical skills worth having

• One or two production languages in depth. The Missouri State specification is a fair snapshot of an enterprise shop: it asks for fluency in two or more of PL/SQL, T-SQL, Java, Groovy, C#, Python or similar languages.
• Relational databases: writing SQL by hand, reading query plans, designing tables that will not need a rewrite in two years.
• Web and API work: REST endpoints, JSON, authentication, and at least one front-end framework such as React, Angular or Vue.js.
• Git, pull requests, code review etiquette, and a CI pipeline that runs tests on every push.
• Mobile toolchains if the job ships apps: Xcode and Swift on Apple platforms, Android Studio and Kotlin on Android, plus the store submission process on each.
• Accessibility basics measured against WCAG 2.1 Level AA, and secure coding habits mapped to the OWASP Top 10.
• Working with AI coding assistants without trusting them blindly: writing a clear task, reading the generated diff line by line, and rejecting what does not fit the codebase.

Certifications

No license is required to work as an application developer, and certifications are optional. If you pursue one, pick a platform your employer runs: AWS Certified Developer - Associate, awarded by Amazon Web Services, for AWS shops, or Oracle Certified Professional: Java SE 21 Developer, awarded by Oracle, for Java teams. For developers moving toward security-heavy work, the Certified Secure Software Lifecycle Professional (CSSLP) is awarded by ISC2.

Habits that separate strong developers

• Asking the clarifying question before writing code, not after the demo.
• Writing a pull request description a reviewer can follow without a meeting.
• Leaving documentation that lets the next developer change the code safely.
• Estimating honestly and flagging risk early when an estimate starts to slip.
• Reading the release notes for the language, framework and platform SDKs the team depends on.

BLS projects employment of software developers, quality assurance analysts and testers combined to grow 10 percent from 2025 to 2035, which it calls much faster than the average for all occupations, with about 106,100 openings projected each year on average. Those figures cover the whole occupation group, not the application developer title alone; BLS does not report application developers separately. The Handbook ties the demand to the continued expansion of software development for artificial intelligence (AI), Internet of Things (IoT), robotics and other automation applications, and expects organizations to increase investment in response to concerns over computer security threats.

Pay is reported for software developers as a whole. In May 2025, BLS counted 1,687,890 software developers and reported a median annual wage of $135,980, with the 10th percentile at $82,460 and the 90th percentile at $214,670. Where an application developer works shapes that number. BLS industry data for the same occupation put the May 2025 median at $101,860 in state government, $122,920 in local government, $104,670 at colleges, universities and professional schools, and $130,840 at insurance carriers. Those are medians for software developers in each industry; BLS does not break out the application developer title within them.

Two changes in 2026 shape the work in front of application developers right now.

Accessibility deadlines for public-sector apps. The Justice Department's interim final rule, effective April 20, 2026, extended the ADA Title II web and mobile compliance date for state and local governments with a total population of 50,000 or more from April 24, 2026 to April 26, 2027. Smaller public entities and special district governments now have until April 26, 2028. The IFR does not alter the substantive requirements adopted in the 2024 rule, which uses WCAG 2.1 Level AA as the technical standard for web content and mobile apps. For developers at a county, a transit authority or a state university, the extra year is time to fix legacy forms, PDFs and mobile screens, not a reason to stop.

AI in the pull request. GitHub's documentation says that starting Oct. 28, 2026, a new Copilot in the cloud experience on GitHub.com and GitHub Mobile is available to users with a paid Copilot plan, letting a developer move between web or mobile and local clients such as VS Code or Copilot CLI within the same Copilot session. Tools like this can shift part of the developer's day from typing code to scoping tasks for an agent and reviewing what it produces. The developer still owns the merge, the test coverage and the security review.

Career growth runs in three directions. One leads deeper into technology: senior developer, then architect or staff engineer. A second builds domain knowledge, such as claims adjudication, student information systems or permitting rules, alongside the code. The third heads into management; BLS notes software developers can advance to project management specialist or computer and information systems manager roles that oversee the development process.

Dear Hiring Manager,

I am applying for the Application Developer position on your Enterprise Applications team. For the past four years I have built and maintained internal business applications at a regional health insurer, and the work your posting describes, modernizing member-facing portals while keeping the claims back end stable, is the work I want to keep doing.

My current stack is C# and .NET on the server, SQL Server for data, and React on the front end. Last year I led the rebuild of our provider directory search. The old page timed out under load and failed a screen-reader review; I rewrote the query layer, added server-side paging, and rebuilt the results view to WCAG 2.1 AA, testing with the accessibility team and two actual screen-reader users before release. Support tickets about the directory dropped noticeably in the months afterward, and the page now passes our automated accessibility checks in CI.

I also care about the parts of the job that do not show up in a demo. I write unit tests with every pull request, I keep the runbook current for the nightly eligibility import I own, and when our security team flagged an outdated logging package, I traced every service that pulled it in and coordinated the upgrade across three teams in a week.

Over the past year I have used an AI coding assistant daily, mostly for test scaffolding and refactoring. My rule is simple: I read every generated line as if a new teammate wrote it, and I reject anything I cannot explain in review.

I would welcome the chance to talk about your portal roadmap and how I could contribute from the first sprint. Thank you for your time and consideration.

Sincerely, Jordan Ellison