Skip to main content

Documentation Index

Fetch the complete documentation index at: https://resources.devweekends.com/llms.txt

Use this file to discover all available pages before exploring further.

Reading about someone else’s interview experience is the closest thing to a cheat code in job preparation. It does not give you the answers, but it tells you what kind of questions to expect, how the process is structured, and where candidates commonly stumble. Every experience below is from a real candidate and structured for maximum usefulness.

​
How to Use These Experiences

  • Identify patterns across companies. Most interviews follow similar structures (screening, technical rounds, behavioral, system design), but the emphasis varies. Knowing where a company places its weight helps you allocate prep time.
  • Note the question types, not just the specific questions. If a company asks “What is the purpose of a SPA in React?” the pattern is “conceptual web fundamentals.” Prepare the category, not just the answer.
  • Pay attention to the process timeline. Knowing that a company has 3 rounds over 2 weeks versus 5 rounds over 6 weeks helps you plan your schedule and manage parallel applications.

​
Arham Soft — Fresh Software Engineer

Process overview: Multi-stage process testing breadth of fundamentals before depth in technical rounds.
  • Initial screening test (MCQs, 40 questions; aim for 27+ correct to advance)
    • Topics covered: Web basics, React SPA purpose and architecture, Java platform independence (bytecode and JVM), SQL queries (range filtering via BETWEEN), control flow structures, and array manipulation
    • Tip: This is a breadth test. They are checking whether you have exposure across the stack, not deep expertise in any one area. Review fundamentals across web, SQL, and one backend language before this round.
  • Essay writing (choose 1 of 5 topics)
    • This round evaluates communication skills and the ability to articulate technical concepts clearly. Choose the topic you can write about with the most specificity and real examples — vague essays score poorly.
  • Technical rounds (DSA, OOP, Database, and project discussion)
    • Expect to write code on a whiteboard or shared editor for DSA questions. OOP questions focus on principles and their practical application, not just definitions. The project discussion goes deep — be ready to explain architecture decisions, trade-offs you made, and what you would do differently.

​
How to Submit Your Experience

Structured interview experiences are the most valuable contribution you can make to this community. When submitting, include:
  1. Company name and role (e.g., “Arham Soft — Fresh SWE”)
  2. Date of interview (month and year is sufficient)
  3. Process stages (how many rounds, what type, how long)
  4. Questions or topics covered in each round (be as specific as you can without violating any NDA)
  5. Difficulty level and your honest assessment of what you wish you had prepared better
  6. Outcome (optional but helpful for calibrating difficulty)
Want to submit your experience? Open a PR to this page or share details with the DevWeekends team. Even partial experiences (e.g., “I only made it through round 2”) are valuable — they tell others what to expect at each stage.
After every interview you go through, spend 15 minutes writing down the questions and your impressions while they are fresh. This helps your own preparation for future interviews and creates a contribution you can share with the community.