Where I started building
Born in India, I grew through hands-on full stack work and early technical leadership in fast-moving product environments.
Frankfurt, Germany / Senior Software Engineer — Systems, Regtech & Product Delivery
I build clarity into complex systems.
I am a full stack engineer in Frankfurt, shaped by India, New Zealand, and Germany. I work where product, infrastructure, data, and regulation meet.
Frankfurt
Living and working in Germany
10+ yrs
shipping production systems
3 domains
regtech, infrastructure, product
3 languages
English, Hindi, German
Three chapters
Built across three countries, grounded in Germany.
Where I learned range
Computing, management, international business, and customer-facing work gave me a practical view of how people depend on systems.
Where I work now
Now a German citizen in Frankfurt, I focus on infrastructure, regtech, reporting workflows, and dependable product delivery.
What I bring
I work best where the problem is not fully defined yet.
The useful work is often between roles: clarifying the rule, shaping the system boundary, and making the final tool usable for the people who rely on it.
Product-minded engineering
I stay close to the user problem, then turn it into interfaces, services, workflows, and tradeoffs a team can ship.
Systems people can explain
Regulated work needs clear rules, visible state, traceable data movement, and failure modes people can understand.
Ownership after launch
I care about maintainability, operations, support signals, and the decisions that decide whether a system stays useful.
Working model
How I move from vague requirements to working systems.
The details change by project. The pattern does not: understand the rules, design the data path, build the interface, and make the result supportable.
01 / Requirements
Turn unclear requirements into implementation decisions.
I separate policy, workflow, data shape, and user intent early so teams can estimate honestly and avoid carrying hidden risk into delivery.
$ solve --mode regulated-workflow
rules.normalized -> backlog.ready -> edge_cases.visible
Project patterns
Problems I am useful for.
Some of the best engineering work cannot be shown as public screenshots. These examples focus on the shape of the work, the constraints, and the decisions behind delivery.
Regulatory systems
Reporting flows with traceable data paths
Designing flows where inputs, validation, transformation, approval, and generated output can be followed and explained.
- Rule-heavy business logic
- Validation and exception handling
- Audit-friendly operational views
Infrastructure
Services and pipelines teams can operate
Building backend and data movement foundations with clear ownership, deployment paths, observability, and recovery plans.
- APIs and service boundaries
- Data pipelines and integrations
- Deployment and runtime clarity
AI-era engineering
Human judgment around AI-assisted delivery
Using AI where it helps, while keeping architecture, risk, domain understanding, and accountability with the engineer.
- Problem framing before code
- Review, testing, and verification
- Pragmatic automation choices
Work contexts
Products and environments I have worked on through my roles.
Not a CV timeline or endorsement list. A compact view of the companies, products, and regulated environments that shaped the problems I have worked on.
Frankfurt-based engineering work across regulatory reporting, infrastructure, internal tools, and product delivery.
Deutsche Bundesbank
European Banking Authority
Unfallkasse Hessen
accenture
shoutME Technologies
GRUNDFOS
GEA Group
NORD
reflex
SKS Group
PERCEL
IDSM
mikroforum
reghouse
CQNC
Some names are employers; others are products, institutions, or environments worked on through those roles.
Toolkit
Technical range, used with restraint.
A senior engineer is not defined by one framework. The value is knowing which tool fits the constraint, how to integrate it, and when to keep the system simpler.
Software Infrastructure
Service design, data movement, deployment discipline, observability, and reliability work.
Regtech
Software for regulated teams where correctness, traceability, and auditability matter.
Regulatory Reporting
Validation, reporting workflows, generated outputs, and clear operational handoffs.
Full Stack Delivery
Backend design, frontend implementation, integrations, and pragmatic technical leadership.
Cloud + Platform
Azure
Cloud architecture
CI/CD
Observability
Backend + Data
APIs
Data pipelines
Integrations
Validation logic
Frontend + Product
UI systems
Internal tools
Workflow UX
Accessibility
Working languages
English
Hindi
German B2
Positioning for the AI era
AI changes delivery speed. It does not remove engineering responsibility.
My value is in problem framing, architecture, domain understanding, system boundaries, verification, and deciding what should not be automated blindly. That matters most when the cost of being confidently wrong is high.
Contact
Working on something complex, regulated, or hard to operate?
I am based in Frankfurt and open to conversations around senior engineering roles, platform work, regtech systems, reporting workflows, and product engineering where correctness matters.
Fill this in and it opens a pre-filled email in your own mail app — nothing is sent from here.
Prefer to skip the form? Email me directly at contact@puravrag.com.