Frequently Asked Questions

(Rarely asked, actually)


What are the goals of this?
In no particular order:
1. To shift your mind and put it into interview mode. 
2. To present a broad overview of the most frequently used topics in software programming that are also popular interview topics.
3. To make you confident of cracking a difficult software engineering interview.
4. To leave you with a sense of having learned something useful in your daily life as a software engineer.

What this is not:
1. It is not a substitute for an Algorithms class. It is intense problem-solving work in an interview-like setting.
2. It is not a get-rich-quick program. It is a pursuit of something worthwhile for your career, life and family.
3. It is not a list of "interview questions". There are innumerable interview questions available online and it's a fool's dream to expect only the ones we have prepared for. It's about trying to bend your mind to think in the right way under interview pressure.
4. We’re not gathered to bash interviewing practices of various companies. We don’t have control over them. We can only try our best to understand them and get through.
5. It is not specific to a programming language.

Why haven't I seen advertisements of this program?
Simply because we don't need to :-). As of this writing, we have been around for 3 years, grown 6x since our first cohort, and not spent a single penny in advertising this program anywhere. Our web presence and love of alumni keeps us going.

Also, we're teacher and engineers. We just focus on what we do best viz. Teaching of Engineering concepts.

Why is this long?
Because it can't get any longer than this, or you will start to have problems with your SO at home :-)

Jokes aside, getting into some of the best places on the planet with a high salary is consistent multi-month work. There are no shortcuts, unless you count being lucky as a strategy. We don't.

Candidates have to work hard and engage actively to make the most of this. If anyone is selling you shorter courses, then they are a glorified recruiting company, who want to collect placement fees by pushing you to work for random-ass companies & waste your life.

What’s the magic?
Sometimes, spending more time with right people, right curriculum and right rigor yields results that are mistaken to be magic.

What are the core beliefs of the founders and instructors? 
0. Interviewing is the first impression you create. Doing well in interviews sets the right tone for an entire career.
1. Getting a job that truly matches your potential is a goal worth chasing, because it has tremendous short-term and long-term benefits. 
2. Software Engineering Interviews are neither exact science, nor standardized tests. But there are some well-understood patterns.  
3. Software Engineering interviews at companies worth their salt are competitive and it pays to prepare well beforehand. 
4. An interviewing mindset is very different from the daily mindset of a programmer.
5. Preparing for interviews in the right way helps one be a better engineer overall. 
6. Anyone can get better when learning with a challenging curriculum, rigorous practice and good instructors. 

How am I going to feel during the coaching?
The coaching is designed to be intense. At different times, you will go through a mixed bag of feelings, both positive and negative. However, if you work diligently with focus, you should feel more confident as the days pass by.

Can I be kicked out?
We won't physically kick you, but if you are disrupting the class, we reserve the right to ask you to leave. Otherwise, we'll support you until you succeed.

What about the coaching is different than me just going off and learning on my own?
1. Practice sessions under interview-like pressure.
2. Learning from each other in a group.
3. Knowing where to focus, from among the myriad choices available online.
4. Reducing your prep-time and making it more methodical.

Which positions is this for?
This coaching, so far, is built for generalist developer roles. Such positions go by different titles e.g. Backend engineer, Server Engineer, Software Engineer, Data engineer, Platform engineer, API developer etc. 

The Curriculum does not cover topic X; why?
The Curriculum is supposed to be generic. It covers the most common topics useful for a generalist developer position. We plan on covering specialized topics at a later time. If you feel that the topic you’re wondering about is pervasive in Software Engineering interviews, but missing in the list, please do let us know!

Is there prior preparation required?
Yes. We will send you a crisp list of preparation once you enroll.

What programming languages do I need to know?
Any one. You should have at least ONE programming language you’re comfortable with; your primary language used in your domain expertise.

Get an invite