KASHII UPDATEZ Everyday Student Requirements & Python Coding Tutorials by Python Kashi
S #2596
Applications open Full-Time Job

cloud security engineer

CRED

  • Bengaluru, India
  • Not disclosed
  • 2–6 Years
  • Posted Yesterday
HR
Recruiter contact
Recruiter / hiring contact
No public email in this post. Use a source-linked contact instead.

About the role

What is CRED?

CRED is an exclusive community for India’s most trustworthy and CREDitworthy individuals, where the members are rewarded for good financial behavior. CRED was born out of a need to bring back the focus on a long lost virtue, one of trust, the idea being to create a community centered around this virtue. a community that constantly strives to become more virtuous in this regard till they finally scale their behavior to create a utopia where being trustworthy is the norm and not the exception. to build a community like this requires a community of its own; a community special in its own way, working towards making this vision come true

here’s a thought experiment: what do you get when you put a group of incredibly passionate and driven people and entrust them with the complete freedom to chase down their goals in a completely uninhibited manner? answer: you get something close to what we have at CRED; CRED just has it better

what you will do:

  • work across a diverse information security domain, with a strong focus on cloud, infrastructure, and data security
  • identify security issues (internal and external), work with stakeholders on mitigation, and design/implement solutions for complex security problems in aws-based systems
  • own and continuously improve the cloud security posture management (cspm) program aligned with standards like nist 800-53 and iso 27001
  • own the cloud workload protection program, including alert investigation and triage
  • drive the data security charter, including data classification, masking, and securing large-scale data stores
  • automate infrastructure security and build security tooling to reduce manual effort
  • conduct security design, infrastructure, and architecture reviews
  • build, operate, and maintain cloud security platforms to enhance prevention, detection, and response
  • translate product requirements into threat models and identify security risks
  • build in-house security frameworks to strengthen security culture across tech teams
  • enable compliance across teams (pci dss, iso 27001, dpdpa) and promote best practices
  • drive security awareness and engineering maturity across the organisation

you should apply if you have:

  • 2–6 years of experience in information security Solid fundamentals on computer networks, operating systems (linux), containers and secure cloud architecture
  • strong programming skills in python, go, or bash
  • solid understanding of cloud security with hands-on experience in aws / gcp / azure
  • experience building and automating custom security tools
  • understanding of microservices, ci/cd pipelines, containers, and securing containerised workloads
  • strong grasp of core security principles like least privilege, defence-in-depth, and zero trust
  • a data-driven mindset with the ability to influence stakeholders
  • security projects on github or technical blogs
  • strong communication skills and the ability to be a go-to security partner for engineers and product teams
  • a proactive approach to staying updated on security threats, breaches, tools, and research
  • basic understanding of llms, mcp, and ai agents and Interest in building ai-driven security workflows.
  • familiarity with vulnerability management, patching cycles, and cvss

how is life at CRED?

working at CRED would instantly make you realize one thing: you are working with the best talent around you, not just in the role you occupy but everywhere you go. talk to someone around you; most likely you will be talking to a singer, stand-up comic, artist, writer, an athlete, or maybe a magician. at CRED, people always have talent up their sleeves. with the right company, even conversations can be rejuvenating. at CRED, we guarantee a good company.

hard truths: pushing oneself comes with the role, and we realize pushing oneself is hard work. which is why CRED is in the continuous process of building an environment that helps the team rejuvenate, including but not limited to a stacked, in-house pantry, with lunch and dinner provided for all the team members, paid sick leaves, and comprehensive health insurance.

to make things smoother and to make sure you spend time and energy only on the most important things, CRED strives to make every process transparent: there are no work timings because we do not believe in archaic methods of calculating productivity; your work should speak for you. there are no job designations because you will be expected to hold down roles that cannot be described in one word. since trust is a major virtue in the community we have built, we make it a point to highlight it in the community behind CRED: all our employees get their salaries before their joining date. a show of trust that speaks volumes because of the skin in the game.

there are many more such eccentricities that make CRED what it is, but that’s for one to discover. If you feel at home reading this, get in touch.

Eligibility & process

Who can apply

See the job description for eligibility.

Skills & stack

Python Microservices AWS Azure GCP CI/CD Git Linux

Selection process

  1. As described in the employer's job posting.

Prep kit

20 resources
Study material 4
Company-specific guides 4
Likely coding questions 4
Round-wise strategy 4
Round 1: Online Assessment (OA) Aptitude, Quantitative Logic & 2 Coding Problems Focus on accuracy and speed. Practice arrays, strings, and standard arithmetic puzzles.
Round 2: Technical Interview 1 Core Tech Stack (Python, Microservices, AWS, Azure, GCP, CI/CD, Git, Linux) & Live Code Tracing Explain your thought process aloud. Analyze time & space complexities before coding.
Round 3: System Design & Problem Solving Database Schemas, APIs & Architecture Basics Clarify edge cases, diagram schemas cleanly, and discuss scalability trade-offs.
Round 4: HR & Cultural Fit Discussion CRED Core Values, Learning Agility & Offer Terms Demonstrate passion, strong communication, and readiness for full-time collaboration.
Technical questions 5
Explain OOP (Object-Oriented Programming) principles with real-world examples in Python. Answer
Model answer: 1. Encapsulation (data hiding via private fields/getters). 2. Abstraction (hiding implementation complexity). 3. Inheritance (code reusability). 4. Polymorphism (method overriding/overloading).
What is the time and space complexity of QuickSort vs MergeSort? Answer
Model answer: QuickSort: Average O(N log N) time, O(log N) space. Worst O(N^2). MergeSort: Guaranteed O(N log N) time, but requires O(N) auxiliary space.
Explain the difference between SQL Indexing (B-Tree vs Hash) and when not to use an index. Answer
Model answer: Indexes speed up SELECT queries via B-Trees. However, they slow down INSERT, UPDATE, and DELETE operations because indexes must be updated on disk. Avoid on low-cardinality columns (e.g., boolean flags).
What happens under the hood when you enter a URL in a browser? Answer
Model answer: 1. DNS lookup (resolves IP). 2. TCP 3-way handshake (SYN, SYN-ACK, ACK). 3. TLS negotiation for HTTPS. 4. HTTP GET request sent. 5. Server responds with HTML/CSS/JS. 6. Browser renders DOM & CSSOM tree.
What is the difference between REST and GraphQL APIs? Answer
Model answer: REST uses multiple fixed endpoints with possible over/under-fetching. GraphQL uses a single endpoint allowing clients to query exact fields in a single request.
Behavioural & HR questions 3
Why do you want to join CRED as a cloud security engineer?
Highlight CRED's market reputation, recent tech innovations, and how your skills in Python directly solve their team's objectives.
Describe a challenging bug or academic project roadblock and how you resolved it.
Use the STAR method: Situation (project context), Task (what needed solving), Action (specific tools/logic applied), Result (quantifiable positive outcome).
How do you handle strict deadlines or sudden scope changes?
Explain your prioritization strategy, proactive communication with mentors/peers, and agile mindset.
CRED Not disclosed
Recruiter Resume Apply
Chat Chat with Kashii