Rails API development
Clean, tested REST APIs for web and mobile clients. Authentication, background jobs, integrations, and the reliability work that keeps products running.
Available for select projects
Five years of shipping and maintaining Ruby on Rails APIs and React interfaces for product teams. Clear communication, steady delivery, and code your next developer will thank you for.
Recent work includes a long-running Rails and React retainer for MoxiWorks. Now taking on focused projects around 16 hours per week.
Teams and products I have worked with
Services
From a focused fix to a full product build, I work best with teams that value clear scope and honest communication. I take on a limited number of projects around 16 hours per week.
Clean, tested REST APIs for web and mobile clients. Authentication, background jobs, integrations, and the reliability work that keeps products running.
Interfaces that feel fast and predictable. Component systems, data-heavy screens, and clean handoffs to backend APIs.
From idea to a working Rails and React product. Scope, build, launch, then iterate without rewriting everything.
Bug fixes, upgrades, performance cleanups, and inherited codebases. I leave things clearer than I found them.
Third-party services, webhooks, CSV imports, admin consoles, and the glue work that unblocks your team.
Practical reviews, documentation, and handover sessions so your team can own the product after I leave.
AI-assisted delivery
I use AI tools for the repetitive parts of delivery, then review and test every change like production code. Speed is useful only when the result still holds up.
Selected work
A few projects that show how I work: joining a team, finding the real problem, and shipping without drama.
A long-running Rails and React engagement for a real estate software client. I joined an established, distributed team and worked across two active workstreams.
Prem manages his time exceptionally well, supporting AP work while also contributing to RiSE development. He is proactive, communicates clearly, and is always ready to collaborate with the team.
Ana Marta Povoa, Manager, Engineering, MoxiWorks
Product engineering for web and mobile applications. The work ranged from new API endpoints to custom features and supporting the people around me.
As per my information, Prem Kaithwas is a great developer. He is doing great.
Suyash and Devesh, Qubited
Backend work for a React application. I owned API endpoints and business logic, then learned React so I could close the loop between frontend and backend.
Congratulations on completing tasks given to you efficiently. Also, I appreciate your efforts for learning React to complete your task. You are doing a great job at becoming more efficient in your workflow.
Team appreciation, Cryptex Technologies
Testimonials
Kind words from managers, clients, and teammates. The common thread is communication, ownership, and follow-through.
Awesome work, Prem. Thanks for handling all these challenging tasks. I mentioned your work and task management to Ben today. We are all really happy with your approach and progress.
It is nice to be treated like a human being. I am sorry I will not be around to watch you finish growing into being an excellent engineer, but I am glad I got to work with you in the meantime.
Pleasure working with you. Your promptness and response to dedicated tasks will lead you ahead in future endeavours as well.
Many thanks. Really appreciated.
Excellent, thank you so much Prem. Let me know how progress is going if no issues. Thanks again and have a good rest of your day.
It has been a pleasure knowing you. Wishing you all the best in your future endeavors. Take care.
Collected from client notes, team messages, and company appreciation posts.
Software engineer
About
I am Prem, a software engineer based in India. For the last five years I have worked across product companies and client projects, mostly in Ruby on Rails and React.
I care about the unglamorous parts: clear APIs, readable code, honest estimates, and handovers that do not leave teams stranded. I have joined inherited codebases, worked alongside product and QA, and handed work back with documentation and a walkthrough.
I use AI tools where they genuinely help, but the judgment, review, and communication stay human. Faster is only useful when the result is still reliable.
Writing
Primebase is where I think in public. The tech blog covers AI tools, cloud, and practical fixes. Both are part of how I learn and explain things clearly.
Process
You should always know what is happening, what comes next, and what it costs.
We talk about the product, the problem, and the timeline. No pitch deck, no pressure.
Scope, milestones, and a clear estimate. You know what is happening before work starts.
Working software every week, a staging link, and updates you do not have to chase.
Docs, a walkthrough, and a support window so your team is not stranded.
FAQ
Rails and React products, API work, maintenance and rescue projects, and focused MVP builds. I am most useful when there is a real product, a clear problem, and room to improve the code over time.
Yes. I have worked in inherited codebases, joined distributed teams, and handled knowledge transfer in both directions. I start by reading, asking questions, and making the smallest safe change.
Yes, as a force multiplier. I use AI for scaffolding, tests, refactors, and documentation, then review and test everything before it ships. I also document the reasoning and trade-offs, so you see the judgment, not just the output.
Fixed scope for defined projects and a weekly rate for ongoing work. You get a written estimate before we start, and I flag scope changes before they become invoices.
Around 16 hours per week alongside my full-time role. That fits a focused scope, ongoing maintenance, or a defined workstream. It is not a full-time embedded role.
IST, UTC+5:30. I overlap with European mornings and US mornings or evenings with a little planning. I have worked with teams across India and the United States.
Yes. I have delivered through an agency retainer and directly with product teams. I am comfortable being the extra pair of hands or the person who owns a workstream.
I already have a full-time role, so my focus here is part-time freelance and contract work around 16 hours per week. If you have a scoped project that fits that capacity, I would be glad to talk.
Let us build
I take on select projects around 16 hours per week. Tell me what you are building, what is stuck, and your timeline. I reply within one business day.
Prefer LinkedIn? Connect with me.