Support & Maintenance of a Beta Node.js/Next Application
Budget: $750 – $1,500 USD
Hello!
We are looking for a single developer (not an agency) to help with ongoing support & maintenance of a web application (already built) as we progress through beta. The application is a tutoring platform that connects students and teachers for live, online lessons over the Internet.
High service quality is paramount which is why we are looking for someone who can help us on a part-time basis debug issues as they might arise.
Application: A coaching platform.
1) A teacher sets his/her time zone and creates windows of availability (i.e., Tuesdays 7-9pm).
2) Students can browse different teacher profiles, see the windows of availability translated in the students’ time zone, and schedule and pay for sessions (30 min, 45 min, etc.)
3) Additionally, through a messaging feature, the teacher can offer students sessions directly.
The backend is built in Node.js; the front-end in Next.js. The database is Mongo. Other services connected to project include Mongo, AWS (S3), Redis & Sendgrid. And the web application itself is hosted on Heroku.
What we are looking for
Principally, a back-end developer skilled in Node.js who can:
1) Troubleshoot bugs and issues as they arise in production/launch
a. The code does not currently have very good documentation
2) Develop &/or streamline incremental issues
3) Has some full-stack experience to implement small front-end issues as they arise
Potential Issues We Need Help On
A user’s service quality relates to scheduling sessions, and having those sessions appear on an internal or exported calendar. The ‘state’ of those sessions shift from Upcoming, to Live, to Passed, etc. It is possible we may have issues with this and we need help in troubleshooting this if it occurs.
Payment provider. We have PayPal and Stripe integrated and are currently testing in sandbox mode. We might have issues as we convert to Live.
Length of engagement
It is likely it would take some time to review & understand the current code upfront. Afterwards, we would be looking for support on an ‘on call’ basis. We can discuss what that would mean. But for now, perhaps 4-6 months.
Next Steps
We can do a 10-15 minute walkthrough of where we are at, plus review some of the issues that have been of concern to us. Thank you.
We are looking for a single developer (not an agency) to help with ongoing support & maintenance of a web application (already built) as we progress through beta. The application is a tutoring platform that connects students and teachers for live, online lessons over the Internet.
High service quality is paramount which is why we are looking for someone who can help us on a part-time basis debug issues as they might arise.
Application: A coaching platform.
1) A teacher sets his/her time zone and creates windows of availability (i.e., Tuesdays 7-9pm).
2) Students can browse different teacher profiles, see the windows of availability translated in the students’ time zone, and schedule and pay for sessions (30 min, 45 min, etc.)
3) Additionally, through a messaging feature, the teacher can offer students sessions directly.
The backend is built in Node.js; the front-end in Next.js. The database is Mongo. Other services connected to project include Mongo, AWS (S3), Redis & Sendgrid. And the web application itself is hosted on Heroku.
What we are looking for
Principally, a back-end developer skilled in Node.js who can:
1) Troubleshoot bugs and issues as they arise in production/launch
a. The code does not currently have very good documentation
2) Develop &/or streamline incremental issues
3) Has some full-stack experience to implement small front-end issues as they arise
Potential Issues We Need Help On
A user’s service quality relates to scheduling sessions, and having those sessions appear on an internal or exported calendar. The ‘state’ of those sessions shift from Upcoming, to Live, to Passed, etc. It is possible we may have issues with this and we need help in troubleshooting this if it occurs.
Payment provider. We have PayPal and Stripe integrated and are currently testing in sandbox mode. We might have issues as we convert to Live.
Length of engagement
It is likely it would take some time to review & understand the current code upfront. Afterwards, we would be looking for support on an ‘on call’ basis. We can discuss what that would mean. But for now, perhaps 4-6 months.
Next Steps
We can do a 10-15 minute walkthrough of where we are at, plus review some of the issues that have been of concern to us. Thank you.