Software Engineer

Software EngineerL3Medium

The Software Engineer L3 interview at CRED is designed to assess a candidate's foundational knowledge in computer science, problem-solving abilities, and cultural fit within the company. It typically involves a mix of technical and behavioral rounds to evaluate a candidate's potential to contribute to CRED's innovative and fast-paced environment.

Rounds·3

Timeline·~7d

Experience·1 - 3 yrs

Comp band·US$100000 - US$150000

Interview time·120 min

Evaluation

What they measure.

  • Problem-solving skills
  • Algorithmic thinking
  • Data structures knowledge
  • Coding proficiency
  • System design fundamentals
  • Communication skills
  • Teamwork and collaboration
  • Adaptability and learning agility
  • Cultural alignment with CRED's values

Preparation

How to prepare.

Tips

  1. Brush up on fundamental data structures and algorithms (Arrays, Linked Lists, Trees, Graphs, Hash Tables, Sorting, Searching).
  2. Practice coding problems on platforms like LeetCode, HackerRank, or GeeksforGeeks, focusing on medium-difficulty problems.
  3. Understand core computer science concepts like operating systems, databases, and networking.
  4. Prepare for behavioral questions by reflecting on your past experiences using the STAR method (Situation, Task, Action, Result).
  5. Research CRED's products, mission, values, and recent news.
  6. Be ready to discuss your resume and projects in detail.
  7. Prepare questions to ask the interviewer about the role, team, and company culture.

Study plan

Fig · Study plan — 05 phases

01 / 05
01

Phase 01 of 05

Data Structures

Weeks 1-2: Data Structures & Operations. Practice problems.

Week 1-2: Focus on Data Structures (Arrays, Linked Lists, Stacks, Queues, Trees, Graphs, Hash Maps) and their common operations and time complexities. Practice problems related to each data structure.

Questions

Commonly asked.

  • Write a function to reverse a linked list.
  • Given an array of integers, find the two numbers that add up to a specific target.
  • Explain the difference between a process and a thread.
  • Describe a situation where you had to handle a conflict within a team.
  • How would you design a URL shortener?
  • What are the ACID properties of a database transaction?
  • Tell me about a time you failed and what you learned from it.
  • How do you stay updated with new technologies?

Locations

Regional differences.

Fig · Regions — 02 locations

01 / 02

Location

Bangalore

Interview focus

Adaptability to local market trendsUnderstanding of regional user behavior

Common questions

  • Discuss a challenging bug you fixed in a production environment.
  • How do you approach learning a new technology?
  • Describe a time you had to work with a difficult team member.

Tips

  • Research CRED's presence and impact in the specific region.
  • Be prepared to discuss how your skills align with local business needs.

Rounds

Round-by-round.

Expand a step for evaluation criteria, sample questions, and prep notes.

Med

Technical Interview (Coding) · 45 min · Software Engineer / Senior Software Engineer

This round focuses on assessing your fundamental programming skills and problem-solving abilities. You will be asked to solve one or two coding problems, typically involving data structures and algorithms. The interviewer will evaluate your approach to solving the problem, the efficiency of your solution, and the quality of your code. You'll be expected to explain your thought process and discuss trade-offs.

What they look for

Logical thinkingAlgorithmic proficiencyClean and efficient codeAbility to communicate technical ideas

Evaluation

  • Correctness of the solution
  • Efficiency of the solution (time and space complexity)
  • Code clarity and readability
  • Problem-solving approach
  • Ability to handle edge cases

Sample questions

  • Given a string, find the first non-repeating character.

    StringHash Map
  • Implement a function to check if a binary tree is a Binary Search Tree (BST).

    TreeRecursionBST

Prep for this round

  1. 01Practice coding on a whiteboard or a simple text editor.
  2. 02Think out loud and explain your approach before coding.
  3. 03Consider edge cases and test your code mentally.
  4. 04Be prepared to discuss the time and space complexity of your solution.

Common rejection reasons

  • ×Inability to articulate thought process clearly
  • ×Poor coding practices (e.g., unreadable code, lack of error handling)
  • ×Incorrect or inefficient solutions to coding problems

DSA

Coding questions at CRED.

Frequently reported on CRED loops

Other guides

More at CRED.