[Interview Experience] SAP Concur – Software Engineer – USA (L1B Visa) | Got Offer ✅
Summary
I went through 5 interview rounds (HR screen, three technical rounds covering DSA, system design, and SQL, plus a managerial round) and received an offer for a Software Engineer position at SAP Concur in the USA.
Full Experience
Company: SAP Concur Role: Software Engineer Location: USA (Virtual interviews, L1B Visa sponsorship) Duration: 4–6 weeks Result: Offer received ✅
Background I worked at SAP Labs India for two years before going through this process. I'm sharing this for anyone targeting SAP America Inc, USA or preparing for a similar L1B visa-sponsored internal transfer.
Important note for international candidates: The L1B visa is an intracompany transfer visa. To be eligible, you must have worked for SAP (or any multinational filing for L1B) in your home country for a minimum of one continuous year within the last three years. If you're aiming for a US role at SAP, building that tenure at SAP in your home country first is a prerequisite, not optional.
Round 1 — HR / Recruiter Screen A standard 30-minute call with an HR recruiter. Focused on background, current role, motivations for the move, and compensation expectations. Nothing technical. The recruiter was friendly and clearly explained the process upfront, which set a good tone. They were also transparent about the L1B visa sponsorship path from the start.
Rounds 2, 3, 4 — Technical Round All three rounds were virtual and covered a mix of DSA, system design, and design patterns. Here's a breakdown of what came up: Data Structures and Algorithms
BST problem: finding a specific node (LCA-style)
- Tree-based problem: find nodes with values greater than a given leaf value
- Count all leaf nodes in a binary tree
- Stack problem: balanced parentheses validation (classic but they wanted clean, well-structured code)
- Array/string manipulation: count occurrences of all substrings within a given string
- String/array question: find unique rows in a 2D array or matrix
The DSA questions were LC Medium level overall. They weren't looking for the most optimized solution right away. They cared about how you think, whether you ask clarifying questions, and how you walk through your reasoning. Think out loud.
System Design
- Design an API system capable of handling N concurrent requests
- Key topics that came up: rate limiting, load balancing, horizontal scaling, queue-based request handling
- They wanted you to think about failure scenarios and bottlenecks, not just the happy path
OOP and Design Patterns
- Discussion on commonly used design patterns (Singleton, Factory, Observer came up in context)
- They asked how you'd apply patterns to real-world scenarios rather than just define them
- Clean code and separation of concerns were emphasized
SQL
- What is a SQL index and how does it work internally? (B-tree structure, when to use, trade-offs with write performance)
- How do you find unique rows in a table? (DISTINCT, GROUP BY approaches, and when to use each)
- General query writing and understanding of relational data modeling
Round 5 — Managerial Round Focused on team fit, communication style, and long-term goals. Standard behavioral questions. Be ready with STAR-format answers around:
- Handling disagreements within a team
- Owning a project end-to-end
- Adapting to new environments or technologies
- Why SAP and why this role
The manager was genuinely curious about your trajectory, not just checking boxes.
Post-Offer: The L1B Visa Process
⚠️ Disclaimer — please read before anything else: Visa rules, processing timelines, and eligibility requirements are extremely delicate and change frequently, sometimes with little notice, especially with shifts in immigration policy. Everything I've shared here reflects my personal experience at the time I went through the process. Do NOT treat this as legal or immigration advice. Always consult a qualified immigration attorney and rely on official USCIS and US State Department sources for the most current requirements. What applied in my case may not apply to yours.
L1B Eligibility: The L1B is an intracompany transfer visa for specialized knowledge workers. To qualify, you must have been employed by the same multinational company (SAP, in this case) in your home country for at least one continuous year within the three years preceding the petition. In my case, my two years at SAP Labs India made me eligible. There are no shortcuts here. The work experience in your home country is a hard eligibility requirement, not just a formality.
The visa timeline after offer acceptance:
- SAP's immigration team initiates the L1B petition. Allow several weeks for USCIS processing and approval.
- Once the petition is approved, a visa appointment is scheduled at the US Consulate.
- Attend the visa stamping interview in Chennai. Prepare your documents thoroughly: offer letter, petition approval notice (I-797), employer support letters, employment history, pay stubs, and anything that demonstrates your specialized knowledge role.
- After successful stamping, you enter the USA on the L1B visa.
SAP's immigration team was supportive and communicative throughout. The visa leg added meaningful time to the overall timeline, so factor this in when planning your start date. Given how frequently immigration policies shift, stay in close contact with SAP's immigration team and verify every step with up-to-date official sources.
Tips for Anyone Preparing
- Brush up on binary trees and BSTs. Multiple questions came from this space.
- Don't neglect stack-based problems. They're quick to solve but interviewers watch for clean implementation.
- Practice substring and string manipulation problems: counting substrings, finding patterns, sliding window techniques.
- For system design, go beyond basic architecture. Talk about scalability, failure handling, and trade‑offs.
- Know your SQL fundamentals deeply: indexes, query optimization, and how DISTINCT vs GROUP BY behave differently.
- Know your design patterns in application, not just definition.
- For the managerial round, have 3–4 solid STAR stories ready.
- If you're targeting SAP USA via L1B, start building your tenure at SAP in your home country early. The one‑year minimum is non‑negotiable, and the visa process itself takes significant additional time.
- Stay current on immigration policy. Rules change, and what worked for someone else's timeline may not apply to yours.
Overall The process was smooth, well‑structured, and the interviewers were respectful of your time. Every round had a clear purpose. Having worked at SAP Labs India for two years gave me solid context going in, and I think that familiarity with SAP's engineering culture genuinely helped. If you're on a similar path, put in the prep and stay patient with the visa process. It's worth it.
Happy to answer questions in the comments. Good luck! 🙌
Interview Questions (8)
Find nodes with values greater than a given leaf value in a BST
Tree‑based problem: given a binary search tree and a leaf node value, find all nodes in the tree whose values are greater than the value of that leaf node.
Count all leaf nodes in a binary tree
Given a binary tree, count the number of leaf nodes (nodes with no children) present in the tree.
Balanced parentheses validation
Given a string consisting of parentheses characters '(', ')', determine if the parentheses are balanced and properly nested.
Count occurrences of all substrings within a string
Given a string, count how many times each possible substring appears in the string.
Find unique rows in a 2D array or matrix
Given a 2‑dimensional array (matrix), return the rows that are unique (appear only once) in the matrix.
Design an API system capable of handling N concurrent requests
Design an API service that can handle a large number (N) of concurrent requests, covering aspects such as rate limiting, load balancing, horizontal scaling, and queue‑based request handling, as well as failure scenarios and bottlenecks.
Explain SQL indexes and how they work internally
Describe what a SQL index is, the underlying B‑tree structure, when to use an index, and the trade‑offs it introduces, especially regarding write performance.
Find unique rows in a SQL table
Given a SQL table, explain how to retrieve rows that are unique using DISTINCT, GROUP BY, or other approaches, and discuss when each method is appropriate.
Preparation Tips
- Brush up on binary trees and BSTs; multiple questions came from this space.
- Practice stack‑based problems such as balanced parentheses validation, focusing on clean implementation.
- Work on substring and string‑manipulation problems (counting substrings, sliding‑window techniques).
- For system design, study scalability concepts: rate limiting, load balancing, horizontal scaling, queue‑based handling, and failure‑scenario analysis.
- Deepen SQL fundamentals: index structures, query optimization, and differences between DISTINCT and GROUP BY.
- Review common design patterns (Singleton, Factory, Observer) and be ready to discuss real‑world applications.
- Prepare 3‑4 STAR stories for behavioral questions (handling disagreements, owning end‑to‑end projects, adapting to new tech, motivation for joining SAP).