TechGrove is the Centre of Excellence for Banyan Software, based in Chennai, India. It plays a key role in supporting Banyan's global businesses through technology, security, and software development. TechGrove brings together India's deep pool of technical talent with Banyan's long-term approach to growth, creating a trusted, developer-focused environment where people can do their best work.
About the role
TDMS is a post-trade reconciliation and settlement platform used by institutional asset managers, and it is entering a significant modernization. This role leads the engineering of it: an AI-first effort to re-architect how the platform is built, deployed, and scaled, on a system that real money settles through every day.
That is also what sets the bar. Settlement accuracy is the product, and a single mis-settled trade is a client-loss event, so the engineering judgment we expect here is high.
This is a build-heavy, high-ownership role at the technical center of the platform. You will own the cloud architecture, the delivery automation, the engineering standards, and the technical execution of the modernization that carries TDMS through its next phase of growth. You will work agentic-coding-first from day one. That is table stakes here, not a bonus: you use agentic tools to deliver well beyond traditional hand-coding throughput, and you read, validate, and stand behind everything that ships. You do not need to be a lifelong C# / .NET expert, but you do need to read C# / .NET fluently, reason about it, and guarantee its quality.
The role carries both sides of the work. You keep the current application healthy in hands-on, day-to-day operations, including the unglamorous parts, while steadily applying modern engineering to it. The migration runs over the coming months, so expect what you do day to day to evolve: the agentic-coding way of working is constant from the start, while the architecture, deployment model, and tooling change as the migration progresses.
You report to the Chief Product and Technology Officer and partner closely with the Head of Development. You will also work with and level up a small, distributed team of engineers across India and the US.
What you will do
Architecture and scale
- Own the platform architecture. Set and drive the target architecture for a cloud-native platform: a load-balanced, stateless application tier over a managed data tier, evolved through coexistence and monitored cutover rather than a single rewrite. New capabilities run in parallel with the paths they replace, and legacy paths are retired only once monitoring confirms traffic has moved.
- Drive a clean service-oriented design. Lead the application architecture toward services that are testable, independently deployable, and independently scalable.
- Own the data platform. Lead schema design, data architecture, performance, and any migration work on PostgreSQL (Aurora), protecting data integrity at every step.
Cloud and infrastructure
- Own the cloud architecture. Lead the platform's architecture on AWS, including managed PostgreSQL (Aurora), load balancing, networking, and managed services.
- Treat infrastructure as code. Stand up reproducible, version-controlled environments rather than hand-built servers.
CI/CD and delivery engineering
- Own CI/CD and delivery automation. Build and own automated build, test, and zero-downtime, progressive deployment (canary, blue/green, rolling) end to end, with feature flags as the default way to decouple deploy from release.
- Set the source-control standard. Establish trunk-based development on GitHub with short-lived branches, squash-merge, and mandatory peer review.
AI-assisted (agentic) development
- Work agentic-coding-first. Agentic coding (Claude Code, GitHub Copilot, and similar) is your default development methodology, not an occasional assist. You set the standard for what strong agentic-assisted engineering looks like here.
- Bring the team up the curve. The rest of the team is still learning these tools and will lean on you. Coach them, pair with them, and establish the patterns that make agentic coding productive and safe.
- Set the guardrails. Define how AI-assisted code is reviewed, tested, and trusted on a mission-critical settlement codebase, so speed never comes at the cost of correctness.
Quality, observability, and reliability
- Own end-to-end observability. Lead application performance monitoring, error tracking, and product analytics across the stack, so the team builds and operates on real signal rather than guesswork.
- Support the live platform. Take part in day-to-day operations, support, and incident response for the production system, and fold modern practices into it as you go rather than waiting for a finished rebuild.
- Own production confidence. Lead automated testing, root-cause analysis, and durable fixes for complex production issues.
- Design for resilience. Build fault tolerance and self-healing into the platform so it degrades gracefully and recovers without manual intervention.
- Roll out carefully. Stage and guard every change that expands the surface area for settlement error.
Technical leadership
- Set the technical direction. Own the architecture and the engineering standards for the platform: the coding, review, branching, testing, and quality practices the team works to, and hold the bar.
- Raise the team. Mentor the engineers across our India and US teams and deepen their strength in modern cloud, delivery, and AI-assisted practices, so platform knowledge is shared across the team rather than concentrated in any one person.
- Solution with the team. Work closely with the CPTO and the wider team to turn product and platform direction into technical execution, contributing to shared solutioning while the overall vision is set at the CPTO level.
What we are looking for
- Typically ten or more years building and operating production software, though we weight demonstrated skill over years on a resume. You read C# / .NET fluently and can review, validate, and reason about it, since agentic tools will generate much of the code and you are accountable for its correctness. Lifelong .NET specialization is not required.
- A track record architecting and scaling complex production systems, including incremental modernization of established codebases through coexistence and parallel-run patterns, with data-driven deprecation of legacy paths once traffic has moved over. Service decomposition and cloud-native design experience expected.
- Hands-on experience designing microservices and building and deploying containers, with a strong grasp of architecture patterns and scalability tradeoffs.
- Strong distributed-systems fundamentals: event-driven architecture with pub/sub and message queues, API gateways, and designing for fault tolerance and self-healing.
- Strong hands-on AWS and/or Azure: managed databases, load balancing, networking, and managed services, with infrastructure as code.
- You have built CI/CD pipelines from scratch, including automated testing and zero-downtime, progressive deployment (canary, blue/green, or rolling), and you have used feature flags in production.
- Relational database depth and hands-on data migration (SQL Server and/or PostgreSQL).
- A performance mindset and excellent troubleshooting skills: reasoning about time complexity, profiling, tuning, and optimization, and running disciplined root-cause analysis under production pressure.
- Agentic coding is table stakes, not a nice-to-have. Deep, hands-on fluency with agentic tools (Claude Code, Copilot, Cursor, or similar) as your primary development methodology in real production work, from day one, plus the ability to bring a learning team up to speed on them.
- Git and modern branching practice (trunk-based development), with GitHub experience.
- Comfort owning quality on a system that cannot fail quietly: disciplined testing, observability, and careful, staged rollout.
Nice to have
- Experience in financial services or another regulated, high-stakes domain. Post-trade settlement, DTCC ITP (CTM, ALERT, TradeSuite), SWIFT MT5xx, or FIX is a strong plus but is not required. We will teach the domain to the right engineer.
- React with TypeScript on the front end.
- Workflow-engine experience (Temporal or similar).
- Building software under SOC 2 or comparable regulated-environment controls.
- Exposure to vector databases, and to a lesser degree graph databases, is a plus. Both are on our roadmap for the coming year rather than day-one needs.
How you work
You are a strong hands-on coder who also sets direction for the platform. You are pragmatic about sequencing modernization so it ships value early and never breaks a live system. You make the engineers around you better through your standards, your reviews, and your judgment, rather than hoarding the hard work, and you communicate clearly with technical and non-technical partners alike.
Why you'll want this
- Real ownership on a small team. Your decisions ship and your ideas are heard, instead of getting lost in the layers of a large organization.
- The work itself: lead an AI-first modernization of a mission-critical platform, and set the standard for how the whole team builds with agentic coding.
- Remote, anywhere in India.
Our culture
We are a small, capable team that cares deeply about the work and about each other, and we challenge each other directly, because that is how good engineering happens. We work closely together, we celebrate our wins, and we stay blameless in our losses. When something breaks, we fix it and learn from it rather than point fingers.
Beware of Recruitment Scams
We have been made aware of individuals fraudulently posing as members of our Talent Acquisition team and extending fake job offers. These scams may involve requests for personal information or payment for equipment.
Protect yourself by following these steps:
- Verify that all communications from our recruiting team come from an @banyansoftware.com email address.
- Remember, employers will never request payment or banking information during the hiring process.
- If you receive a suspicious message, do not respond — instead, forward it to [Confidential Information] and/or report it to the platform where you received it.
Your safety and security are important to us. Thank you for staying vigilant.
