Job description

A leading organization is seeking two Backend Software Engineers to support an API enhancement initiative focused on improving access to structured information through document-based outputs. The engineers will build backend capabilities that transform structured data into encounter-style PDF documents, making relevant information easier for users to access and review. The position requires hands-on backend development experience with Python, GCP, APIs, SQL, and AI technologies.

Responsibilities

• Develop and enhance backend services using Python.
• Build and improve APIs that support document generation and data access.
• Create backend functionality that converts structured data into usable PDF documents.
• Work with structured datasets using SQL.
• Develop solutions within a GCP environment.
• Apply AI capabilities where appropriate to support project requirements.
• Support API enhancements that improve access to relevant information.
• Build reliable backend components for document-viewing workflows.

Required experience and skills

• Strong backend software engineering experience.
• Hands-on Python development skills.
• Experience developing and integrating APIs.
• Experience working with GCP.
• Proficiency with SQL and structured data.
• Experience with AI technologies.
• Ability to develop backend solutions that transform structured data into document-based outputs.

FAQs

1. What does a Backend Software Engineer do?

A Backend Software Engineer designs, develops, and maintains the server-side components that power applications and services. The role typically involves business logic, APIs, database interactions, integrations, performance optimization, and production support.

2. What technologies are commonly used in backend software engineering?

Backend engineers may work with languages such as Python, Java, JavaScript/Node.js, Go, or C#, depending on the technology stack. They commonly use REST or GraphQL APIs, relational or NoSQL databases, cloud platforms, version control, automated testing, and CI/CD tools.

3. How does a Backend Software Engineer design and maintain APIs?

Backend engineers define API endpoints, request and response structures, authentication, validation, error handling, and integration patterns. They also maintain API documentation and monitor performance and reliability as services evolve.

4. What database skills are important for a Backend Software Engineer?

Backend engineers should understand relational databases such as PostgreSQL or MySQL, including schema design, SQL queries, indexing, transactions, and performance optimization. Depending on the application, experience with NoSQL databases such as MongoDB, Redis, or DynamoDB may also be required.

5. How does a Backend Software Engineer handle application performance?

Performance work can include optimizing database queries, improving API response times, implementing caching, managing resource usage, and identifying bottlenecks through monitoring and profiling. Engineers use application metrics and logs to diagnose performance issues and validate improvements.

6. What is involved in testing backend applications?

Backend testing typically includes unit tests, integration tests, API tests, and regression testing. Engineers validate business logic, database interactions, error handling, and service integrations before changes reach production.

7. How does a Backend Software Engineer work with frontend developers?

Backend engineers collaborate with frontend teams to define API contracts, data structures, authentication flows, and error-handling behavior. They ensure backend services provide reliable and consistent data that supports the application's user-facing functionality.

8. What responsibilities can a Backend Software Engineer have in production environments?

Production responsibilities may include monitoring services, investigating application errors, resolving incidents, reviewing logs, and deploying fixes. Engineers may also contribute to reliability improvements, observability, capacity planning, and operational documentation.