We’re very proud to be adding good paying technology jobs to our local community and working with clients worldwide. You can find out more details about RED SOFT, by visiting our about page.
You can easily describe RED SOFT’s clients as the following:
Some quick facts about our clients:
- Helping our clients reach their full potential, however they define success.
- Giving students real world experience they wouldn’t otherwise gain.
- Creating a work place and culture that supports people’s personal goals.
- Dedication to every person’s long term success.
- Identify root causes and get beyond solving the symptoms.
- Trust and personal responsibility in all relationships.
RED SOFT receives over 200 new applicants a month Our selection process includes 4 steps :
I. Coding test- Should need to get 80% number of all applicants.
II. Best fit phone interview.
III. Reference check. IV. In – personal interview:
- We’ve interviewed more than 800 candidates in order to find the group of people.
- When hiring developers, we focus on finding people who can learn and apply concepts quickly under pressure and have a strong grasp of computer science fundamentals.
- Our team is fluent in many languages, technology stacks and specialties.
- It’s mutual or bilateral.
- We understand the requirements of the project and believe that the project and client are a good fit for RED SOFT
- We are not violating any other agreements that we have as a company.
- The requirements in RFPs are often extremely detailed, but usually lack any business context.
- The probability of this document containing the optimum feature set is extremely low.
- By agreeing to respond to an RFP, we are relying 100% on someone else’s ability to capture the correct requirements. The right features are better learned by the project team through user interviews, mockups, prototyping, releasing actual software and getting feedback from real users.
- This contract style sets the client and consultant working against each other right from day one.
- Communication between project teams and clients is not limited to interactions with the project lead. Every member of the RED SOFT team is empowered to communicate with our clients. It’s common for phone calls and emails to be exchanged throughout the work week between RED SOFT teams and their clients.
- Every project team at RED SOFT is assigned to a team E-mail(firstname.lastname@example.org).
- Weekly meeting to review success, failures and future plans- 1 hour
- Team members demonstrate what they got done the week prior.
- Everyone discusses how they can improve the processes/techniques on the project.
- Software is rarely “done.” We know that our clients and their users will continue to have great ideas throughout the process and after the initial delivery. As your business changes, your software will need to evolve and adapt.
- It’s common after the first release to pause on building features for a bit and focus on enhancements or fixes to drive user ad option.
Do you code everything from scratch?
RED SOFT teams get incredible leverage from open source tools, libraries, frameworks and indeed entire projects or our own proprietary libraries. We never reinvent the wheel when there is a tool that is suitable for solving a problem. We always program from scratch the parts that make your project custom and valuable.
Our projects run from a few months to a year or more. Some have a budget of $50k and others have budgets of over $1 million.
- Code Review – 2 people, 1 week
- Research, Design & Planning engagement – 3 people, 4 weeks
- Idea to Version 1 – 3 people, 3-5 months
- Proof of Concept – 2 people, 1 to 2 months
- Project Rescue – varies
- Dedicated Team – retainer per month
- Fill a gap until an internal team is hired – 2 people, 3 months
- Staff augmentation with existing internal team – 3 people, 6 months
While its really hard to know the specific costs of the project without going through a discovery phase like our Research, Design, and Planning phase, we can usually help you set a responsible budget during before you ever hire us.
No matter how large or small your budget, it’s always our goals for the value our clients receive to significantly exceed the fees we charge.
For a rough approximation of project duration, we take the estimates above and divide by 32 hours for each person on the team. For example, a 1200-hour project takes approximately 3 months of calendar time for a team of 3 people (1200 hours / (3 people * 32 hours/person/week) / 4 weeks/month = ~ 3 months)
On large projects, we’re able to add people and go faster. That’s quite an amazing thing, actually, and not something every team or company can do. Growing the team requires we have additional employees available.
For projects that have a total monthly budget, we still track hours to ensure that we hit the mark each and every month. For more details about pricing or engagement models, you can see our pricing and packages here.
Remember, you are paying your team to help you mitigate these risks, not to financially own them. Each sprint or release is not a guarantee of a finished, bug-free product. However, we do have standards and best practices in place that encourage each team to do their best to build a high-quality product.
We encourage our clients to embrace bugs, embrace risks, and know that we will do everything we can to address both. Your team will track bugs and work them into the schedule each week with other backlog item.
Our teams are smart and experienced; they do their best at predictably building your product. With each iteration, we’ll take what we’ve learned and quickly your teams integrate new insights to keep quality high.
Be aware that the financial risk of developing custom software is in your hands. A warranty doesn’t come from your development team, but it’s what you will offer to your customers and employees. Taking on the financial risk is why you have such a potentially significant financial upside.
When billing for a dedicated team, payment is due in advance for that month’s team. Ex: On February 1 st, you’ll pay for the month of February.
- Not fully understanding the scope of the project.
- Lack of client and team communication throughout the project
- In the event of each failure, we ate the full cost of the project until it was back on track. We know this was the right thing to do.
- After taking our lumps, we improved our processes and our training. Some improvements include:
- Creation of our highly successful Research, Design & planning phase.
- Multi-point estimation methods that put an emphasis on risk
- A more thorough 60-day on boarding process with all new employees.
- Mandatory Scrum training for all new employees
- Web – Python (Django, Flask), ASP.NET Core (C#), PHP, Node.js, ReactJS, AngularJS, HTML5, Bootstrap, Sass.
- Mobile – iOS, Android, Cordova
- Desktop – Java, Microsoft WPF
- Embedded – C, C++
- Database – PostgreSQL, SQL Server, MySQL