Skip to main content
The people behind the code

Meet the team

How we're structured

Discipline groups, not a pool of generalists

CodePrism isn't one undifferentiated bench of developers. Everyone belongs to a discipline group with real depth in its craft: full stack engineering, React and React Native, Flutter, Java, Python, AI and ML, solution architecture, UI/UX design, and quality assurance.

Projects draw from whichever groups the work actually needs. A WhatsApp CRM rollout might pull a solution architect, two full stack engineers, and a QA engineer. A production generative AI system pulls from the AI and ML group with backend engineers behind it. The group is where someone's craft gets sharpened. The project team is where it gets applied.

That's why we can staff an enterprise engagement without a hiring cycle in front of it, and why the engineer reviewing your React Native pull request has spent years in React Native rather than picking it up for your project. You can see what the arrangement produces in our case studies and across our services.

30 people across 12 disciplines

Current headcount by group, straight from our team directory.

Management
3
Java
1
Flutter
2
React and React Native
5
Quality assurance
2
Python
1
UI/UX design
2
Full stack engineering
7
Accounts
1
Solution architecture
2
Sales and marketing
1
AI and ML
3
Our team

The people who make it happen

Each person here ships real software for real enterprises. Grouped by the discipline they practice.

Management

Anupam Gupta

Anupam Gupta

Managing Director & Founder

Godwin VC

Godwin VC

Managing Director & Founder

Priyanka Kondapally

Priyanka Kondapally

Manager, HR

Java

Chandan Kumar

Chandan Kumar

Java Developer

Flutter

Korapati Syam Kumar

Korapati Syam Kumar

Flutter Developer

Anoop Unni R

Anoop Unni R

Flutter Developer

React and React Native

Priyanka Pradhan

Priyanka Pradhan

Senior Frontend Developer

Azhar Ahmad Lone

Azhar Ahmad Lone

Frontend Developer

Mriganka Sekhar Hazarika

Mriganka Sekhar Hazarika

Frontend Developer

Purandhar Sri Sai Pasam

Purandhar Sri Sai Pasam

Frontend Developer

Albrin V Anand

Albrin V Anand

React Developer

Quality assurance

Pochammala Praveen

Pochammala Praveen

Senior Software Engineer

Regonda Durga Prasad

Regonda Durga Prasad

Software Engineer

Python

Muhammed Anees K

Muhammed Anees K

Backend Developer

UI/UX design

Harika Ogirala

Harika Ogirala

UI/UX Designer

Kasula Hrithik

Kasula Hrithik

UI/UX Designer

Full stack engineering

Vamsi Thiruveedula

Vamsi Thiruveedula

Full Stack Developer

Muhammed Hisham

Muhammed Hisham

Full Stack Developer

Shiva Prasad

Shiva Prasad

Full Stack Developer

Ashif Ali P

Ashif Ali P

Full Stack Developer

Gangula Saicharan

Gangula Saicharan

Full Stack Developer

Chamala Harshavardhan Reddy

Chamala Harshavardhan Reddy

Full Stack Developer

Deepak Mittal

Deepak Mittal

Full Stack Developer

Accounts

Aastha Adatia

Aastha Adatia

Accounts & Finance Executive

Solution architecture

Sameer Joshi

Sameer Joshi

Solution Architect

Bala krishna Reddy Mogiligundla

Bala krishna Reddy Mogiligundla

Solution Architect

Sales and marketing

Arindama Ramakrishna

Arindama Ramakrishna

Sales and Marketing Head

AI and ML

Pratheek Nistala

Pratheek Nistala

AI/ML Engineer

Mounika Badri

Mounika Badri

AI/ML Engineer

Syed Basid

Syed Basid

AI/ML Engineer

How we work

What working with this team looks like

The four things that stay constant no matter which disciplines your project draws on.

Engineers own outcomes, not tickets

Whoever writes the code stays with it through review, deployment, and the first production incident. Nothing gets handed to a maintenance team that has never opened the codebase.

Small teams, direct access

You talk to the engineers building your product, not to an account manager relaying requirements. Fewer people in the loop means fewer things lost in it.

Reviewed before it ships

Every change goes through peer review inside its discipline group and an automated check suite. Quality assurance joins at the first sprint instead of being bolted on before launch.

Documented while we build

Architecture decisions, runbooks, and handover notes get written while the context is still fresh, so your own team can operate what we deploy.

More on where the company came from in our story, what we stand for on the about us page, and if you want a desk in one of these groups, we list every open role as soon as it opens.

Want to work with this team?

We're always looking for exceptional engineers, and if you have a project in mind, let's talk.

Get in touch