Back End Engineer

Description:

1. Role: Backend Engineer

1. Years of Experience: 5+ Yrs of experience

Vision for role OR role Overview:  

Im looking for a Senior Backend Engineer to join the team and take ownership of designing, building, and evolving robust backend services. He/she will work across epics, driving technical decisions that balance immediate delivery with long-term scalability and reliability. 

In this role, he/she will be expected to architect solutions using Kotlin, Java , Rust, and Python with frameworks like Spring, Quarkus, and Axum, operate confidently in a cloud-native environment with Kubernetes and Flux/Argo CD, and contribute to observability practices using OpenTelemetry, Prometheus, Grafana, and Pyrra. Beyond coding, he/she will play an active role in improving team processes, raising the quality bar, and mentoring less senior engineers. 

The team operates on a Kanban workflow with a strong culture of continuous improvement. We measure what matters, use flow metrics to drive delivery decisions, and treat process refinement as an engineering discipline in its own right. If he/she is the kind of engineer who gets curious when cycle times spike or throughput drops, he/she will fit right in. 

This is a role for someone who is as comfortable leading an incident response and who treats engineering as a craft and takes pride in leaving systems better than they found them. 

1. Role Responsibilities and skills (be as specific and detailed as possible) 

What are the main responsibilities of this role: 

• Design and implement scalable, production-ready backend services using Kotlin, Java, and Rust with Spring, Quarkus and Axum; 
• Architect systems and services with long-term maintainability and future scaling in mind, applying well-accepted design patterns; 
• Own observability for your domain. Define SLIs, monitor operational data with Grafana, and drive stability and performance improvements; 
• Lead cross-service debugging and incident response, coordinating across teams during critical events; 
• Contribute to CI/CD pipelines (GitHub Actions and Azure DevOps) and cloud-native infrastructure on Kubernetes with Flux CD; 
• Actively identify and propose process improvements, using flow metrics and delivery data to drive decisions; 
• Mentor and support less senior engineers in technical practices, debugging approaches, and quality standards; 
• Identify dependencies, risks, and blockers within your product scope and help adjacent teams understand the impact of your services. 

Core functions and skills MUST require to be successful in this role: How are they used on the job

• Strong proficiency in Kotlin, Java and/or Rust for backend development (experience with Python is a plus);
• Hands-on experience with Spring, Quakus and/or Axum;
• Solid understanding of software architecture principles and distributed systems design.
• Experience with Kubernetes, GitOps workflows (e.g. Flux/Argo CD and GitHub Actions) and/or Azure DevOps.
• Comfortable building and maintaining CI/CD pipelines with GitHub Actions.
• Proficiency in observability tooling, like metrics, dashboards, and alerting (Grafana or equivalent);
• Security-conscious mindset. Familiar with security scanning tools and secure design principles.
• Strong communication skills with the ability to document technical decisions clearly.

Nice to have 

• Experience working in a Kanban environment with exposure to flow metrics (cycle time, throughput, WIP); 
• Familiarity with data-driven process improvement practices; 
• Experience leading architecture reviews; 
• Previous experience mentoring engineers or running knowledge-sharing sessions. 

Platforms/tools/technologies position will work with: 

• Required/ideal previous experience 
• 5+ years of backend engineering experience in production environments; 
• Proven track record designing and delivering distributed systems or microservices at scale; 
• Experience owning a service domain end-to-end from architecture decisions to production monitoring; 
• Hands-on experience with CI/CD pipelines and cloud-native deployments; 
• Demonstrated ability to lead technical discussions, drive cross-team incident response, and mentor peers; 
• Experience working in agile delivery environments with a focus on continuous improvement. 
• Nice to haves 
• Exposure to Kanban workflows and familiarity with flow-based metrics (cycle time, lead time, throughput); 
• Experience with GitOps practices and tools such as Flux/Argo CD; 
• Background in security assessment, secure design, or compliance-related engineering work; 
• Experience with load testing, stress testing, or performance profiling of backend services. 
• How would a day-to-day look like 

A typical day balances delivery, collaboration, and continuous improvement: 

• Morning sync with short Kanban standup with the team to review flow, surface blockers, and align on priorities for the day; 
• Deep work blocks for designing or implementing backend features, reviewing pull requests, or investigating a cross-service issue with a systematic debugging approach; 
• Collaboration touchpoints occasional sessions with business partners or product stakeholders to refine upcoming work, clarify requirements, or validate technical trade-offs; 
• Observability & operations — checking Grafana dashboards, responding to alerts, or following up on an ongoing incident; 
• Process & improvement — contributing to retrospectives (proposing automation improvements, or analyzing delivery metrics to identify bottlenecks in the team's flow); 
• Mentoring by pairing with a less senior engineer, reviewing their work, or running a short knowledge-sharing session. 
• Required technical stack 
• Languages: Kotlin, Java, Rust (Python is a plus); 
• Frameworks: Spring, Quarkus, Axum; 
• Build tools: Gradle, Cargo; 
• Databases: Relational and/or NoSQL (experience with production-grade data modelling); 
• Infrastructure: Kubernetes (K8s); 
• GitOps / Deployment: Flux/Argo CD; 
• Observability: Grafana; 
• Version Control: Git.