Matching exceptional talent with companies that value substance over stories.
Y.R.K.
Platform Architect
Backend engineer turned platform architect with proven track record scaling fintech systems from zero to millions of users
🧠 How they think
• He approaches problems with a clear business-first mindset, consistently tying technical solutions back to measurable outcomes and KPIs throughout our conversation. This wasn't just lip service - when discussing building systems for longevity, his first instinct was to validate the business case before diving into technical architecture.
• His thinking is notably structured and systematic. When describing complex technical challenges like the Account Aggregator system or the audience management platform, he naturally broke down problems into logical components and explained the progression from zero to scale in clear stages.
• We found his approach refreshingly pragmatic. Rather than chasing shiny new technologies, he advocates for simple, standardised architecture that can solve 99% of problems. He thinks in modular terms, comparing his ideal systems to Lego blocks that can be plugged and played anywhere.
• He demonstrates genuine first-principles thinking when it comes to platform decisions. His willingness to spend extra time building reusable components rather than quick fixes shows he considers the broader implications of technical debt and future scalability needs.
⚡️ Fast facts
EDUCATION
B.Tech ICT from DA-IICT, Gandhinagar with 9.0 CPI
INDUSTRY EXPERTISE
Artificial Intelligence, Machine Learning, Financial Services, Fintech, Cloud Computing, Data Analysis, Enterprise, SaaS
YEARS OF EXPERIENCE
7.5+
EXPERIENCE WITH TOOLS
Scala, Python, Java, JavaScript, SQL, AWS, Elasticsearch, Pinot, GraphQL, Kubernetes, Docker, Redis, Kafka, Spark, Tensorflow, Airflow
NOTICE PERIOD
2 months
PRIORITIES FOR NEXT ROLE
Competitive compensation, Great colleagues, Career growth
HEAR THEM IN ACTION
💪 What drives them
• He's genuinely energised by the craft of engineering itself. When discussing his career moves, it was clear he left Morgan Stanley specifically to get into tech because that's where his passion lay, not for external factors like compensation or prestige.
• Building systems that scale excites him immensely. The way he described growing the Account Aggregator from zero to 300k users or the audience management platform serving 40 million requests daily showed genuine pride in creating something that handles real-world scale.
• He's motivated by solving problems that matter. His emphasis on ensuring there's a real business case before building anything suggests he wants his work to have genuine impact rather than just technical elegance.
• The systematic approach to his side projects - posting on Reddit for validation before building - shows he's driven by creating things people actually use, not just building for the sake of building.
😇 Understanding of self
• He demonstrated genuine self-awareness when discussing his learning curve around team dynamics. His admission that he initially expected everyone to perform at his capability level, and his conscious effort to build processes that accommodate different skill levels, shows real introspection and growth.
• The way he described learning that not everyone loves their work like he does was particularly honest. This wasn't a surface-level answer about work-life balance - it was a fundamental realisation about human motivation that required him to reset his expectations and management approach.
• He was refreshingly direct about writing off his Jupiter ESOPs rather than maintaining unrealistic optimism, suggesting he can assess situations objectively even when it concerns his own interests.
• However, when pressed on personal development areas, his responses focused more on external adaptations rather than internal skill gaps. We would have liked to hear more about specific technical or leadership skills he's actively working to improve.
📣 Communication style
• He communicates with impressive clarity and structure, naturally organising complex technical concepts into logical progressions. When explaining the Account Aggregator system, he moved seamlessly from the regulatory framework to technical implementation to business outcomes.
• His explanations balance technical depth with business context beautifully. Rather than diving into pure technical details, he consistently framed solutions in terms of user impact and business metrics, making him easy to follow for both technical and non-technical audiences.
• We noticed he's comfortable admitting uncertainty ('I forget the exact term, I'm sorry for that') rather than trying to bluff through gaps in recall, which suggests intellectual honesty and confidence.
• His communication has a nice conversational flow - he doesn't sound rehearsed or overly formal, yet maintains professionalism throughout. This suggests he'd be effective in both technical deep-dives and stakeholder presentations.
⚠️ Potential risks
• His current role involves managing teams from tier 3/4 colleges as a cost optimisation strategy. While he's adapted well to this, there could be questions about whether he'd struggle transitioning back to working with uniformly high-calibre engineering teams where his current management approach might need adjustment.
• He mentioned writing off his Jupiter ESOPs mentally, which suggests either the company hasn't performed as expected or there are liquidity concerns. This could indicate some risk assessment issues or perhaps just realistic expectations about startup equity.
• While his technical breadth is impressive, his recent focus on platform architecture might mean his hands-on coding skills could need refreshing if moving to a more IC-focused role.
• His strong preference for loving work might create unrealistic expectations for team members who view their roles more transactionally, though he seems to have learned to manage this.
🧑🎨 Life beyond work
• He follows sports regularly, particularly cricket and tennis, though he was honest that his interest in tennis has waned since the 'big four' era ended.
• His weekend side projects show genuine entrepreneurial drive beyond just technical curiosity. The systematic approach - building things, testing with users, posting on Reddit for validation - indicates he's treating these as potential business ventures rather than just hobby coding.
• Notably absent were typical tech industry extracurriculars like open source contributions or technical blogging, despite his impressive publication record during university. This might indicate he channels his creative energy more into building products than sharing knowledge publicly.
🥵 Toughest problem solved
• The Account Aggregator system at Jupiter stands out as his most complex technical achievement. Building this RBI-backed framework from scratch to handle user-consented financial data access, scaling it to 300k users with 700k daily transactions, while being among the first industry adopters working directly with regulatory bodies, required both technical sophistication and business navigation skills.
• The audience management platform demonstrated his ability to architect for extreme scale - serving 40 million requests daily with 99.9% uptime while processing 5 million events. What impressed us most was his focus on the business impact: 'saving countless dev hours' rather than just technical metrics.
• His current challenge of optimising team performance with engineers from tier 3/4 colleges shows his evolution from pure technical problem-solving to people and process challenges. The way he described creating structured approaches to get consistent output despite varying skill levels suggests strong systems thinking applied to human challenges.
• Throughout these examples, he consistently focused on outcomes and business impact rather than just technical complexity, which indicates a mature approach to problem-solving.