Learn software dev and QA with practical study material.
This page is a starting point for students, junior engineers, and interview prep. It focuses on core concepts, real-world practice, and common questions asked in interviews.
Study by topic, then practice with examples.
A good prep routine is to learn the concept, try it in a small project, and then explain it out loud as if you were answering an interview question.
- HTML, CSS, and JavaScript fundamentals.
- Frontend vs backend vs full-stack roles.
- REST APIs, JSON, request methods, and status codes.
- Git basics, branching, commits, merge conflicts.
- OOP, functions, data structures, and problem solving.
- Debugging, testing, and code review habits.
- Test plan, test case, test suite, and test strategy.
- Smoke, sanity, regression, functional, and exploratory testing.
- Bug lifecycle, severity vs priority, and defect reporting.
- Manual testing vs automation testing.
- Test data, environments, and release readiness.
- Basic performance, accessibility, and API testing concepts.
Common questions for software and QA interviews.
Use these as practice prompts. The goal is to answer clearly, with a simple example, and without overcomplicating the explanation.
- What is the difference between frontend and backend development?
- What is REST and why is it used?
- Explain the difference between GET, POST, PUT, and DELETE.
- What is Git and why is branching useful?
- What is the difference between synchronous and asynchronous code?
- How do you debug a broken feature?
- What is the purpose of unit testing?
- What is the difference between a framework and a library?
- What is the difference between QA and testing?
- What is the difference between smoke and regression testing?
- How do you write a good test case?
- What is severity and what is priority?
- What is the defect life cycle?
- When would you choose manual testing over automation?
- What makes a test automation suite maintainable?
- How do you report a bug clearly?
How should I answer in interviews?
Use a simple structure: define the term, explain why it matters, then give one short example from a project or exercise.
What should I study first?
Start with HTML, CSS, JavaScript, Git, APIs, then move into testing basics, defect handling, and simple automation concepts.
How can I practise QA questions?
Try writing one sample test case for a login form, one defect report, and one regression checklist for a small feature.
A simple study pattern you can reuse.
Here is a compact way to turn theory into interview-ready answers and practical notes.
Want this turned into a full learning library?
I can expand this into separate sections for HTML, CSS, JavaScript, manual QA, automation, API testing, and interview practice cards.