Adobe, Atlassian, Intuit, Uber and Global Product Companies: Hiring Process

The group in this guide

Beyond the very largest technology firms, many well-known software and internet companies hire engineers in India: Adobe, Atlassian, Intuit, Salesforce, Uber, PayPal, Visa, Mastercard, Walmart Global Tech, ServiceNow, Workday, Nutanix and others. Their products range from creative tools to payments to developer software. Their hiring processes share a family resemblance: strong coding rounds, some design, and serious attention to behaviour and values.

A typical flow (with variations)

Based on what candidates commonly report; the exact steps change by company, team and level:

1. Application, referral or campus shortlisting. Referrals help significantly at product companies (referral templates).
2. Online assessment (often for freshers and some experienced roles): two or three coding problems in a timed environment (online assessment tips).
3. Recruiter or manager screen: your background, motivation and logistics.
4. Technical interviews (two to four rounds):
   • Coding / data structures and algorithms: medium problems, sometimes hard
   • Low-level (object-oriented) design or a machine-coding style exercise, especially for earlier-career roles
   • System design for experienced engineers
   • Domain depth: frontend, backend, data or mobile, depending on the role
5. Behavioural or "values" interview: many of these companies explicitly assess collaboration, ownership and how you work with people. Atlassian, for example, is widely known to include a values-focused conversation. Prepare to give concrete examples.
6. Hiring manager round and offer discussion, with background checks.

What interviewers look for

• Correct, clean, tested code and clear communication while solving
• Problem solving under ambiguity: asking clarifying questions and handling follow-ups
• Design thinking: trade-offs, extensibility and scale, depending on level
• Collaboration and ownership: the examples you give about teams, feedback and mistakes
• Craft and curiosity: whether you care about quality and users

Preparation plan (10–12 weeks)

Weeks 1–6: algorithms. Work through the DSA study plan, concentrating on arrays, hashing, trees, graphs, heaps and basic dynamic programming (dynamic programming guide).

Weeks 4–9: design. Learn object-oriented design with SOLID and common patterns (guide), and practise machine-coding exercises such as a parking lot, a rate limiter or a splitwise-style expense tracker. Experienced candidates should add system design basics.

Weeks 6–10: behavioural stories. Prepare six to eight real stories about ownership, conflict, failure, learning and helping others (STAR guide). Read the company's published values or principles and connect your stories to them honestly.

Weeks 9–12: mock interviews. Practise speaking your solutions aloud, with a timer (technical interview checklist).

Role-specific depth

• Frontend: JavaScript, React, browser performance and accessibility; a UI coding task (frontend roadmap, React guide)
• Backend: APIs, databases, concurrency and caching (backend roadmap)
• Data and ML: SQL, statistics, modelling and experimentation (data roadmap)
• Mobile: platform lifecycle, architecture and performance (mobile roadmap)

Tips

• Treat every round, including the "culture" one, as technical in importance
• Prepare questions that show you studied the product and the team
• Be honest about what you do not know, and show how you would learn it
• If you have an offer elsewhere, share it professionally to help scheduling; do not use it as a threat

Common mistakes

• Grinding only algorithm problems and arriving without a single behavioural story
• Memorising solutions and failing on variations
• Giving "we" answers that hide your own contribution
• Neglecting design practice for roles that need it

Next steps

Read how Amazon and Google run theirs for contrast, learn about negotiating an offer and browse experienced and fresher openings.

What the company's own pages say (checked 28 October 2026)

Atlassian, confirmed in its published engineering interview guides (for example the backend guide):

• The engineering process is described as two coding interviews, one system design interview, one leadership (management) interview and one values interview. Some guides replace a round with a "craft" interview for fullstack or SRE roles.
• Coding rounds are 60 minutes and look at code quality, reasoning, adaptability and communication. The leadership interview is a 60-minute scenario-based conversation with an engineering manager. The values interview is 45 minutes and is behavioural.
• Feedback is reviewed by a hiring committee, and successful candidates go through a Team Match call with hiring managers before an offer.

Not confirmed: Adobe, Intuit, Uber, Salesforce, PayPal and the rest of the companies named. Our searches returned no official process pages for them, so their details are candidate-reported. The Atlassian guides are undated, so confirm the current rounds with your recruiter.

---

Please note: hiring processes change between campuses, drives and years, and companies update their rounds without notice. This guide describes the commonly reported structure so you know what to expect and how to prepare. Always confirm the current process on the company's official careers page or in your invitation email. This site is not affiliated with any company mentioned, and company names belong to their owners.