James Bitanga Overview

  • Investor Type
  • Angel
  • Investments
  • 1
  • Exits
  • 1
Exits

James Bitanga General Information

Description

Mr. James Bitanga serves as Chief Legal Officer at REAPRA. He joined REAPRA in August 2016, and holds extensive legal and business experience in the technology and startup space. Prior to REAPRA, He worked as a legal consultant under Axiom supporting the commercial and compliance activities of some of the largest global technology companies. He also held an in-house role with IBM following years of private practice in New York and government work in the Philippines. He is an active member of the Southeast Asian and US startup community, primarily as an angel investor. He completed his Juris Doctor from Boston College Law School and a degree in Management in Communications Technology from Ateneo de Manila University. He is a member of the New York Bar.

Contact Information

Primary Investor Type
Angel (individual)

James Bitanga Investments (1)

Company Name Deal Date Deal Type Deal Size Industry Company Stage Lead Partner
0000000 15-Oct-2013 0000 00000 00000 Application Software Out of Business 00000 0000000 00
To view James Bitanga’s complete investments history, request access »
Want detailed data on 3M+ companies?

What you see here scratches the surface

Request a free trial
Want to dig into this profile?

We’ll help you find what you need

Learn more

James Bitanga Exits (1)

Company Name Exit Date Exit Type Exit Size
0000000 17-Jul-2017 000 00 00000000
To view James Bitanga’s complete exits history, request access »

James Bitanga Investments by Industry, Year, and Region

Investments by Industry

Investments by Year

Investments by Region

PitchBook’s data visualizations quickly surface an investor’s historical investments—showing a breakdown of activity by industry, year and region.

Request a free trial

James Bitanga Team (1)

Name Title Deals Funds Boards Office
James Bitanga JD Angel Investor 0 Singapore, Singapore
To view James Bitanga’s complete team members history, request access »