Technical Support Engineer (Java)

Cybrilla Technologies; Bengaluru; On-site; INR 1,800,000 - 3,000,000; Full time

Job summary

Cybrilla Technologies is seeking a production‑level Java engineer who can own customer issues end to end. You will diagnose across services, write fixes, and deploy with proper tests and rollback plans.

The role emphasizes strong debugging, systems thinking, and clear communication with customers and stakeholders. You will work within a product engineering context, ensuring operational continuity, efficient triage, and a proactive stance on reducing recurring incidents.

Qualifications

• Strong debugging and systems-reasoning ability to diagnose complex distributed flows.
• Production-grade engineering in Java with an understanding of blast radius of changes.
• Excellent written and verbal communication with customers, PMs, or compliance.
• Experience with production incidents, on-call support, or customer-facing debugging.

Responsibilities

• Own resolution for customer issues end to end — reproduce, diagnose across services and dependencies, and ship fixes.
• Merge to production with tests and a rollback plan, ensuring disciplined change control.
• Protect operational continuity of your area for every customer and own domain reliability.
• Triage tickets by routing correctly and escalating when needed, without dropping the customer.
• Communicate clearly with technical customers, providing honest timelines and status.
• Drive down recurring issues and partner with TPMs on health metrics for the supported areas.

Skills

Strong debugging

Systems reasoning

Java production engineering

Excellent communication

On-call / production incidents

Tools

SQL

PostgreSQL

Job description

We're looking for first-principles thinkers who take ownership, and aren't afraid to build from scratch.

If you thrive in ambiguity, value deep learning and expertise over fluff, bring bold ideas to the table, and believe great work happens through collaboration—join us!

" Cybrilla is built by highly skilled knowledge workers who thrive on intellectual stimulation. We give them meaningful work and, in turn, they take ownership of their growth.

Satish Co-founder

" We move fast, solve hard problems and push boundaries. Cybrilla isn’t for comfort seekers. If you're driven, adaptable and ready to create real impact, this is your chance to be part of a challenging but rewarding journey.

Anchal Co-founder

" We spend a lot of time to understand our customers, build tailored solutions, and help them solve real business use cases. You will have a great time at Cybrilla if you enjoy taking work ownership and cracking complex deals.

Piyush Business & Partnerships

" There’s true freedom to experiment here — with tools, design systems, colours, and ideas. The work I do is not just about completing tasks, but about understanding the 'why' behind every decision. That kind of trust and creative space has shaped me into a better designer and developer.

Tech team

" Decisions do not trickle down through layers of hierarchy here. The co-founders are always accessible and it feels like I’m sitting right next to them, discussing ideas in real time. We're not just fixing pieces of the puzzle – we understand the business and products in their entirety.

Madhavan Tech Team

" For me, working at Cybrilla has always meant figuring things out as we go, learning by doing, and solving problems that actually make a difference. There’s a lot of trust here — space to try new things, experiment, fail, and grow. And the team? Always game for a good challenge. That’s what makes it fun.

Customer Success Team

" Problem-solving is at the core of what we do. Everyone is expected to get their hands dirty—there are plenty of challenges to tackle, and each person gets a share of the problem-solving pie.

Product Team

" We take the time to truly understand what our customers are up against and work with them to find smarter solutions for their unique use cases. When they win, we win. Through curiosity, sharp questions, and trust-building, we show up as real partners, not just a support team.

Customer Success team

" Cybrilla is built by highly skilled knowledge workers who thrive on intellectual stimulation. We give them meaningful work and, in turn, they take ownership of their growth.

Satish Co-founder

" We move fast, solve hard problems and push boundaries. Cybrilla isn’t for comfort seekers. If you're driven, adaptable and ready to create real impact, this is your chance to be part of a challenging but rewarding journey.

Anchal Co-founder

" We spend a lot of time to understand our customers, build tailored solutions, and help them solve real business use cases. You will have a great time at Cybrilla if you enjoy taking work ownership and cracking complex deals.

Piyush Business & Partnerships

" There’s true freedom to experiment here — with tools, design systems, colours, and ideas. The work I do is not just about completing tasks, but about understanding the 'why' behind every decision. That kind of trust and creative space has shaped me into a better designer and developer.

Tech team

" Decisions do not trickle down through layers of hierarchy here. The co-founders are always accessible and it feels like I’m sitting right next to them, discussing ideas in real time. We're not just fixing pieces of the puzzle – we understand the business and products in their entirety.

Madhavan Tech Team

" For me, working at Cybrilla has always meant figuring things out as we go, learning by doing, and solving problems that actually make a difference. There’s a lot of trust here — space to try new things, experiment, fail, and grow. And the team? Always game for a good challenge. That’s what makes it fun.

Customer Success Team

" Problem-solving is at the core of what we do. Everyone is expected to get their hands dirty—there are plenty of challenges to tackle, and each person gets a share of the problem-solving pie.

Product Team

" We take the time to truly understand what our customers are up against and work with them to find smarter solutions for their unique use cases. When they win, we win. Through curiosity, sharp questions, and trust-building, we show up as real partners, not just a support team.

Customer Success team

" Cybrilla is built by highly skilled knowledge workers who thrive on intellectual stimulation. We give them meaningful work and, in turn, they take ownership of their growth.

Satish Co-founder

" We move fast, solve hard problems and push boundaries. Cybrilla isn’t for comfort seekers. If you're driven, adaptable and ready to create real impact, this is your chance to be part of a challenging but rewarding journey.

Anchal Co-founder

" We spend a lot of time to understand our customers, build tailored solutions, and help them solve real business use cases. You will have a great time at Cybrilla if you enjoy taking work ownership and cracking complex deals.

Piyush Business & Partnerships

" There’s true freedom to experiment here — with tools, design systems, colours, and ideas. The work I do is not just about completing tasks, but about understanding the 'why' behind every decision. That kind of trust and creative space has shaped me into a better designer and developer.

Tech team

How We Work Together

1.

First-Principles Thinking

We dive deep and question everything. No surface-level solutions, no band-aids, no 'that's how it's always been done.' We're not here to make small tweaks - we're here to fundamentally change the game.

2.

We keep things straightforward—whether it’s code, communication, or decision-making. This helps us create an environment where trust runs deep and ideas flow freely.

3.

We approach problems with curiosity and depth, and learn through experimentation—small, iterative tests that lead to lasting solutions.

4.

Ownership

Take initiative, make mistakes, learn from them, and grow—what matters is that you're driving toward meaningful results. We value steady progress and meaningful impact over mindless hustle.

5.

We question the status quo and challenge the old ways of doing things. We’re not here to play it safe—we’re here to disrupt a 30-year-old industry and that requires bold ideas, fresh perspectives, and a challenger mindset.

6.

Shared Purpose

We trust that everyone at Cybrilla is working toward the same goal. Alignment may differ at times, but mutual trust keeps us moving forward as a team.

Our products are deep and technical, and our customers need someone who can pick up a broken transaction, reason about where it went wrong across our services and the rails beneath them, and actually fix it — not file a ticket and wait.

That's what this role is. You sit inside Product Engineering, not in a separate support silo. You're customer-facing, you debug in the real codebase, and you can merge fixes to production. Your job is to collapse the time between "a customer is blocked" and "the customer is unblocked" — and, over time, to make the class of problem stop recurring.

This is a resolution role, not a triage role. The bar is set accordingly: we hire people we trust with production access and code review, because that's what the job requires.

What you'll do

Own resolution for customer issues end to end — reproduce, diagnose across our services and upstream dependencies (RTAs, TSPs, payment and KYC providers), and ship the fix.

Merge to production under real guardrails — write the fix, get it reviewed, deploy it with tests and a rollback plan. Fixing hot under time pressure is exactly when discipline matters most, and we hold you to it.

Protect the operational continuity of your area for every customer. Each support engineer owns a functional domain — Orders, Payments, and so on — and keeps it running smoothly: an Orders engineer ensures units move cleanly, a Payments engineer ensures money moves. When a bug threatens that day-to-day operation, you're the person who keeps it from becoming an incident.

Triage cleanly and route what isn't yours. Some tickets are genuine bugs (you own these); some are "the integration behaves unexpectedly" or "we need a capability that doesn't exist" (you route these to the right owner) — always without the customer feeling dropped.

Communicate with technical customers as a peer — clear status, honest timelines, and the confidence that comes from someone who understands the system, not someone reading from a script.

Drive down recurring issues, not just close tickets. Spot the pattern behind repeated failures and either fix the root cause or make the case for the engineering investment that will. You'll partner with TPMs on operational health metrics (failure rates, latency, recurring-issue rates) for the areas you support.

What makes this role different

Most "support engineer" roles are a queue and a knowledge base. This one is genuine engineering with a customer-driven backlog. You'll write real code against a real production system, and the work you do is visible to the people who care most about the product. That proximity — to the code, to the customers, to the failure modes — is also the fastest way to learn how the whole system actually behaves under load.

What we're looking for

Required

Strong debugging and systems-reasoning ability — you can hold a distributed flow in your head, form hypotheses, and narrow down where it broke.

Production-grade engineering in Java — you can read an unfamiliar codebase, write a correct fix, and understand the blast radius of a change.

Comfort with the full production discipline: code review, testing, safe deploys, rollbacks.

Excellent written and verbal communication — the people you deal with on a customer's side might be engineers, PMs, compliance, or others, and you can articulate a technical problem in terms each of them understands, staying clear and calm under pressure.

Sound judgment about escalation — knowing what to fix yourself, what to route, and when to pull the alarm.

3–6 years of experience, including hands-on ownership of production systems — you've shipped fixes to prod and dealt with live issues, not just built features.

Strongly preferred

Experience with production incidents, on-call, or customer-facing debugging.

Familiarity with SQL / PostgreSQL for investigating data-level issues.

Exposure to fintech, payments, or regulated systems — or a demonstrated ability to get up to speed on complex domain rules quickly.

Understanding of API-driven, multi-tenant systems.

We are not looking for

Someone who wants to write only new features and never touch a customer.

Someone who wants to only talk to customers and never touch code. The whole point of this role is that it's both.

What you can expect from us

Production access and the trust that comes with it, from day one after ramp-up.

Direct line of sight to customers, founders, and the engineering leadership — your work is not buried.