Principal Engineer

Summary

Currently, my time as an architect is equally split into achieving two broad objectives -
- Deliver artifacts from designs to algorithms to implementations.
- Adopt an event-first strategy for architecting and operating the applications and services including where integration is required with outside entities.
- Which applications are the best candidates for event-driven integration? Are there event streaming use cases where your organization is likely to integrate with another organization?
- Balance between building the right thing vs the time thing vs the proper thing.
- Gauge what product features needs to be designed right now and what can be deferred to the future.
- Finding and advocating for the most important problems that need to be solved.
- Solving fuzzy organizational problems.
- Factor out common libraries and services as needed.
- Manage design complexiy and provide paved paths(common development frameworks)

Talking about my time with product features, it involves collaborating with the product managers to brainstorm
and come up with revenue generating features, their scope and timelines. Here I need to provide answers to the
questions like - out of the N features, which one is technically feasible within the timelines ? Will our
current architecture scale or we need to some foundational work first. This is where I need to make some
tradeoffs from among the 3-dimensions (fast/cheap/quality). This also involves coming up with POCs/socializing
the decisions with the broader team/taking them into confidence, etc

Fuzzy organization problems are like a one liner - making our services more resilient or reduce the occurrence
of field incidents. Then I need to dig deeper my collaborating with domain experts in their silos and break this down
into smaller and more relatable problems like - we need proper DR, we need faster code delivery, we need to
move to a newer infrastructure problem. There are tradeoffs to be made here too - build versus use a managed service.

In both of these endeavours, I am focussed on
a) Make the system more valuable for each user,
b) Help grow the number of active users,
c) Make the system last longer,
d) Make the system generate more revenue, and reduce the cost of maintaining and running the system.
a) Lead opportunities for optimization & automation
b) Enforcing standards sensibly.

[N.B]: "If what your project really needs to be successful is for someone like me to come in and write 50k lines of code, I can do that,". But I find that when a large project is off track, it's rarely for a lack of coding velocity. It's a lack of consensus, direction, customer buy-in, system architecture, or interlock. Those are the things I put the bulk of my energy into creating.

None of the artifacts for those issues get committed to github.

Success stories from the past two years until now
-------------------------------------------------
1) Led the design and implementation of a cloud-based data platform (real-time and batch) to process high-velocity (of the order of thousand
transactions per second) and analyze large data sets (of the order of GB's) to drive key actionable insights & solutions across the organization.

2) Led the design and implementation of an orchestration platform for improving the resiliency and disaster recovery for hundreds of critical services.

Expectations

Looking for opportunities to own, design, implement end to end systems.

Employment Preferences

Expected Base Salary

*,*00,000 INR

Expected Total Compensation

**,000,000 INR

Academic Degree

Experience

Skills

• Java
• Kafka
• AWS
• System Design