Skip to main content

CareerSwift

Backend Developer

San Francisco Office (Remote)fulltimemidAdded today

About this role

CelebriOS is hiring a Backend Developer to design, build, and maintain scalable APIs and data systems that power the company's products. You'll collaborate across engineering and business teams to deliver secure, performant services while balancing reliability and maintainability.

What you'll do

  • Design, build and maintain backend services and REST/GraphQL APIs
  • Develop data models and work with relational or NoSQL databases
  • Integrate internal systems with third-party services
  • Write automated tests, technical documentation and monitor production services
  • Improve application performance, security and reliability
  • Review code and contribute to architecture decisions with cross-functional teams

What they're looking for

  • Backend development (Python, Java, Node.js, Go, or C#)
  • REST, GraphQL or event-driven service design
  • SQL and database design
  • Authentication, authorization and API security
  • Git, automated testing and deployment workflows
  • Cloud platforms (AWS, Azure, or GCP)
  • Containers, message queues and distributed systems
  • CI/CD and infrastructure monitoring

Benefits

  • Health, dental and vision coverage
  • Flexible PTO
  • 401(k)
  • Home-office equipment stipend
  • Annual learning and development budget
Apply on the employer's site

Opens the official application on the employer’s site. No login required.

CareerSwift

CareerSwift builds an AI-powered job search platform with a focus on reliable infrastructure and polished user experiences. The company is hiring DevOps engineers to manage cloud infrastructure and CI/CD pipelines, frontend developers to build React-based interfaces, and QA engineers to ensure product quality through manual and automated testing.

View all jobs at CareerSwift

Likely interview questions

  • Walk us through a backend system you designed—what were the key architectural decisions and tradeoffs?
  • How do you approach database schema design for a new feature, and when would you choose SQL vs. NoSQL?