Back End Developer

Role 1: SDE – DevOps-Heavy Skillset

4.1 Role Definition

• This is a skillset-driven role, not purely a title-based designation.

• Expected to work across DevOps and development, depending on business needs.

4.2 Core Expectations

• Strong hands-on experience in DevOps and infrastructure setup.

• Ability to:

o Deploy and redeploy services

o Manage stateless and stateful components

o Understand infra terminology and cloud concepts

• Candidate must also have:

o Basic-to-decent coding ability

o Comfort switching between infra and development tasks

4.3 System Understanding

• Candidates must demonstrate:

o High-level understanding of the systems they have worked on

o Knowledge of components, interactions, and data flow

o Awareness of synchronous vs asynchronous communication

• Deep system design problem-solving is not expected.

• However, candidates should clearly explain:

o How their system works

o What happens during key business flows (e.g., payment, booking, order creation)

4.4 Programming Expectations

• Java or Python is acceptable.

• Strong OOP concepts are mandatory.

• C / C++ is not acceptable due to paradigm mismatch.

• Exact language is less important than:

o Coding fundamentals

o Ability to read, write, and reason about code

4.5 Cloud & DevOps Clarifications

• GCP-specific experience is not mandatory.

• Experience on any public cloud is acceptable if concepts are strong.

• Candidates must be able to:

o Understand infra requirements before designing solutions

o Ask clarifying questions (scale, load, availability, cost)

• Directly jumping to VM or infra sizing without understanding requirements is a major rejection reason.

• CI/CD knowledge is an implicit requirement:

o Tool-specific experience (e.g., Jenkins) is good-to-have, not mandatory.