TAC HRTAC HR
A scene from a Saudi workplace
HR templates

Job Description: Software Developer

Use this description when you advertise for a developer who builds features and fixes defects on a product team. It is not IT support, which serves staff devices, nor the network administrator, who secures the infrastructure. Copy the text and edit the bracketed fields for your own languages and tools.

Last reviewed
On this page

01When to use the software developer job description, and who uses it

A tech lead or engineering manager writes this description when adding a developer to a team building a product or internal systems: a fintech company, an online shop developing its platform, or a large organisation with an in-house systems team. HR uses it in the contract, and the lead reviews the developer on the quality of what they deliver and product stability, not lines of code.

It is reopened when the team's languages or frameworks change, when operating systems and on-call duty are added to the developer's work, or when their level rises, bringing more independence and responsibility for reviewing others' work.

02The software developer job description

This text sets out the software developer's duties in 5 groups, Analyzing requirements, Writing code, Testing and review, Release and operations and Documentation and team, then the performance indicators, qualifications, skills and working conditions.

[Company name]
Job Description

Job title: Software Developer
Department: Engineering and Product
Reports to: Tech Lead / Head of Engineering
Work location: [location, or partly remote]
Work pattern: [full-time / project contract / remote]
Issue date: [date]      Version: [number]

Job summary
The developer builds the product's software features from requirements to release, writes clear tested code, fixes defects, and takes part in reviewing and documenting the team's work.

Duties and responsibilities
1) Analyzing requirements
   - Understand a feature's requirements with the product manager and ask questions before starting.
   - Estimate the time needed and split the work into small tasks.
   - Propose technical alternatives when requirements clash with capacity.
2) Writing code
   - Build features in readable code that meets the team's standards.
   - Connect the front end to the back end and the databases.
   - Handle bugs reported from production and analyze their causes.
3) Testing and review
   - Write tests for new code before merging it.
   - Review colleagues' merge requests and receive review of their own.
   - Check that a change does not break existing features.
4) Release and operations
   - Take part in releasing versions and watch them after launch.
   - Monitor performance and alerts for the part they built.
5) Documentation and team
   - Document interfaces and design decisions.
   - Share knowledge and help newer team members.

Suggested performance indicators
- Assigned features completed on schedule.
- Code quality from review feedback.
- Defects returned from production in the part they built.
- Teamwork and documentation.

Qualifications and experience
- Bachelor's degree in computer science or software engineering, or equivalent experience.
- At least [__] years developing [type of applications].
- Command of [one or more programming languages] and databases.

Skills required
- Problem solving and logical thinking.
- Writing clean, maintainable code.
- Working with version control.
- Knowledge of interfaces and basic security.
- Clear communication with the team.

Working conditions
- Desk work at a computer for long hours.
- Hours follow the team pattern, possibly with on-call cover for outages: [____].
- Equipment and accounts: [supplied by the company].

Approval
[Approver's name and job title]      Signature: ________      Date: [date]

Job holder acknowledgment
I have read the job description above and confirm that I understand it.
Name: [employee name]      Signature: ________      Date: [date]

03The software developer description, clause by clause

Understanding requirements: questions before code

The developer understands what the product owner needs and asks about edge cases before writing, and estimates the effort. An ambiguous requirement built as written comes back as rework.

Writing code: the team's standards

The developer writes code to the team's standards and tooling and breaks work into small, reviewable changes. The description names the actual languages and frameworks, not a generic list.

Testing and review: no merge without review

The developer writes tests for what they build, reviews colleagues' work and has their own reviewed before merging. A defect caught in review costs less than one a customer finds.

Deployment and operation: by the approved procedure

The developer deploys following the team's procedure, watches logs after release and takes part in resolving incidents. Out-of-hours on-call duty is written if it exists.

Documentation, team and qualifications

The developer documents what they build well enough for the next person to understand, and takes part in team planning. The qualification is a computer science degree or equivalent experience, command of the named tools, and the required level written down.

Approval at the end of the template

The software developer description ends with the approver's name, title, signature and date, so when duties change a new version is issued with a new number instead of handwritten edits.

04Interview questions that test the software developer description

  • 01A requirement says “add an export to the report”. What do you ask before starting? Format, data volume, permissions, empty states and who will use it.
  • 02Reviewing a colleague's work, you find a security flaw. How do you write your comment? Clearly, with evidence and a suggested fix, without being personal, and blocking the merge until it is fixed.
  • 03Production breaks after your release. What are your steps? Roll back or switch off quickly, diagnose from the logs, then fix with a test that prevents a repeat.

05A filled-in example: a software developer at a fintech company in Riyadh

A fintech company in Riyadh hires a mid-level Saudi software developer reporting to the tech lead; this is the developer's first registered job, so the new GOSI system applies. The company named its languages, frameworks and database, wrote that work is hybrid with three office days, and that on-call is one week every two months with compensation under policy. It estimated six hours of overtime a month.

FieldIn the example
CompanyA fintech company with a fifteen-person engineering team
CityRiyadh
Work period9:00 am to 5:00 pm, hybrid office and remote
Start date2026-12-20
NationalitySaudi
Basic salarySAR 13,000.00
Housing allowanceSAR 3,250.00
Transport allowanceSAR 1,300.00
Total monthly salarySAR 17,550.00

These inputs give the following software developer figures, worked out with the same functions as the GOSI calculator, the leave calculator, the overtime calculator and the end-of-service calculator on our site:

CalculationResultBasis
End of probation (90 days)2027-03-19the start date counts as day one
Actual hourly wageSAR 73.13(basic + allowances) ÷ 30 ÷ 8 hours
Overtime hourly rateSAR 100.21actual hourly wage + 50% of the basic hourly wage
Pay for 6 overtime hoursSAR 601.25overtime rate × hours
Employee GOSI share per monthSAR 1,746.88new system, phase-in year 3, employee rate 10.75% of SAR 16,250.00
Employer GOSI share per monthSAR 2,071.8812.75% of the contributory wage
End-of-service award if the contract ends at term after two yearsSAR 17,550.00half a month's wage per year for the first five years, on the total of SAR 17,550.00 to 2028-12-19
Annual leave earned by the end of probation5.18 days21 days per year of service, pro rata

06Hard cases and common mistakes in a software developer description

A deadline that leaves no room for quality

The developer sets out the options plainly, reducing scope or moving the date, and does not ship untested anything that touches money or data.

Old code with no documentation

The developer documents what they learn while working and adds tests before changing it, so nothing that works gets broken.

A request for access to the production database

Access matches the need, for a limited time and under the security policy, because customer data is not a test environment.

A technical disagreement with a colleague

It goes to the lead with arguments and data for a decision, and the decision is recorded.

Common mistake: A long list of languages nobody uses

It drives away suitable candidates and attracts people skilled in what you do not need. Write the tools you actually use.

Common mistake: Measuring by lines or tickets

What matters is the quality of what is delivered, product stability and defects after release.

07Steps to adapt the software developer description to your company

  1. 1

    Write your real tools

    the languages, frameworks and databases your team uses, since they screen applicants first.

  2. 2

    Set the level

    junior, mid or senior, and what independence is expected at each.

  3. 3

    State the working model

    remote, on site or hybrid.

  4. 4

    Detail on-call duty

    is the developer expected to answer production outages out of hours?

08Software developer description checklist before approval

6 items

09Frequently asked questions

  • A developer builds and fixes software; IT support serves users' devices and accounts.

  • Require it if it is core to your product; otherwise ask for the fundamentals and ability to learn.

  • Yes, it affects the applicant's decision. State the on-site days if there are any.

  • By tasks finished on time, review quality, defects returned and teamwork, not by lines of code.

  • Equivalent proven experience is often accepted; say so if you accept it.

  • Write the work model in the description and contract, with communication tools and availability hours.

  • Not in this description; supporting staff devices belongs to the IT support specialist.

  • On the quality of delivered work in review, defects after release, keeping to estimates and contribution to the team.

  • The company's ownership of work product is written into the contract as the regulations allow.

Inside TAC HR

The software developer description in TAC HR

TAC HR lets a tech lead follow developers' attendance and work periods in the attendance service, with each developer's clock-in location set as the company decides, assign development tasks and follow them in the task management service, and run review cycles, goals and periodic follow-ups in the performance service. You will find other templates on the templates page.

This template fills the software developer vacancy in the "New job" («وظيفة جديدة») screen: "Duties and responsibilities" («المهام والمسؤوليات»), then "Requirements" («المتطلبات»), then "Benefits" («المزايا») in the "Job description" («الوصف الوظيفي») tab, and the post reaches your careers page from "Posted jobs" («الوظائف المعلنة»). The software developer salary band is set once in "Job titles" («المسميات الوظيفية»), and the system counts and flags those outside it.

After hiring, the "End of probation" («نهاية فترة التجربة») date shows in the employee list, and the first review in "Performance management" («إدارة الأداء») is the end-of-probation review, so the software developer's indicators written here are measured before confirmation.

  • Recruitment — A recruitment system that ranks applicants with written reasons and turns the accepted one into an employee file
  • Performance and development — A performance review system with weighted criteria and a result whose every point has a known source
  • Employee requests — An employee request system with an approval route per request type and a leave balance checked before approval