Software Engineer Intern (Fullstack)

About GeoComply

We’re GeoComply! We are at the forefront of geolocation, cybersecurity, and anti-fraud innovation, developing and delivering cutting-edge technologies to help ensure regulatory compliance, combat bad online actors, alleviate user friction, and protect businesses from fraud.

Achieving significant business and revenue growth over the past three years and dubbed a tech “Unicorn,” GeoComply has been trusted by leading global brands and regulators for over ten years. Our compliance-grade geolocation technology solutions are installed on over 400 million devices and analyze over 12 billion transactions a year.

At the heart of it all is the people, united by a deep commitment to problem-solving and revolutionizing how people and businesses use the internet to instill confidence in every online interaction. With teams across five countries, three continents, and a global customer base, we have no plans to slow down.

The Role

GeoComply runs fraud detection at a scale most engineers never encounter — billions of monthly transactions, real-time decisions, zero tolerance for error. GCI (GeoComply Chargeback Intelligence) is at the center of a 2026 strategic push to turn chargeback data into a proactive fraud-prevention asset across the entire product ecosystem (RiskGuard, IDComply, HUB, CMS, CORE) — not just a reactive dispute tool.

As a Software Engineer Intern (Fullstack) on the CMS/GCI team, you’ll work across the stack — Go and PHP/Laravel services as well as the React frontend — to help build what makes this possible: the APIs and data pipelines that turn chargeback history into fraud signals, and the UI that surfaces it to analysts and clients. Today, only ~0.2% of GCI’s 215K+ chargeback cases have a recorded outcome; you’ll help build both the backend plumbing and the user-facing workflows that close that gap. You’ll bring product curiosity to a genuinely high-impact problem, take real ownership of your work, and use AI tools as a default part of how you build. This is what fullstack engineering looks like here.

Key Responsibilities

• Backend

  • Help build the API and data-layer work needed to surface chargeback intelligence to other products — e.g., querying chargeback history by user ID, device fingerprint, IP, email/phone for consumption by RiskGuard and IDComply.
  • Contribute to the outcome / feedback-loop pipeline: capturing won/lost/fraud-type case outcomes and propagating that data so it strengthens fraud scoring elsewhere in the ecosystem.
  • Work in our Go, PHP (Laravel) and Python depending on the task — following our DDD/clean-architecture and CQRS conventions.
  • Support data aggregation for Phase 1.5 intelligence features — dispute frequency patterns, geohash-based clustering, cross-operator pattern detection.

• Frontend

  • Build and enhance the GCI case & dispute UI — chargeback case lists, outcome-capture flows, and case detail views — using our org-wide Storybook Design System and React.
  • Contribute to the GCI section of the Unified User Page — surfacing chargeback counts, disputed amounts, case history, and device-level flags in a single view for fraud analysts.
  • Build visualization surfaces such as dispute geohash heatmaps, returning-offender alerts, and chargeback trend views.
  • Build status-tracking UI in support of Phase 2 automation and AI initiatives (automated dispute submission, AI-optimized dispute documents) as these capabilities come online.

• Across the stack

  • Use AI-assisted tools (coding assistants, our Figma Storybook pipeline, LLM-powered workflows) as a default part of your engineering practice — not occasionally, but every day. Spot opportunities where AI can reduce toil or accelerate delivery in the GCI workflow, and propose them.
  • Understand the why behind each feature — how chargeback and dispute data connects to fraud-prevention outcomes for clients, not just the ticket description.
  • Participate in the full development lifecycle: scoping, implementation, testing, PR review, and post-release monitoring, on both API and UI changes.
  • Write well-tested, readable code on both ends of the stack, and collaborate with designers, QA, and backend/frontend engineers to ship high-quality, end-to-end features.
  • Raise risks early — surface data-sensitivity concerns (chargeback data touches PII and cross-operator signals), edge cases, and tradeoffs proactively rather than waiting to be…