Backend Engineer

This role is for one of the Weekday's clients

Backend Engineer

event-driven architecture

Requirements

Key Responsibilities

• Design, develop, and maintain backend services and APIs using modern backend frameworks and programming languages.
• Build and enhance event-driven systems using message brokers, queues, and streaming platforms (e.g., Kafka, RabbitMQ, AWS SNS/SQS, or similar).
• Implement asynchronous communication patterns to ensure system scalability, fault tolerance, and decoupling between services.
• Develop and manage consumers, producers, and event handlers while ensuring data consistency and reliability.
• Collaborate with cross-functional teams to translate product requirements into technical solutions.
• Write clean, maintainable, and well-tested code following best engineering practices.
• Participate in system design discussions, code reviews, and architectural decisions.
• Monitor and debug production systems, analyze logs and metrics, and proactively resolve issues.
• Optimize backend performance, latency, and resource utilization.
• Ensure adherence to security, data privacy, and compliance standards.
  

Required Skills & Qualifications

• 1-3 years of professional experience as a Backend Engineer or Software Engineer.
• Strong understanding of event-driven architecture, asynchronous processing, and messaging patterns.
• Hands-on experience with message queues or event streaming platforms such as Kafka, RabbitMQ, ActiveMQ, AWS SNS/SQS, or equivalents.
• Proficiency in at least one backend programming language such as Java, Python, Node.js, or Go.
• Experience building RESTful APIs and working with JSON-based data formats.
• Solid understanding of databases (SQL and/or NoSQL) and data modeling concepts.
• Familiarity with distributed systems concepts like retries, idempotency, eventual consistency, and fault tolerance.
• Basic knowledge of cloud platforms (AWS, GCP, or Azure) and containerization tools is a plus.
  

Nice to Have

• Exposure to microservices architecture.
• Experience with observability tools (logging, monitoring, tracing).
• Understanding of CI/CD pipelines and automated testing