RMOTR school offers 4-month online Python web development and data science bootcamps. Students interact with teachers, mentors, and classmates remotely and are equipped with the skills to land a new role in tech with the help of RMOTR career advisors. Trainings include a clear and curated path for the curriculum, scheduled live sessions, and mentor support every week to keep students accountable. Students also participate in creating well-thought, real-life projects to build their own portfolio, and much more.
Prospective students can try full-featured access to a course for free during the whole first week of training (which includes 2 live classes). Students can unsubscribe at any time, no questions asked.
Recent RMOTR Reviews: Rating 4.94
Recent RMOTR News
- MySQL, Data Science, MongoDB, Git, R, Python, SQL, Hadoop, Machine Learning, Spark, Linux, Virtualization, Data Structures, Algorithms
OnlinePart Time6 Hours/week
A fully remote course, but with two LIVE classes per week + unlimited mentorship. Learn to use Python to automate every mundane task and perform data analysis with the most popular tools and libraries: Pandas, Matplotlib, Bokeh, Scrapy, etc. It's a 3-month course, led by a real instructor, meeting two times per week in live classes to help keep yourself accountable. Our course is highly practical, you won't learn just Python, but to interact with the whole environment: git, github, test driven developments, deployments, code reviews, etc.
- Start Date
- Rolling Start Date
- Class size
- TRY FOR FREE
- Monthly payments available.
- Tuition Plans
- Monthly: $349. Bundle (4 months): $1099.
- Minimum Skill Level
- Basic python skills
- Prep Work
- All the prep work is provided by us.
- Placement Test
- MySQL, MongoDB, Git, Python, Django, SQL, CSS, Linux, Data Structures, Algorithms
OnlinePart Time6 Hours/week5 Weeks
Our "Web Development with Django" course is great for Python developers that are willing to get a job as Web developers or want to create their our products/startups. You will start with a quick overview of all the Django concepts, and jump directly into the most advanced features of the framework. We dedicate a big part of the course to teach you about HTTP concepts, MVC frameworks and RESTful architectures. You will be writing an entire RESTful API using the well know "django-rest-framework" library. The program aims to teach you things that you won't find in most of the common resources, like: good practices based on experience, conventions, most used tools, building reusable Django apps and uploading them to pypi, deploying your Django app or API, etc.
- Start Date
- None scheduled
- Class size
- TRY FOR FREE
- Monthly: $349. Pay as you go.
- Tuition Plans
- Monthly: $349. Bundle (4 months): $1099.
- Minimum Skill Level
- Basic python skills
- Prep Work
- We provide the required prep work.
- Placement Test
134 reviews sorted by:
- Only Applicants, Students, and Graduates are permitted to leave reviews on Course Report.
- Post clear, valuable, and honest information that will be useful and informative to future coding bootcampers. Think about what your bootcamp excelled at and what might have been better.
- Be nice to others; don't attack others.
- Use good grammar and check your spelling.
- Don't post reviews on behalf of other students or impersonate any person, or falsely state or otherwise misrepresent your affiliation with a person or entity.
- Don't spam or post fake reviews intended to boost or lower ratings.
- Don't post or link to content that is sexually explicit.
- Don't post or link to content that is abusive or hateful or threatens or harasses others.
- Please do not submit duplicate or multiple reviews. These will be deleted. Email moderators to revise a review or click the link in the email you receive when submitting a review.
- Please note that we reserve the right to review and remove commentary that violates our policies.
Click here to log in or sign up and continue.
I really liked the variety of coding projects, and they way how they were structured to tackle specific topics covered in the class.
There was only one real class a week. When taking a class, I mean to be taught by the teachers. During that class a lot of topics were explained, and sometimes it was hard to pay attention and keep the pace during the two hours of class. I would maybe split the class into a few days, and mix them with projects to practice the covered concepts.
I'm more than happy with the overall experience.
The projects helped a lot with retaining what was covered in the lessons. I think that having an instructor leading a class and explaining each topic is a wonderful way of learning.
There were lots of projects, maybe a bit too many. But I would have loved to have more time to tackle them all.
I was a bit frustrated with other online platforms that I used in the past to learn programming, but with RMOTR I now believe again that it's something totally doable.
Working in groups with other people remotly was great. I'm from India, and don't have much chances to learn in my local city. RMOTR gave me the chance to share a classroom with folk from the main cities in the US, and that's an incredible opportunity.
The only thing is that there is not enough time to complete the pre-readings if the individual taking the course is a full time employee somewhere, so it's very important to specify that this course if for people who can work on this full time. Other than that it's great.
Working in groups with other people from all around the world, from home, was simply amazing.
I didn't feel like there was enough time to complete most of the assignments, but that's probably associated to my bussy weekly schedule. It's know that it's an intensive course, so I should have reserved more time to commit in the extra readings/coding.
I think it's a great approach. If anything, I would say that having a little more time for readings, and having supplementary material for subjects that are not central to the course but are necessary for projects would help (e.g. I would have worked through a SQL tutorial before the last week had I known it would be needed.) Also as I mentioned on the call, I think materials on debugging, linting and all of that fun stuff would be a great help. Some of this I learned from other students, but that is hit or miss.
I want to enroll for the more advanced course as well. This methodology definitely made my learn a lot in a short time.
The greatest part is having live class and coding sessions.
I didn't feel like the coding exercises in the homework assignments on the learn site were very helpful. I'm not sure what would make them better.
I liked the process a lot. Knowing that we had an opportunity to ask questions in class about the reading topics, and knowing that we would be using the concepts we were reading and discussing for our coding sessions provided good motivation to prepare, and the class was structured so we could prepare well. The readings were very helpful, but they were hard to get done. I take a while to process what I read, and it would have been helpful if the readings had been available earlier. I think if they had been posted a full week before the class sessions, I would have been ready to ask more questions in class.
Doing group programming live on cloud9 was fantastic. I never thought attending an experience like this from the confort of my home, sharing the class with folks from all around the globe.
Sometimes the suggested reading was too much for me to do. But that's probably my personal issue.
I really liked working in teams with mentor help. It might have been good to have the whole group read the project assignment before hand so we could just jump right in to coding when the time starts.
It was a great experience overall, but maybe there could be a structure that works more easily with full-time workers. For example, readings and class during the week with an easy project. Then two intense projects during the weekend.
Group work was a bit hard for me sometimes. I am guilty of this as well - especially during the work week real life commitments took away how much I or my teammates could contribute.
Aside from that, I would totally recommend this methodology. Kept me accountable the whole month.
It was great that professors are super kind and helpful.
I feel like a lot of material was just thrown at us. i.e. I did not know how to use the time module and I needed it for the decorator problem. However, we never touched on how to implement those modules. It would be nice to see the professors code more, and see how they solve similar problems. Anyway, I understand that this is how real life works, and getting prepared for that it's also a good experience.
Interesting projects that exposed me to a variety of topics in python.
Sometimes the projects involved libraries that were confusing, and so instead of getting to spending most of the time learning about the topic that we were supposed to be learning, we had to waste a lot of time struggling to understand the other library (e.g. in the decorator project, dealing with logger. Or in the mix-in project, dealing with argparse.). I would suggest that when there is an extra library being used in a project, there should be some practice with it in the learn platform ahead of time, so we can get used to the syntax.
Also, I think having more experience building a project from scratch is important. Having the interface and tests already created is probably 90% of a typical project. And overall project structure (how to structure packages and modules) is something that I don't know much about and wish I had had the chance to practice in this course.
Another issue was when the tests had errors in them that made it impossible to pass the tests. That made the coding sessions frustrating, because we were not just debugging our own code but the tests also.
Finally, I thought there was a big difference in what was taught during the lessons on Wednesday and what we were expected to do in the coding sessions. I found that most of the Wednesday sessions didn't teach me much that I didn't already know from the assigned reading, learn platform, or previous experience. But then when we got to the actual coding session it was far more difficult than what was taught. I think it would be better to assume/require people have done the reading and then teach the class accordingly so that we learn more in the teaching sessions.
That said, I still think it's a great course and methodology. I would totally recommend it.
I loved the intensity and collaborating with other course takers.
I truly enjoyed my experience with the RMOTR guys, I have just two things I'd want to have shared with me if I were a RMOTR owner: 1. I felt a few times that mentors were pushy / overbearing in their 'help' during coding sessions. I had been cut off mid-thought several times while trying to describe my problem + thought processes. Once the mentor saw the issue, I felt flooded with 'xyz' on what to do; most often this left me more confused on what the code was doing and why. 2. I posted in the mentors-help Slack channel twice over the 4 week course, both times it felt slow to have someone get back to me; which I didn't really like in the moment - a good chunk of the Rmotr sales pitch was 'mentored learning', between this and point 1, I'd have to say I feel better mentored by my peers than Rmotr itself. A few checks-and-balances to what I'm saying here: I asked for mentors-help at weird times (e.g. Sunday evening) and I probably should have been in the beginner's camp (as the material was too dense for me to get through in the 4-week time frame). All in all, I'm very happy I chose RMOTR and would give you my business again under the right circumstances. Thanks so much
The people at RMOTR, whether they are the instructors, mentors, or fellow students, are perhaps the best part of the RMOTR experience. Everyone is very helpful, kind, and they all want you to understand the material.
"What follows is my perspective as a student who literally picked up coding earlier this year in January 2017. For others, I under these criticisms may not apply. At multiple points in the course, I found myself in way over my head in terms of the difficulty of the projects. This is both a good and bad thing. It's good because it is helpful to learn difficult concepts. But on the other hand, the feeling of helplessness during some of the projects left me very drained. Especially with further projects on the horizon with even more difficult and novel concepts. For example, after trying to learn one library or module in one project, we are thrown into a new project where we have to tackle even more modules, novel syntax from other frameworks, and even more new syntax from SQL databases. I am happy to try and learn all of these things. But all at once, in a 2-3 hour coding session, is quite daunting. I would have appreciated more practice and familiarity with some of these modules/libraries and concepts outside of the coding sessions. I'm not sure what could or could not be done with the 'learn' environment. In the latter half of the course, 'learn' is used a lot less and while I'm not sure the comparison to the Introductory Course is apt here, but in that course, the 'learn' assignments were much more helpful in preparation for the coding sessions and projects. Lastly, the more difficult projects seem like they would take most people quite some time to complete, necessitating more coding sessions. It can be difficult to arrange times outside the allotted schedule with other students and mentors to get help. P.S. - You guys should clone Jason Symons."
The people, the mentors, and the way the projects are designed to show us how to code for real.
The only thing I think could be done better is to give us at least a day between a class and the first coding session of that week. This way, we get the chance to really look through the material and get acquainted with it before we are thrown off the deep end with a project.
Mentors truly worked at your pace even when it must have been infuriating.
2 small things I didn't like. The time projects actually took was usually well over the 3 hour projected time. This led to several late nights and burned me out at the end of the course. Second small thing, the lectures skimmed over some material that became extremely important when doing a project. Sometimes felt that they lectures only hit the broadest of topics and we were supposed to research the tiny topics on our own time, most of my own time was spent trying to finish up prior projects.
"The amount of material covered was great, I felt I gained a much stronger grasp of Python during this course. I really like the instructors, and I find curriculum is really well structured. I'm a big fan and I will return when you have more courses that appeal to me, I'm even considering taking the Django class in a few months. Thanks for doing an amazing job!!"
I felt I took on too much by going directly from Intro to Python into Advanced Python. I would love if there was a bridge module that we could take, that consisted of several projects of the same complexity as the last few in Intro, first few of the Advanced class, basically involved object oriented programming problems. This combined with weekly meeting with mentors would have helped me solidify my skills before taking on the large workload and overwhelming amount of information of the advanced class. If I were to do it again, I would make sure that the advanced class was the only thing I had to focus on, as the amount of work is significantly more than the intro class. Waiting a month or two with active programming in Python would also have helped me.
I loved the fixed schedule, I would have never forced myself to read that much and work on projects that much on my own. I also really liked the exercises on the Learn platform, they just seemed to fit perfectly for cementing/applying what you just read. Simple enough to figure out in not too long of time, but with enough twist to make you think and make sure you actually understand what you just read.
I didn't really like working in groups on the projects. I feel more comfortable learning and experimenting with things on my own. In the groups, it either felt like your partner was leaving you behind, or you might be leaving your partner behind, but if you taught everything to your partner and made sure they understood everything, the project would take twice as long.
The instructors and the lab technology worked well. I have taken several online courses and have gotten bogged down in trying to make the labs work or getting them set up. But rmotr's set up worked well and I could focus on learning the course material.
A bit more instruction on your Learn platform would have been great. until about the third week I didn't figure out how to go back to a previous try at an answer.
Having a strict schedule (clear start and end date to the class, scheduled classes) with a short timeline (4 weeks) and lots of accountability (through all the required group work, having to join the Zoom sessions, mandatory human interaction) were all extremely helpful for a non-committal, procrastinating person like me. I usually never finish classes or I slack off, but RMOTR's class somehow pulled out a new level of dedication. I think out of all of those, being in a class with "real people" and interacting with each other was the most helpful in terms of keeping me coming and and staying on track. Taking other online courses can sometimes feel isolating, but RMOTR did the absolute best it could in relieving that.
I have mixed feelings about amount of resources given on the material. If I were not already aware of and familiar with all of the concepts covered, I imagine that the links for reading material would not be enough. The lectures to cover concepts were not that detailed either. I think what filled me in most were the Learn exercises and the group projects, so I would suggest having even more Learn exercises (double the amount, especially for the OOP and Advanced OOP sections) OR adding another project per week on Tuesdays instead of having just a Learn exercise group work day. I think Monday & Tuesday sessions were the least helpful because we wouldn't cover much in the Zoom session and we didn't do any projects those days either.
I really enjoyed the structured approach and the accountability that comes with working with teammates.
Instructors sometimes had poor internet connection experiences so it was hard to hear them at times, but it was just few times. Not sure if it should be considered as an issue.
I really enjoyed the projects using GitHub - they're hard, but it's a great way of seeing how everything fits together.
The difference in timezones was a bit rough, but that's inevitable and no-one's fault. I also prefer to work by myself so fewer group projects would have been better for me, but that's just me.
Once you understand the learning process, it's very streamlined and engaging to solve the weekly problems. Even the homework is often challenging and engaging. If you're looking for depth, the instructors and mentors are always ready for a deep dive on a topic.
There were times that I dreaded being paired up with someone who was really behind, which happened to me a few times. The difference between being paired up with someone around your level, versus someone that just isn't "getting it" is that you will spend the entire session explaining a problem instead of solving a larger problem collaboratively.
Our latest on RMOTR
Phil Wright studied math in college, and took a job in manufacturing after graduation. He started teaching himself Python to help automate manufacturing processes, but needed more guidance; so he enrolled in RMOTR’s online Advanced Python Programming course. Phil explains why he wanted to learn remotely in a collaborative environment where he could communicate regularly with instructors and students, tells us about his extra RMOTR capstone project that expanded his skills, and talks about his new job as a software engineer at FoxGuard Solutions!
What were you up to before RMOTR?
I got a mathematics degree, with a big focus on math theory. After graduation, I went to work for a local manufacturing company. The work was related to customization and optimization of their products and processes. In college, I took some courses that introduced me to scientific computing resources, like MATLAB and Mathematica, and took some very basic programming courses, so I had a slight working knowledge of a couple of programming languages.
Once I started working for the manufacturing company, I saw a number of ways that coding tools could be used to automate processes, and I wanted to learn more about how to use those tools. I started learning Python, largely because of how accessible it was and because of the supportive online community of people who were learning and sharing resources. Over a few years, I built up basic Python skills, and I knew some of the basics of control flow, but I was having difficulty grasping certain features of the language. So I started looking for resources to help me learn those more technical aspects of the language in a guided environment.
Which courses did you take at RMOTR?
Why did you choose RMOTR over other online coding courses? Have you taken other online courses?
I have taken some other courses through sites like Udacity and Coursera to improve my programming skills. What really drew me to the RMOTR courses was the level of communication between the instructors, students and mentors, that the classes were taught in real time, and that the projects were done in real-time, collaborating with other students. I also liked that RMOTR would allow me to ask questions and have immediate resources to get answers. Finally, I needed an online course that would allow me to work from home – that was a big deal for me – and also outside of work hours, because I was working full-time.
What was the RMOTR application process like for you? Since it was an advanced Python course, did you have to demonstrate prior knowledge?
I had to submit an application that included a short development test. It tested the basics of the language constructs and some fundamentals of Python. For the Django course, there was a similar test.
How many people were you studying with? Was your class diverse in terms of gender, race, life and career backgrounds?
My cohort for the Python course was around 18 to 20 students. There were two separate classes running at the same time, which were divided up for logistical reasons. For the Django course, we had 6 to 8 students. In both classes there was a fairly good mix of students and professionals. There were a few people who were interested in learning the language for their current jobs; others were self-employed and wanted the skills to offer to clients. In the Python class there were a few women, and there was one woman in my Django cohort.
There were people from a few different countries too. In the Python class we had a man from India, which was a lot of fun. It was great to be able to interact with people from all over the world, and around the US. I live in Virginia, but I got to learn with students from St. Louis, Texas, California – all over the place.
What was your learning experience like at RMOTR? Tell us about the teaching style.
Both courses were each four weeks long. We were assigned readings the week before we met for the first time, and then for each following week. Each week we would have one scheduled, two-hour lecture session, where everyone would meet online and the instructor would give a presentation related to the readings that we had done. We would interact with the instructor, ask questions, and go through a few examples.
Later in the week, there would be three separate, three-hour coding sessions. During each coding session an instructor or mentor would present a new project to us, then we would split into groups, and go into separate Google Hangouts and work as a team to code on the project. If we had a question during the session, we could message the mentors on Slack and a mentor would jump into our Hangout to help. Once we submitted our solutions through Github, we would receive another group’s work to code review, and our work would be code reviewed by another group.
We learned a lot through the projects, and through reviewing other people’s code. We needed to think critically about the design decisions they made.
Were there time constraints? Did you have to set aside a certain amount of time to do RMOTR?
In total we were working about 20 hours per week.
Our lecture session was one evening during the week; two of the coding sessions were on weeknights, and the third coding session was on Saturday mornings. It worked very well; it meant we had one day between each coding session, and one evening off, so we could catch up on reading or have a much-needed break.
How many instructors or mentors did you have, and how did you communicate with them?
The two primary instructors were Santiago and Martin, who are the RMOTR founders, and then we had 3 to 5 mentors during each coding session in addition to Santiago and Martin. We would use Slack to communicate with them – if we had a question we would send a link to our hangout, and a mentor would jump in to help.
Outside of coding session times, there were usually one or two people available, or we could schedule something if no one was immediately available.
What is your favorite project that you built in a RMOTR course?
At the end of the advanced Python course, there was an optional demo day project, where students could form a small group and work on a project for a couple of weeks. We had to submit a proposal for what our project would do, and build a minimum viable product. Then Santiago and Martin invited people from the software development industry to a demo session where we could demo the project and answer questions about decisions we made.
My group built a website which listed open software development jobs, and provided statistics around the numbers of job postings over time for jobs users are looking for. It also pulled in reviews of companies from the glassdoor.com website. It was definitely a challenge to do in the amount of time that we had, but I really enjoyed it.
What sort of career advice did the team at RMOTR give you?
Santiago and Martin gave us guidance on how to seek out the types of jobs that we would be prepared for after the courses, suggested some good websites to look at, and encouraged us to collaborate and share our successes with other students. They also talked about resume writing, and encouraged us to come to them with questions related to that. Alumni are still able to interact with current students and previous alumni through the Slack channel – there is a lot of discussion on there about job search tips, and about programming questions, which is really cool.
How did these two RMOTR courses help you with your career?
One reason I chose to do the demo day project was because I was looking for a new job. Late last year, I found a new job working as a full-time software engineer! I know that the practices encouraged by RMOTR are things that this new company found attractive in me as a candidate. For example, I now have a solid understanding of test driven development, good knowledge of continuous integration practices, experience doing code reviews, and working with Github – I learned all of that at RMOTR.
Where are you working as a developer now and what’s your role?
I’m working for FoxGuard Solutions, a local Virginia security software development firm. The team I’m working on produces web-based tools for security management for client assets. The work has involved doing programming in a number of different languages. I work on a team with about eight other developers, and we focus on test driven development, which I learned a great deal about at RMOTR. We have a solid continuous integration procedure in place for development, as well as a very structured code review process. A few of the tools we use at this company are the same or similar to tools we learned with RMOTR.
Are you using Python or Django – the languages you studied at RMOTR? How has your company trained you on new technology?
I’ve done some work in Python at my new job, and I’m still using it extensively on personal projects, but it’s not the primary language at this company. Most of the work I do is in C# which I did not have a ton of experience in before I got the job. But the languages that I learned at RMOTR helped prepare me for learning C#.
FoxGuard Solutions trained me in C#. There were some language-specific exercises I went through for a few months when I started at the company, and I was encouraged to interact with other developers on the team when I had questions. So it was a mix of using reference material, training resources, and asking questions, which is similar to how the RMOTR courses were structured.
Since I’ve started doing more software development, I’ve learned that the process of running into questions or issues as I’m developing is something that is always going to happen, and it’s good to know how to find the answers yourself. That was something I really appreciated about the RMOTR course – when we had a question, the mentors or instructors would answer the direct question, and also point out where deeper documentation could be found. When you have one question about a topic, you’re most likely going to have more in the future.
How has your previous background been useful in your new job?
At my previous company I learned a lot about time management and prioritization. In manufacturing there is a heavy emphasis on efficiency and lean practices, and that’s helped me see how and why tasks at my new job are prioritized the way they are. I also brought knowledge of how and when to communicate about questions or hangups that may arise, when those need to be asked, and how to determine who to communicate with. A lot of that was very key to the work we were doing on the manufacturing side and has helped a ton in this new job.
What’s been the biggest challenge or roadblock in your journey to becoming a full-time software developer?
One of my biggest challenges is part of my own personality: I love to have a complete and rigorous understanding of a topic before I start working on it. That’s held me back in some situations. I’ve had to learn to accept the gaps I have. One of the things my team talks about is personal technical debt, which refers to gaps in your knowledge that you’re aware of, which you deliberately allow to be there, so that you can be functional with a certain tool or topic. Being aware of that has been very useful.
What advice do you have for people making a career change through a coding bootcamp?
Establish concrete goals for yourself and look for programs that address those goals specifically. Don’t be afraid to do research into a number of coding programs, be willing to re-evaluate those goals and work hard to accomplish them. I can’t speak highly enough about RMOTR’s courses. As long as you’re willing to work hard and invest time and effort, you’ll certainly benefit greatly from them. It’s especially difficult to gain additional skills on top of a full-time job, but it won’t be that difficult forever – it’s worth the extra effort!