We are hiring a Software Engineer II – Backend with 4–6 years of professional experience to strengthen our backend team. This role focuses on building scalable, secure, and reliable backend services. You will design and deliver APIs, authentication systems, and cloud-native applications while ensuring strong observability and engineering best practices. As a mid-level engineer, you will also contribute to architectural decisions and collaborate closely with frontend, DevOps, and other cross-functional teams.
Your Responsibilities & Impact
- Design and develop backend services applying OOP and clean architecture principles.
- Implement secure authentication flows (OAuth2, token refresh mechanisms).
- Work with ORMs (Prisma, SQLAlchemy) to handle database operations.
Build, containerize, and release applications using Docker and CI pipelines (e.g., GitHub Actions). - Enable observability by adding structured logging and distributed tracing for APIs.
- Use AWS services such as S3, RDS, and Secrets Manager for cloud-native development.
- Apply best practices for secure deployments across environments.
- Collaborate effectively with frontend, DevOps, and cross-functional partners to ensure end-to-end delivery.
Requirements
Must-Have Skills
- Strong grasp of OOP and clean architecture concepts.
- Proficiency in Python/Nodejs/ TypeScript for backend development.
- Experience implementing secure authentication (OAuth2, token refresh).
Proficiency with ORMs like Prisma or SQLAlchemy.
Hands-on experience with Docker and CI/CD workflows (e.g., GitHub Actions). - Ability to implement observability practices (logging, tracing).
- Familiar with AWS core services: S3, RDS, Secrets Manager.
- Solid understanding of deployment security standards.
Effective communicator across frontend, DevOps, and cross-functional teams.
Nice-to-Have Skills
- Experience with async task processing (Celery, Cloud Tasks).
- Exposure to AWS Lambda or ECS.
- Familiarity with monitoring tools (Prometheus, Grafana).
- Understanding of Cloud IAM roles and permission boundaries.
Experience implementing circuit breakers and retry strategies.