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.

This is a shame.

Yesterday someone reached out and repeatedly tried convincing me to take Amazon’s online assessment for them.
Asking me to CHEAT so they could get a foot in the door.

I don’t know what’s happening with the new wave of students and aspirants.

Everyone wants the tag.
The swag.
The salary screenshot.
The LinkedIn announcement.
But no one wants the grind
(Thanks to influencers who said that 15 questions are enough for DSA)

And it’s not funny.
It’s not “just help bro”
It’s disrespectful to the company, to the people working hard and to yourself.

Let me be clear!
I’ve failed so many interviews
I’ve had rejections BACK TO BACK
I’ve questioned myself multiple times

But NEVER NEVER NEVER did I think of cheating my way into a company or for that matter BEGGING for such an unethical thing.

To students reading this

Please stop chasing shortcuts.
Please stop assuming there is a hack to everything.
Please stop expecting others to build your career for you.

Work.
Show up.
Practice.
Build.
Fail.
Retry.

The satisfaction of earning a role through your own hard work hits differently and you’ll know that feeling only if you actually put in the effort.
If you cheat to get in, the job will expose you faster than any interview ever could

Do better. Earn it.
Make yourself someone companies want to hire!

My DMs are open for career guidance.
Not shortcuts.

#cheating #students #hiring #jobsearch

Rohit Doshi

People clap at the result, not the process.

They don’t see
▪️The rejections
▪️The late nights
▪️The doubt
▪️The failures
▪️The days you wanted to quit but didn’t

But here’s the good part, YOU see it.
And the person you’ll become through that consistency will always matter more than the applause.
The ones who win are the ones who show up especially on days they don’t feel like it.

If you’re working toward something, start with the basics
🔹 Fix your resume and portfolio
🔹 Apply to roles even if you don’t feel 100% “ready”, a 60-70% works
🔹 Build a small project or proof of work
🔹 Learn skills your future role needs
🔹 Network i.e. talk to people who are already where you want to be
🔹 Be consistent! even if it’s just 30 minutes a day

Keep going and one day the same people who doubted you will ask how you did it.

And that day you’ll know
It wasn’t luck!
It was consistency!

#motivation #career #growthmindset #tech #consistency #learning

I don’t forget people just like that.

People who
✔️ Pushed me when I doubted myself
✔️ Backed my work when I wasn’t present
✔️ Shared my content without asking me
✔️ Helped me navigate interviews and roles
✔️ Recognized the effort behind the scenes and not just the output
✔️ Told leadership “He deserves a seat at the table”

Some people genuinely changed my journey without asking for anything in return.

Because of them, I make an effort to do the same for students, juniors, peers or whoever needs a push!

While doing all of this, I’ve been reminded of one thing that you don’t grow alone.
And not everything we learn in tech has to be technical.
Sometimes the biggest unlock is support, empathy and access.

If someone has done this for you, thank them today!

And if you haven’t been that person yet, what are you waiting for? Start now!

Sometimes a career changes because someone believed before you did💙

✨ Follow Rohit Doshi for more motivation in your life!
♻️ Repost if you think this is useful!
---
Image Credits - Jean Kang 🔥

#career #growth #leadership #mentorship #tech

SDE1(Freshers/Experienced) and 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/gQ2aziVt

Software Development Engineer, AFFS
▪️https://lnkd.in/gdtCW3Gq
▪️https://lnkd.in/ga3NNYYT

Software Development Engineer II, Alexa MultiModal Initiatives
▪️https://lnkd.in/gQG8Uh9k

Software Dev Engineer II, Identity Services
▪️https://lnkd.in/gNJUVuZP

Software Development Engineer II, Amazon MGM Studios Tech
▪️https://lnkd.in/gA63zrQT

Software Development Engineer 2, Prime Video Playback Operations Tech
▪️https://lnkd.in/g4UGSQcB
▪️https://lnkd.in/gV46P3ME

Front End Engineer-2, Alexa Smart Home
▪️https://lnkd.in/gV3UVQZg

Software Dev Engineer II
▪️https://lnkd.in/gZssZG_e


♻️ 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

You might have faced these questions in your interviews:

“What if payments fail three times?”
“How do you handle refunds or promo codes?”
“What happens when a billion rows pile up and you need to add a new column?”

Most candidates try to answer these by jumping straight into code or tools.

But these questions aren’t about tools.
They’re about thinking like a system designer.
Let's deep dive into each of them.

1. “What if payments fail three times?”
This isn’t just retry logic.
Interviewers want to hear:

 • Retry with exponential backoff
 • Idempotency keys to avoid charging twice
 • Circuit breaker pattern if downstream payment gateway is down

Fallback flow: save order as “Pending Payment”, notify user, allow manual retry
The key idea here being a failed payment should not break the user or the system.

2. “How do you handle refunds or promo codes?”
Here they’re testing your understanding of business logic + data consistency.

Good structure would look like

 • Audit trail: Refund shouldn’t delete the original record but it should create a reverse financial transaction.
 • Validation rules: Promo codes expire, have limit usage and must be stored with metadata (region, user eligibility, etc.)
 • Event-driven flow: OrderPlaced → RefundRequested → RefundProcessed → UpdateInvoice

The concept they want to hear is about treating financial transactions as immutable ledgers, not editable rows.

3. “What if you need a new column in a billion-row table?”
This tests your understanding of scaling + reliability.

Key points to mention here are

Zero-downtime migration strategies
Shadow writes & feature flags
Backfill with batch jobs
Schema evolution instead of schema rewrite

Schema changes in production require planning, phasing and safety nets not a single ALTER TABLE.

Interviews aren’t testing how fast you answer.
They’re testing how deeply you think.
And thinking at scale is a skill not a shortcut.

Save this post.
It’ll help when the next “What happens if...” interview shows up 🙂

Repost it to spread knowledge ♻️
Follow Rohit Doshi for more such posts !

---
#systemdesign #tech #softwareengineering #softwaredevelopment #growth #mindset #learning

I went from SDE at Barclays → VP Engineer at Goldman Sachs → now Senior SDE at Amazon after 6 yrs…

And when I look back at my own journey, 1 thing stands out clearly 👇

🔸 People will always have opinions. And most of the time, they’re loudest when you are quietly putting in the work.

I remember hearing the same things over & over again while I would prep:

“Why are you practicing LeetCode every day?”
“Why work on side projects when you already have a job?”
“Who even reads your Medium blogs?”
“Why network so much on LinkedIn?”

People laughed. People judged. People assumed it was “too much.”

But here’s the truth I’ve lived 👉 These small, consistent habits are exactly what change careers!

Those who were mocked for putting in extra effort?

They’re the ones who broke into MAANG-level PBCs, switched to leadership roles, built startups, or became the go-to experts in their field.

Because opinions won’t get you through your next interview.

In tech, and honestly, in life, your prep is your parachute.

The late-night debugging sessions? They teach grit.
That side project? It speaks louder than a 2-page resume.
That extra hour of System Design? It might be the exact reason you clear your next round.

And if you’re an SDE that’s built the experience & is aiming to switch to more senior roles at top PBCs, I’d highly recommend trying EVOLVE by Bosscoder Academy.

🔗 Explore EVOLVE here: bcalinks.com/3DYdkTW 

They’ve helped 2200+ engineers crack top PBC roles through:
💡 Structured curriculum to help you master DSA, System Design, and AI
💡 Real world, AI-powered projects & 24/7 doubt-solving
💡 Leadership skills for Senior roles with 1:1 mentorship from industry experts
💡 Resume reviews, mock interviews, and 100% job switch support.

#tech #jobswitch #leadership #seniorsde #motivation #pbc

My community has crossed 50,000 people on LinkedIn
And I keep thinking if each one of us shares even ONE useful idea, this platform becomes the biggest classroom we ever had.

1. Talking to students taught me patience

Every time I visit a college or respond to a student’s DM, I learn something new.
Their curiosity reminds me what pure learning looks like.
Their doubts force me to explain things more clearly.
Their energy teaches me to stay calm and grounded.

2. Talking to fellow creators taught me consistency

People think content creators compete.
We actually help each other survive.
Ideas, feedback, motivation, late night “this post will flop?” messages.
A single comment from a creator friend sometimes teaches me more than a full guidebook.

3. Talking to seniors taught me direction

Every conversation with someone more experienced than me resets my perspective.
They don’t just teach you skills.
They teach you how to think.
How to navigate your role, how to prepare for the next one, how to stay sane while doing it.

And that’s the power of a network.

Not for referrals.
Not for shortcuts.
But for wisdom.

---
♻️ Repost if you found it relatable!
🌟 Follow Rohit Doshi for more !

What exactly makes a good REST API?
(Simple checklist for beginners!)

REST APIs are everywhere. But designing them well?
Not everyone gets that right.

1️⃣ Treat paths as resources, not actions

A URL should always represent a thing.

✔ GET /items
✘ GET /items/getItems

✔ DELETE /items/{id}
✘ /items/delete-item/{id}

The HTTP method defines the action.

2️⃣ Use plural nouns in paths

Follow common conventions.

✔ /users/{id}/profile-picture
✘ /user/{id}/profile-picture

Helps with consistency across teams & large codebases.

3️⃣ Use the right HTTP method
A quick mapping about when to use what would look like

GET -> Fetch resource
POST -> Create new resource
PUT -> Update entire resource
PATCH -> Update partial resource
DELETE -> Remove resource

Same path but different intent.
Example:
GET /users/{id}/profile-picture
DELETE /users/{id}/profile-picture

If you follow just these 3 rules…

✔ Resource-based paths
✔ Plural naming
✔ Correct HTTP methods

You already have a clean, beginner friendly REST API.
Even many senior engineers miss these basics.
You’ll need it in your next API design or interview.

If this helps repost it ♻️
Follow Rohit Doshi for more such posts !

Image Credits - ByteByteGo
---
#api #systemdesign #tech #softwareengineering #softwaredevelopment #growth #mindset #learning

Not everyone needs a mentor. 
But everyone deserves one.

Early in my career, I didn’t think much about mentorship.
I figured I’d just learn things by doing.
Read the docs, write some bad code, debug at 2am, repeat.

And to be fair, it worked. But it was slow. And lonely at times.
The real cost? 

I had no idea how much faster I could’ve grown just by talking to someone who’d been there.

Now that I’m on the other side of the table, I try to show up for people in the way I didn’t know I needed.

Not with perfect answers
👂But by listening!
❓By asking the right questions!
👁️By pointing out blind spots they might not see yet!

Most people don’t ask for a mentor.
🔹Not because they don’t want one, but because they don’t know they can!
🔹Sometimes all it takes is someone noticing!
🔹Someone reaching out first!

So when I see someone trying hard, I let them know I see it.
👉🏻If I notice someone struggling, I check in.
👉🏻It’s not about formal mentorship.
👉🏻It’s just being human.

If you’re in a place where you can guide someone, even a little, do it.

You don’t have to be a “mentor” to make an impact.

Sometimes, a 10-minute chat is what changes someone’s week.
Or their mindset.
Or their path.

What’s the best advice you got early in your career?
Still remember it?

#mentor #life #career #softwareengineering #learning #growthmindset

Some Mondays feel like a fresh start.
Others feel like a punch in the gut.

If today feels heavy… you’re not alone.

You don’t have to wake up supercharged.
You don’t have to pretend everything is perfect.
You don’t need a “5 AM routine” to earn success.

You just need one thing today:
Show up!

Show up for your goals.
Show up for the version of you that refuses to settle.
Show up even if the effort is 50% because 50% still beats 0%.

Growth isn’t loud.
It’s quiet steps.
Small wins.
Choosing not to quit especially when quitting feels easier.

So drink water.
Take a deep breath.
Open the laptop.
Start the task.

You don’t have to be the strongest today.
Just be present.

Happy Monday 🌟

#monday #motivation #growth #mindset #learning #culture

Designing a Hotel Booking System(LLD)

While working on system design problems, I recently came across a thoughtful low-level design breakdown of a hotel booking engine.

Below is how I’d explain it if I were designing from scratch.

✅ Core requirements you must always get right

 • Search & filter hotels by location, date range, room type, price range.
 • Real-time availability check so no two users book the same room at the same time.
 • Booking flow with payment state tracking like Pending → Completed → Refunded/Cancelled.
 • Support for cancellation policies and booking modifications.
 • Dynamic pricing or seasonal price adjustment support.

Any hotel booking system or indeed any transactional system needs these features solidly covered before even thinking about bells and whistles.

🧱 What a clean “low-level design (LLD)” approach teaches

From the article I read recently, I learned how powerful OOP + SOLID-driven design can be even before involving databases or UI.

𝐒𝐞𝐩𝐚𝐫𝐚𝐭𝐢𝐨𝐧 𝐨𝐟 𝐜𝐨𝐧𝐜𝐞𝐫𝐧𝐬:
Booking logic, pricing logic, availability checks, user roles (customer, hotel-manager, admin) were all neatly separated, making code easier to test and extend.

𝐂𝐨𝐧𝐜𝐮𝐫𝐫𝐞𝐧𝐜𝐲-𝐬𝐚𝐟𝐞 𝐛𝐨𝐨𝐤𝐢𝐧𝐠 𝐥𝐨𝐠𝐢𝐜:
When multiple people try to book the same room simultaneously, locking, or careful conflict-resolution is essential to prevent double-bookings.

𝐄𝐱𝐭𝐞𝐧𝐝𝐚𝐛𝐢𝐥𝐢𝐭𝐲:
Designing room inventory, pricing strategy, booking states in a way that adding features like discounts, cancellations, waitlists becomes easier later.

In short, a well thought out LLD gives you a foundation that stays stable even when your app grows.

If you’re a fresher or junior dev, here’s what you gain from studying such designs:

 1. Better OOP / SOLID fundamentals helps beyond this project.
 2. Understanding concurrency & real-world edge cases immediately.
 3. Awareness about modular design, separation of concerns, and maintainability.
 4. Readiness for system design interviews where you might be asked to build systems like booking engines, inventory systems, etc.

♻️ Repost if you found it useful !
🌟 Follow Rohit Doshi for more such posts !

---
Source - https://lnkd.in/g2S4FEwx

#lld #systemdesign #tech #softwareengineering #softwaredevelopment #growth #mindset #learning

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)