Software engineer

What does a software engineer do?

A software engineer designs, builds, tests and maintains software.

The software may be a web app, a mobile app, an internal tool or a service that other systems call through an API.

In Singapore, software engineers work in banks, government agencies and their vendors, startups, logistics firms and product companies. They usually sit in an engineering or technology team, often in a small squad that owns one product or service.

You work with product managers, designers, QA engineers, data teams and operations staff. More senior engineers also talk with the business stakeholders who set the requirements.

What the work involves

• Read user stories and talk with stakeholders to understand what the software must do.
• Write code and unit tests, then submit changes for review through Git.
• Review teammates' code for bugs and security weaknesses.
• Join design discussions and sketch how a new feature fits into the existing system.
• Fix defects, support releases and keep an eye on the pipeline that builds and tests each change.

Pay in Singapore

Back to top

Skills a software engineer needs

Back to top

Software engineer job description

We are hiring a software engineer to build and maintain applications for users in Singapore.

You will turn requirements into tested code, review teammates' work and help release changes safely. You will join an agile team with product, design and QA colleagues.

Responsibilities

• Analyse user and business requirements and write them up as clear tasks.
• Design and write code for new features and improvements to existing applications.
• Write unit, integration and system tests, and meet the team's test coverage goals.
• Review teammates' code for quality, readability and security weaknesses.
• Follow secure coding standards to avoid common vulnerabilities.
• Keep code under version control and manage branches and releases.
• Take part in design reviews and help prepare prototypes or diagrams.
• Investigate and fix defects reported by users or found in monitoring.
• Support releases through the CI/CD pipeline and help resolve production issues.
• Record measures such as code quality and size, and share them with the team.

Requirements

• Diploma or degree in computer science, software engineering, information technology or a related field. Bootcamp graduates and career switchers with a strong portfolio are also hired.
• Typically 0 to 2 years of experience for an entry role and 2 to 5 years for a mid-level role.
• Working skill in at least one language such as Python, Java, JavaScript or TypeScript, plus SQL.
• Comfort with Git, REST APIs, Docker and a CI/CD tool.
• Basic knowledge of a cloud platform such as AWS, Azure or Google Cloud, and of secure coding practice.

Back to top

Software engineer career path

The SkillsFuture Skills Framework lists two steps for this job: Associate Software Engineer, then Software Engineer.

The later steps below follow common job titles in Singapore.

1. Associate software engineer

   Entry · SkillsFuture title

   You write and test code under guidance, support updates to existing applications and learn the team's standards for design, testing and secure coding.

2. Software engineer

   Mid · SkillsFuture title

   You own features from requirements to release, join design reviews, handle integration work and suggest improvements to existing applications.

3. Senior software engineer

   Senior

   You lead the design of larger features, review much of the team's code and coach newer engineers. You also weigh trade-offs with product and business teams.

4. Tech lead or engineering manager

   Lead

   You set technical direction for a team or run the team itself. The work shifts towards planning, hiring, delivery and cross-team decisions.

Steps marked "SkillsFuture title" follow the career pathway in the SkillsFuture Skills Framework. The others are titles commonly used in Singapore.

Related jobs and their pay

Back to top

Software engineer interview questions

We wrote these questions from the skills this job needs. They are not an official question bank.

1. How would you choose between a hash map and a sorted array for looking up customer records?

   What a good answer covers

   • Hash map lookups are fast on average, while a sorted array with binary search takes logarithmic time.
   • A sorted array supports ordered iteration and range queries without extra work.
   • Hash maps use more memory and can slow down when many keys collide.
   • The right choice depends on data size, the read and write mix, and the queries needed.

2. Design a REST API for booking appointments at a clinic.

   What a good answer covers

   • Names resources clearly, such as patients, slots and bookings, with sensible endpoints.
   • Uses the right HTTP methods and status codes, and a consistent error format.
   • Prevents double booking, for example with idempotency keys or database constraints.
   • Covers authentication, pagination and how to version the API.

3. A SQL query on a large orders table has become slow. How do you find the cause?

   What a good answer covers

   • Reads the query plan with EXPLAIN before changing anything.
   • Checks whether the filter and join columns have suitable indexes.
   • Selects only the columns needed and removes unnecessary joins.
   • Tests the fix on a copy of the data and measures the result.

4. What is the difference between a Docker image and a container, and why do teams use them?

   What a good answer covers

   • An image is a read-only package of code and dependencies. A container is a running instance of it.
   • Containers behave the same on a laptop, in testing and in production.
   • Mentions small images, a Dockerfile kept in version control and secrets kept out of images.

5. Walk me through what happens to a code change from your laptop to production in a CI/CD pipeline.

   What a good answer covers

   • Describes a branch, a pull request and review before merge.
   • The pipeline builds the code, runs tests and checks, and produces an artefact.
   • Deployment goes to a test environment first, then production.
   • Mentions rollback, approvals where needed and monitoring after release.

6. How do you protect a web app from SQL injection and cross-site scripting?

   What a good answer covers

   • Uses parameterised queries instead of building SQL by joining user input.
   • Encodes output and validates input on the server.
   • Sets security headers and a content security policy.
   • Names the OWASP Top 10 as a checklist and uses dependency scanning.

7. Design a service that sends delivery status notifications to a large number of users.

   What a good answer covers

   • Puts events on a queue so the sender is separate from the order system.
   • Uses workers that scale and retry failed sends with backoff.
   • Avoids duplicate messages with idempotent handling.
   • Respects the limits of SMS or push providers, and tracks failures with logs and alerts.

8. What do you look for when you review a pull request?

   What a good answer covers

   • Checks that the change does what the ticket asks and is covered by tests.
   • Looks at readability, naming and simple design before style details.
   • Spots security issues such as unchecked input or leaked secrets.
   • Gives specific, polite comments and separates must-fix items from suggestions.

9. How do you use an AI coding assistant such as Copilot or Cursor, and how do you check what it writes?

   What a good answer covers

   • Uses it for drafts, boilerplate and tests, and keeps responsibility for the result.
   • Reads every suggestion and runs the tests before committing.
   • Watches for invented functions, outdated libraries and insecure patterns.
   • Keeps confidential code and customer data out of tools the company has not approved.

1. At 6pm on a Friday, payments start failing for some users after your release. What do you do?

   What a good answer covers

   • Confirms the scope and impact using logs and monitoring.
   • Rolls back or turns off the feature first, then investigates.
   • Tells the team, the product owner and support in clear updates.
   • Finds the root cause and writes a short post-incident review with follow-up actions.

2. A product manager wants a feature in two weeks, but you estimate five. How do you respond?

   What a good answer covers

   • Explains the estimate by breaking the work into parts.
   • Asks which parts matter most and offers a smaller first release.
   • Names the risks of cutting tests or review.
   • Agrees a plan in writing and flags early if it slips.

3. You inherit a large module that has no tests and you must add a feature. How do you start?

   What a good answer covers

   • Reads the code and talks to people who know its history.
   • Adds tests around current behaviour before changing it.
   • Makes small changes that can be reviewed and released separately.
   • Refactors only where it helps the new feature.

1. Tell me about a time you disagreed with a teammate on a technical approach.

   What a good answer covers

   • Describes the situation and both options fairly.
   • Shows how the two of you compared them with data, a prototype or a senior opinion.
   • Explains the outcome and what you learned, even if your idea was not chosen.

2. Describe a bug you introduced and what you changed afterwards.

   What a good answer covers

   • Owns the mistake and does not blame others.
   • Explains how it was found and fixed.
   • Names a lasting change, such as a new test, a check in the pipeline or a review habit.

1. Your team is adding a sign-up form that collects NRIC numbers and mobile numbers. What do you consider under the Personal Data Protection Act (PDPA)?

   What a good answer covers

   • Asks whether the data is needed at all and collects only what the purpose requires.
   • Gets consent and states the purpose clearly, unless an exception applies.
   • Stores the data securely, limits who can see it and avoids logging it in plain text.
   • Plans for access and correction requests and for deleting data when it is no longer needed.
   • Checks with the company's data protection officer on the rules that apply to NRIC numbers.

2. You join a bank's technology team in Singapore. How would your habits change given the expectations of the Monetary Authority of Singapore (MAS)?

   What a good answer covers

   • Expects tighter change control, with approvals, audit trails and separation of duties.
   • Treats security testing, access control and logging as part of delivery.
   • Knows MAS sets technology risk expectations for financial institutions and asks the team which ones apply.
   • Plans for resilience, such as backups, failover and incident reporting.

Common questions about a software engineer job

Sources