Goldman Sachs

Software Engineer (Associate) 

• Worked for migration of regulatory applications to a multi-tenant architecture using scalable and distributed platforms like Kubernetes, Kafka and AWS S3. 
• Responsibilities include - 
=>Preparing solutions by determining and designing system specifications, standards, and programming.
=>Coordinating cross-team communications for effective collaboration.
=>Creating and designing implementation plans for application.

Software Engineer (Senior Analyst) 

Barclays

Experience with deployment and testing of microservices, handling the operational complexity of microservices. 
Effectively coded software changes and alterations based on specific design specifications. 
Extensive experience using and developing APIs.
Experience with AWS cloud deployments and infrastructure design. 
Worked well independently and on a team to solve problems.

Developer

Ab-Initio Developer
• Designed, developed and implemented applications based on analyzed requirements and understanding of industry technical standards.
• Revised, modularized and updated old code bases and design of Informatica to Ab-Initio to modern development standards, reducing operating costs.
• Implemented CI/CD automation tool to deploy code in different work environments.
• Collaborated with cross-functional development team members to adopt an End-To-End automation tool for detailed reporting project progress, staff management, coding errors and automated code migration activities.

Graduate Analyst

BMC Software

Project Intern
• Designed and implemented collaboratively with team members a system to predict the severity of a source code file using version control and defect tracking history.
• System consisted of required services running over Flask Server, POSTGres Database containing history of Git and JIRA associated with code file.
• Collaborated with senior leaders in creation and maintenance of project tracking tools, verifying clear communication of all inherent expectations and responsibilities.
• Wrote, modified and maintained software documentation and specifications.

Project Intern

SDE 2 @ Goldman Sachs | 16K+ LinkedIn Followers | Ex-Barclays, BMC

Hi, I'm Rohit Doshi 👋.

An innovative thinker and enthusiastic software developer with a passion for dancing ! ⭐

I possess clear understanding of fundamentals and operational activities in below technical skills :
-> Java, Python, Shell Scripting
-> MySQL, MongoDB
-> Microservices, Multi-tier Architectures
-> AWS, Kubernetes, Kafka

I have also received professional training in AWS, Machine Learning, and Data Science. ✔️

My technical expertise and problem-solving skills make me an asset to any team 🤝.

I often talk on LinkedIn with topics related to my skillset. 🔊

I enjoy sharing my knowledge and experience with others, and I'm always happy to mentor students and early-career professionals 🫱🏻‍🫲🏻.

When I'm not coding, you'll find me pursuing my passion for dance 🕺🏻, which I share on Instagram - @rohit_doshi_9 📷.

New threads profile - https://www.threads.net/@rohit_doshi_9

Thank you for taking the time to read about me 😄.

If you're interested in connecting or exploring potential collaborations, don't hesitate to reach out through DM 📩. 
I'm eager to contribute my skills and expertise to help organizations and individuals succeed 🚀.

Note - All opinions posted are of my own and not of my employer.

My friend's team is hiring AI Engineers in Goldman Sachs !

Check out these jobs below -

https://lnkd.in/gyU3Fjxa

https://lnkd.in/g6A4SxzA

https://lnkd.in/gbmwMEBK

https://lnkd.in/gNKVUdJv

https://lnkd.in/gjcB3a5M

https://lnkd.in/g89AgyjJ

#goldmansachs #hiring #ai #machinelearning #softwaredevelopment #softwareengineering

Rohit Doshi

This resume got me interviews at Amazon, MasterCard, Uber, Google, Flipkart, DE Shaw and Arcesium!

Here are the 3 key areas I focused on while creating it:
✅ Impact-Driven Projects: Highlighted work where I optimized performance, built scalable systems, and solved real-world problems.
✅ Tech-Stack Alignment: Focused on DSA, backend technologies, and system design relevant to the roles I applied for.
✅ Essential Links: Added GitHub, LeetCode, and LinkedIn to showcase my work beyond the resume.

At first, my resume wasn’t getting shortlisted. It took 6–7 iterations, plenty of trial and error, and feedback from senior engineers to finally get it right.

If you’re also struggling to land interviews despite multiple revisions, try getting your resume reviewed by senior SDEs from top PBCs. Their personalized feedback can make a huge difference. 💪
📌 Get on a FREE consultation here: https://lnkd.in/gFwxUyn3

They'll help you review and improve your resume, align it with industry standards, and tailor it for specific roles under their mentorship program. They’ll also provide insider tips and guide you through overall interview preparation. 🌟
All the best!

#resumereview #resumeoptimization #ATS #paidpartnership #jobsearch #techresumetips

SDE1(Freshers/Experienced) and Top SDE2 jobs in Amazon posted very recently!
Apply before they close out!

My personal suggestion would be to check job descriptions and apply only to the relevant openings!

Amazon is hiring for the below roles -

SDE I (Fresher), Amazon University Talent Acquisition
▪️https://lnkd.in/dvi4vwjz
▪️https://lnkd.in/dfwpK8Fb

System Development Engineer I, Amazon WWR&R
▪️https://lnkd.in/dPA73p24

Software Development Engineer II, AGI Data Services
▪️https://lnkd.in/deRt4R6P

Software Development Engineer II, Digital Acceleration
▪️https://lnkd.in/dFqz6F3Z

Software Development II, Risk Management
▪️https://lnkd.in/dE-wiFDx

Software Development Engineer 2, Prime Video App Experience
▪️https://lnkd.in/d3KUZBhT

Software Development Engineer 2, Prime Video Experience Tech
▪️https://lnkd.in/d-gPB-Df
▪️https://lnkd.in/dJCyfn4J

♻️ Repost so this can help someone!
🌟 Follow Rohit Doshi for more such updates on hiring and technology related content!

-----

#amazon #india #hiring #softwareengineering #softwaredevelopment #sde #jobs #jobsearch #tech

Have you ever retried an API call because something “just didn’t go through” ?
That’s where idempotence quietly saves the day.

In simple terms
An operation is idempotent if running it once or a hundred times gives the same result

Think of it this way :
Action is - Turning on a light switch
If it’s already ON, pressing “ON” again changes nothing.
That’s idempotence!!!

Now, why does this matter in system design?

1️⃣ Message Queues
Let’s say you’re processing events from a queue.
Your service reads a message, processes it, and crashes before confirming success.
When it restarts, it reads the same message again.
If your operation isn’t idempotent, that order might get processed twice ie. two emails, two bills or two notifications.

But if it’s idempotent, the same message reprocessed won’t cause chaos. The system stays consistent.

2️⃣ APIs
Idempotence isn’t just for backend queues but it’s built into HTTP itself.
GET — Safe and idempotent. 
Fetching data doesn’t change anything.

PUT — Replaces a resource. 
Doing it twice is the same as once.

DELETE — Removes a resource.
Deleting twice? Still gone.

POST — Not idempotent by default (creates new stuff)
But you can make it idempotent using an idempotency key which is a unique request ID that tells your backend,
“If I’ve already handled this request, don’t do it again and just return the same response”

That simple trick saves users from double payments or duplicate records.

3️⃣ Databases
Idempotence also lives in your DB layer.
UPSERT (Insert if not exists, else Update) is idempotent.
Running the same insert/update multiple times leads to the same result.
Perfect for retry logic when a DB call fails midway.


Idempotence is a safety net for your entire architecture.
It makes retries safe, systems resilient and engineers sane.

So next time you design a feature, ask yourself
“If this runs twice, will it still be okay?”

That’s where real engineering maturity begins!

♻️ Repost so this can reach the right audience!
🌟 Follow Rohit Doshi for more such posts!

-----

#systemdesign #softwareengineering #tech #softwaredevelopment #api #design #programming

If you are free this weekend and don’t have any plans, explore this HLD roadmap I’ve curated!

This will help you build a strong foundation in system design, understand trade offs and prepare better for interviews.

1️⃣ Basics of Scalability
• Horizontal vs Vertical scaling
• Load Balancers
• CAP Theorem

2️⃣ Caching
• Client-side vs Server-side caching
• CDN (Content Delivery Network)
• Redis / Memcached basics

3️⃣ Databases
• SQL vs NoSQL
• Indexing strategies
• Sharding, Replication, Partitioning

4️⃣ Networking Essentials
• DNS
• HTTP vs HTTPS
• REST vs gRPC vs GraphQL

5️⃣ Message Queues & Streaming
• Kafka, RabbitMQ basics
• Producer-Consumer model
• Event-driven systems

6️⃣ Storage Systems
• Object Storage (S3, GCS)
• Block vs File storage
• Distributed File Systems

7️⃣ Designing for Reliability
• Replication & Failover
• Heartbeats & Leader election
• Monitoring & Alerting

8️⃣ Security & Authentication
• OAuth2, JWT
• Rate limiting, Throttling
• Encryption (in-transit, at-rest)

9️⃣ Core System Components
• API Gateway
• Reverse Proxy
• Service Discovery

🔟 Case Studies (must try!)
• Design URL Shortener
• Design Instagram Feed
• Design WhatsApp / Messenger
• Design YouTube or Netflix
• Design E-commerce system (Amazon-like)

Pick one case study
→ break it into core components
→ think about data flow, scaling and bottlenecks
→ then compare with real-world implementations

---

💯 Save this post as a quick reference
♻️ Repost if you think this was useful to you!
🤝🏻 Follow Rohit Doshi for more such insightful posts!

#systemdesign #HLD #softwareengineering #softwaredevelopment #career #tech #interview #interviewtips #growth

API versioning is the hidden skill that separates juniors from becoming that one talented senior! 😎

Most freshers and even mid level engineers never think about it. They’re busy building features, fixing bugs or clearing sprint tickets.

But if you’ve ever broken someone else’s integration by “just renaming a field” you’ll quickly understand why versioning matters.

💡 Why versioning?
Think of an API as a contract.

If your contract says:
{ "id": 123, "status": "shipped" }

…your consumers (other teams, apps, or external companies) expect exactly that.

Change status to delivery_status?
→ Someone’s app might crash.

Change numbers to strings?
→ Someone’s analytics pipeline might fail.

Even small changes can ripple into production failures for clients you don’t even know about.

That’s where API versioning steps in a way to evolve APIs without leaving consumers behind.

How versioning works?
There are different strategies, each with pros and cons:

1️⃣ Path-based versioning
/api/v1/orders → /api/v2/orders
Clear and easy but pollutes URLs and forces you to maintain multiple versions.

2️⃣ Query parameter versioning
/api/orders?version=2
Keeps the path stable but complicates caching and routing.

3️⃣ Header based versioning
GET /api/orders  
api-version: 2
Or via media type headers 
(Accept: application/vnd.github.v2+json)
Cleaner URIs but harder to debug and cache.

4️⃣ Payload versioning
Include version inside the request/response body. Useful in event-driven systems where data is replayed years later. Not ideal for normal REST APIs.

📌 When to bump a version?
Not for every deployment.
Only when the API contract changes in a way that breaks clients.

✅ Adding optional fields? No new version.
❌ Removing/renaming fields? New version needed.
✅ Fixing bugs internally? No version bump.
❌ Changing response formats? Definitely new version.

Notice the pattern? 
Both prioritize client stability over “quick hacks” 

Also the truth is versioning won’t make your code run faster today.
But understanding it will make you stand out tomorrow when you’re asked to design APIs for teams, clients or millions of external users.

Because at senior level, breaking APIs = breaking trust 💔

---

♻️ Repost if you think this was useful to you!
🫱🏻‍🫲🏻 Follow Rohit Doshi for more such insightful posts!

Image Credits - Nikki Siapno/Level Up Coding
#systemdesign #api #versioning #softwareengineering #softwaredevelopment #career #tech

We spend years learning and implementing these concepts!


✅ Clean code
✅ Design patterns
✅ Architecture principles
✅ Best practices

And yet… sometimes we get stuck debating things like
➡️ “Should we use Strategy Pattern here or Factory?”
➡️ “Is this function name perfectly descriptive?”
➡️ “What if in the future we scale to 100M users?”

Meanwhile, the deadline stares at us…
and the feature isn’t even shipped 😅

This is where overengineering sneaks in.
It’s not about writing bad code vs. good code. It’s about losing sight of balance.

A few reminders I’ve learned along the way -
• Design principles are tools and not rules.
• Shipping value matters more than perfect abstractions.
• Solve today’s problem not an imaginary one from 5 years later.
• Over-optimizing early can make systems harder to maintain.

The best engineers I’ve worked with know when to go deep and when to keep it simple.

Good enough today > Perfect and never delivered

So the next time you catch yourself endlessly refactoring for elegance

Ask 
“Does this change actually improve outcomes for users and teammates?" 
"Or just my ego as an engineer?”

Because at the end of the day, shipped code > beautiful slides 🚀

---

♻️ Repost if you think this was worth your time!
🤝🏻 Follow Rohit Doshi for more such posts!

#career #growth #systemdesign #softwareengineering #softwaredevelopment #humour #meme

Your potential isn’t scary because it’s impossible.
It’s scary because deep down, you know it’s possible.

You’ve seen glimpses in those rare moments when you went all in.
And you’ve felt the quiet weight of knowing you’re capable of more.

That’s the real fear.
Not failure.
But the gap between the life you’re living and the life you could be living.

It’s like owning a Ferrari and never shifting out of first gear.
Every day you stay in that gear, you feel it.
Heavily.

But here’s the thing - your next level is waiting.

Not out of reach. 
Not someday. 
Right now.

So stop playing small.
Go all in.
Show up.

P.S. I should titled the post as "HIGH MOTIVATION ALERT 🚨"
---

♻️ Repost if you think this can help someone!
🫱🏻‍🫲🏻 Follow Rohit Doshi for more such posts!

#career #growth #growthmindset #consistency #learning #motivation

Taplio

Rohit Doshi's Linkedin Analytics

Rohit Doshi

Performance ScoreRohit Doshi's LinkedIn Performance

Rohit Doshi's Best Posts (last 30 days)

Ready to grow your LinkedIn presence?

Taplio

.css-6ytdur{background-image:linear-gradient(284deg, rgba(39, 43, 72, 1) 0%, rgba(33, 47, 183, 1) 100%);color:transparent;-webkit-background-clip:text;background-clip:text;}Rohit Doshi's Linkedin Analytics

Rohit Doshi

Performance Score.css-goub6s{font-size:var(--chakra-fontSizes-md);font-weight:500;color:var(--chakra-colors-gray-600);display:block;margin-top:var(--chakra-space-1);}Rohit Doshi's LinkedIn Performance

Rohit Doshi's Best Posts .css-1emoo84{font-size:var(--chakra-fontSizes-md);font-weight:400;color:var(--chakra-colors-gray-600);}(last 30 days)

Ready to grow your LinkedIn presence?

Rohit Doshi's Linkedin Analytics

Performance ScoreRohit Doshi's LinkedIn Performance

Rohit Doshi's Best Posts (last 30 days)