The role of a Software Engineer at Bosch Rexroth is pivotal in driving innovation and ensuring the seamless integration of software solutions within the company’s advanced engineering frameworks. In this capacity, you will contribute directly to the development of control systems and automation technologies that empower manufacturers across various industries. The impact of your work is profound—enhancing product efficiency, reliability, and user experience through cutting-edge software applications. At Bosch Rexroth, you will engage in exciting projects that may involve IoT integration, real-time data processing, and complex algorithm development. Working alongside cross-functional teams, you will have the opportunity to influence product design and functionality, making your contributions not only valuable but essential to the company's mission of providing state-of-the-art hydraulic and automation solutions. This role combines technical expertise with creative problem-solving, making it both challenging and rewarding.
Technical Assessment
reportedInitial technical evaluations such as coding tests or problem-solving exercises.
What to demonstrate
- Initial technical evaluations such as coding tests or problem-solving exercises
- Depth in CAD / Computer-Aided Design
How to prepare
- Answer aloud and timed: Can you explain your experience with software development methodologies?
- Answer aloud and timed: What programming languages are you proficient in, and which do you prefer to use?
Behavioral Interview
reportedInterviews that explore your experiences and teamwork capabilities.
What to demonstrate
- Interviews that explore your experiences and teamwork capabilities
- Depth in CAD / Computer-Aided Design
How to prepare
- Prepare three examples from your own work, each with a decision you made and an outcome you can quantify.
- Re-read the description of the behavioral interview above and write down what you would ask to confirm before it.
Final Interviews
reportedConcluding interviews conducted by HR representatives, technical leads, and department heads.
What to demonstrate
- Concluding interviews conducted by HR representatives, technical leads, and department heads
- Depth in CAD / Computer-Aided Design
How to prepare
- Answer aloud and timed: Explain the importance of version control in software development.
- Answer aloud and timed: How would you design a control system for an automated assembly line?
PracHub editorial advice for the preparation topics above.
Prepare for Behavioral Questions
Practice articulating your past experiences with a focus on challenges and outcomes. Use the STAR (Situation, Task, Action, Result) method to structure your responses.
Research the Company
Understand Bosch Rexroth’s products, services, and market position. Be ready to discuss how your skills align with their business goals.
Practice Technical Skills
Review relevant programming concepts and practice coding challenges. Familiarity with algorithms and data structures will be beneficial.
Engage with Interviewers
Show interest in the people you meet during the interview process. Ask insightful questions about their work and experiences at Bosch Rexroth.
Choose a category, try a prompt, then open its approach, worked solution or follow-up when you need it.
Write a function that reverses a string in place.
Write a function that reverses a string in place.
Approach
- Restate the input: its shape, its size, and what is guaranteed about it.
- Name the brute-force solution and its complexity before improving on it.
- Choose the data structure from the access pattern, not from familiarity.
- State the target complexity and say which constraint rules the naive version out.
Follow-up
- How does this change if the input no longer fits in memory?
- What is the worst case, and how likely is it on real data?
How would you find the shortest path in a graph?
How would you find the shortest path in a graph?
Approach
- Restate the input: its shape, its size, and what is guaranteed about it.
- Name the brute-force solution and its complexity before improving on it.
- Choose the data structure from the access pattern, not from familiarity.
- State the target complexity and say which constraint rules the naive version out.
Follow-up
- How does this change if the input no longer fits in memory?
- What is the worst case, and how likely is it on real data?
Find overlapping job attempts and peak concurrency from lease records
A day of job_run history yields about 50,000,000 attempt records: (job_run_id, job_type, attempt, started_at, finished_at which is NULL when the worker died, lease_expires_at). Leases expire on a clock, so a job that outran its lease ran twice. Produce (a) every job_run_id whose attempts overlapped in wall-clock time and (b) the peak number of simultaneously running attempts per job_type with the minute it occurred. Target O(n log n). State how you treat a NULL finished_at and what clock skew does to your answer.
Approach
- Define the interval before sorting anything: an attempt occupies [started_at, COALESCE(finished_at, lease_expires_at)). finished_at is observed and lease_expires_at is only a promise, so every attempt without a finish contributes an estimate and the whole result is a lower bound on overlap rather than an exact count.
- For peak concurrency, sweep: emit 2n endpoints, sort by (timestamp, kind) with ends ordered before starts at equal timestamps, then walk the sequence maintaining a counter per job_type and record each type's maximum with its timestamp. O(n log n) dominated by the sort, O(n) space, or O(1) extra if the sort is external and the walk streams.
- For overlap detection, do not compare attempts pairwise. A single global sort by (job_run_id, started_at) gives both the grouping and the order; within a group, keep the maximum end seen so far and report an overlap exactly when the next start is less than that running maximum, which is one linear pass after the sort.
- Half-open intervals matter and are easy to get wrong: with closed intervals an attempt ending at the same millisecond another begins reads as concurrency two, and across 50,000,000 records that artefact swamps the real signal.
Follow-up
- A handler is not idempotent and you have found 400 overlapping jobs. Which of them actually caused damage, and what would you query to find out?
- Peak concurrency for one job_type is 4 against a configured cap of 4. Is the cap working, or is the data hiding attempts that never started?
Denormalise tenant onto revisions and backfill it live
resource_revision (revision_id, resource_id, version, actor_user_id, change_kind, patch, request_id, created_at) has 400M rows and no tenant column; tenant_id lives only on resource. Two reads need it: a tenant-scoped audit feed ordered by created_at DESC, and an offboarding purge. Both join back to resource today. Justify adding tenant_id to resource_revision against those two reads, name the anomaly the copy introduces and the constraint that prevents it, then give the ordered migration for a live table taking 1.2k writes/second — the lock each step takes, how the backfill is batched, and where each step stops being reversible. PostgreSQL 16.
Approach
- Justify from the access path rather than from taste. Without the column, the audit feed either scans resource_revision by created_at and discards other tenants' rows, or resolves the tenant's resource_ids first and probes with them — both proportional to the tenant's whole history rather than to one page. With (tenant_id, created_at DESC, revision_id DESC) it is a seek that stops at 50 rows, and the purge becomes a ranged delete instead of a join.
- Name the cost exactly: a second copy of a fact can disagree with the first. Make the disagreement unwritable rather than documented — add UNIQUE (resource_id, tenant_id) on resource so it can serve as a foreign-key target, then FOREIGN KEY (resource_id, tenant_id) REFERENCES resource (resource_id, tenant_id) on the revision table. A revision can then only ever carry its parent's tenant.
- Step one, expand: ALTER TABLE resource_revision ADD COLUMN tenant_id BIGINT NULL, with no default, so it is a catalogue change and no rewrite. It still needs ACCESS EXCLUSIVE for an instant, and that instant queues behind the longest open transaction on the table while every later query queues behind it — set lock_timeout to 2s and retry rather than wait.
- Step two, dual-write: deploy the writer that populates tenant_id on every new revision while reads still use the join. Reversible by redeploying the previous build, because nothing reads the column yet.
Follow-up
- The backfill is half finished and a rollback is required. What state is the table in, and what does the previous build do with a half-populated column?
- How do you verify the backfill actually finished, given rows are still being inserted while it runs?
Write the update path that detects a concurrent edit
resource carries version INT NOT NULL DEFAULT 1. resource_revision holds revision_id, resource_id, version, actor_user_id, change_kind, patch JSONB, request_id, created_at with UNIQUE (resource_id, version). outbox_event holds aggregate_type, aggregate_id, aggregate_version, event_type, payload, status. A PUT carries the version the client read. Write the exact statements for the single transaction that applies the edit, records the revision and enqueues 'resource.updated', and give the handler's branch on zero affected rows. Then say what PostgreSQL 16 does under READ COMMITTED when two of these updates hit one row at once.
Approach
- One transaction, three writes, no network call inside it: UPDATE resource SET title = $3, version = version + 1, updated_at = now() WHERE resource_id = $1 AND tenant_id = $4 AND version = $2; then INSERT the resource_revision row at version $2 + 1; then INSERT the outbox_event row at the same aggregate_version. The event goes to a table rather than a broker because no transaction spans both.
- Branch on the affected-row count before doing anything else. Zero has three causes — stale version, wrong tenant, row gone — so re-read once and map to 409 carrying the current version, or 404 for an id outside the caller's tenant, which also stops the endpoint confirming that another tenant's id exists.
- State the engine behaviour instead of assuming it. Under READ COMMITTED the second UPDATE blocks on the row lock, and when the first commits PostgreSQL re-evaluates the WHERE clause against the newly committed row, so the version predicate now fails and the statement reports zero rows. Under REPEATABLE READ the identical collision raises SQLSTATE 40001 instead, so the handler must fold both shapes into one conflict response.
- Keep UNIQUE (resource_id, version) even though the predicate already serialises writers. It is what makes a lost update unwritable if any other path ever reaches the revision table, and it converts a logic bug into 23505 rather than into a silently missing history row.
Follow-up
- A client sends the version it read ten minutes ago and the resource has moved three versions. What is in your 409 so it can resolve the conflict without a full re-fetch?
- Two editors, two disjoint fields, no overlap. Does your answer still refuse the second write, and should it?
What programming languages are you proficient in, and which do you prefer to use?
What programming languages are you proficient in, and which do you prefer to use?
Approach
- Clarify what is being asked and what a complete answer contains.
- State your assumptions explicitly before working the problem.
- Say what you would check first and why it is the highest-information step.
- Work from the requirement backwards to the design.
Follow-up
- What assumption would you test first?
- How would you know your answer was wrong?
Describe a challenging technical problem you solved in a previous project.
Describe a challenging technical problem you solved in a previous project.
Approach
- Clarify what is being asked and what a complete answer contains.
- State your assumptions explicitly before working the problem.
- Say what you would check first and why it is the highest-information step.
- Work from the requirement backwards to the design.
Follow-up
- What assumption would you test first?
- How would you know your answer was wrong?
Explain the importance of version control in software development.
Explain the importance of version control in software development.
Approach
- Clarify what is being asked and what a complete answer contains.
- State your assumptions explicitly before working the problem.
- Say what you would check first and why it is the highest-information step.
- Work from the requirement backwards to the design.
Follow-up
- What assumption would you test first?
- How would you know your answer was wrong?
How would you design a control system for an automated assembly line?
How would you design a control system for an automated assembly line?
Approach
- Fix the scope first: who calls this, how often, and what they do when it fails.
- Name the read and write paths separately; they rarely have the same bottleneck.
- Choose a partition key and say what query it makes expensive.
- State the consistency you need, and where you are willing to be stale.
Follow-up
- What breaks first when traffic grows ten times?
- How does this behave when that dependency is down for an hour?
Discuss the considerations you would take into account when architecting a microservices-based application.
Discuss the considerations you would take into account when architecting a microservices-based application.
Approach
- Fix the scope first: who calls this, how often, and what they do when it fails.
- Name the read and write paths separately; they rarely have the same bottleneck.
- Choose a partition key and say what query it makes expensive.
- State the consistency you need, and where you are willing to be stale.
Follow-up
- What breaks first when traffic grows ten times?
- How does this behave when that dependency is down for an hour?
What design patterns do you commonly use, and why?
What design patterns do you commonly use, and why?
Approach
- Fix the scope first: who calls this, how often, and what they do when it fails.
- Name the read and write paths separately; they rarely have the same bottleneck.
- Choose a partition key and say what query it makes expensive.
- State the consistency you need, and where you are willing to be stale.
Follow-up
- What breaks first when traffic grows ten times?
- How does this behave when that dependency is down for an hour?
How would you optimize a software process that is currently too slow?
How would you optimize a software process that is currently too slow?
Approach
- Clarify what is being asked and what a complete answer contains.
- State your assumptions explicitly before working the problem.
- Say what you would check first and why it is the highest-information step.
- Work from the requirement backwards to the design.
Follow-up
- What assumption would you test first?
- How would you know your answer was wrong?
Present a case where you had to make a trade-off in your design decisions. What did you choose and why?
Present a case where you had to make a trade-off in your design decisions. What did you choose and why?
Approach
- Clarify what is being asked and what a complete answer contains.
- State your assumptions explicitly before working the problem.
- Say what you would check first and why it is the highest-information step.
- Work from the requirement backwards to the design.
Follow-up
- What assumption would you test first?
- How would you know your answer was wrong?
How do you approach debugging and troubleshooting software issues?
How do you approach debugging and troubleshooting software issues?
Approach
- Establish what changed and when, before forming any theory.
- Pick a bisection that eliminates candidates whichever way it turns out.
- Check the instrumentation before believing the symptom.
- Separate the trigger from the cause; the deploy is rarely the bug.
Follow-up
- What would you look at first, and what would it rule out?
- How would you tell a cause from a coincidence here?
Built from the rounds and topics Bosch Rexroth candidates report.
Prepare, practise & reflect
One practical outcome each day. Spend longer where you need it.
0 / 7 done01Map the Bosch Rexroth loop
- Write out the reported sequence: Technical Assessment, Behavioral Interview, Final Interviews.
- For each round, write one sentence on what it is judging, from the description above, and mark the one you are least ready for.
Deliverable: A one-page map of the 3 reported rounds, with the weakest marked.
02Work CAD / Computer-Aided Design
- Spend the session on CAD / Computer-Aided Design, which Bosch Rexroth candidates report being tested on.
- Write one worked example in CAD / Computer-Aided Design and time yourself on it.
Deliverable: One timed worked example in CAD / Computer-Aided Design.
03Work System/Control systems (control system design)
- Spend the session on System/Control systems (control system design), which Bosch Rexroth candidates report being tested on.
- Write one worked example in System/Control systems (control system design) and time yourself on it.
Deliverable: One timed worked example in System/Control systems (control system design).
04Work 3D modeling / assembly design
- Spend the session on 3D modeling / assembly design, which Bosch Rexroth candidates report being tested on.
- Write one worked example in 3D modeling / assembly design and time yourself on it.
Deliverable: One timed worked example in 3D modeling / assembly design.
05Answer out loud: Technical / Domain Questions
- Answer aloud, timed: Can you explain your experience with software development methodologies?
- Answer aloud, timed: What programming languages are you proficient in, and which do you prefer to use?
Deliverable: Spoken answers to 2 reported Technical / Domain Questions question(s), under time.
06Answer out loud: System Design / Architecture
- Answer aloud, timed: How would you design a control system for an automated assembly line?
- Answer aloud, timed: Discuss the considerations you would take into account when architecting a microservices-based application.
Deliverable: Spoken answers to 2 reported System Design / Architecture question(s), under time.
07Answer out loud: Behavioral / Leadership
- Answer aloud, timed: Tell me about a time you led a project. What challenges did you face?
- Answer aloud, timed: How do you handle conflicts within a team?
Deliverable: Spoken answers to 2 reported Behavioral / Leadership question(s), under time.
Expand any day for tasks and deliverables. Your progress is saved on this device.
Behavioural rounds judge the decision you made and what it cost.
Can you explain your experience with software development methodologies?
Can you explain your experience with software development methodologies?
Approach
- Pick a story where you made the decision, not one where you watched it.
- State the situation in two sentences and spend the rest on the reasoning.
- Give the blast radius: what could have broken, and what you measured.
- Name the disagreement and how you resolved it with evidence.
Follow-up
- What would you do differently if you ran that again?
- How did you know your change caused the improvement?
Tell me about a time you led a project. What challenges did you face?
Tell me about a time you led a project. What challenges did you face?
Approach
- Pick a story where you made the decision, not one where you watched it.
- State the situation in two sentences and spend the rest on the reasoning.
- Give the blast radius: what could have broken, and what you measured.
- Name the disagreement and how you resolved it with evidence.
Follow-up
- What would you do differently if you ran that again?
- How did you know your change caused the improvement?
How do you handle conflicts within a team?
How do you handle conflicts within a team?
Approach
- Pick a story where you made the decision, not one where you watched it.
- State the situation in two sentences and spend the rest on the reasoning.
- Give the blast radius: what could have broken, and what you measured.
- Name the disagreement and how you resolved it with evidence.
Follow-up
- What would you do differently if you ran that again?
- How did you know your change caused the improvement?
What motivates you to perform at your best?
What motivates you to perform at your best?
Approach
- Pick a story where you made the decision, not one where you watched it.
- State the situation in two sentences and spend the rest on the reasoning.
- Give the blast radius: what could have broken, and what you measured.
- Name the disagreement and how you resolved it with evidence.
Follow-up
- What would you do differently if you ran that again?
- How did you know your change caused the improvement?
- 01
Can you explain your experience with software development methodologies?
- 02
Tell me about a time you led a project. What challenges did you face?
- 03
How do you handle conflicts within a team?
- 04
What motivates you to perform at your best?
What is the difficulty level of the interviews?
The interviews at Bosch Rexroth are generally considered of average difficulty, with a balanced mix of technical and behavioral questions. Preparation time can vary, but candidates typically spend several weeks reviewing relevant materials and practicing problem-solving.
Bosch Rexroth Software Engineer candidate reports ↗What differentiates successful candidates?
Successful candidates demonstrate not only technical expertise but also strong communication skills and a collaborative mindset. Being able to articulate your past experiences effectively and showing alignment with the company's values are crucial.
Bosch Rexroth Software Engineer candidate reports ↗What is the company culture like at Bosch Rexroth?
Bosch Rexroth embraces a culture of collaboration, innovation, and integrity. Expect a supportive environment where teamwork and continuous learning are encouraged.
Bosch Rexroth Software Engineer candidate reports ↗What is the timeline from initial screen to offer?
The interview process can take several weeks, typically ranging from 4 to 8 weeks from the initial screening to the final offer, depending on the role and location.
Bosch Rexroth Software Engineer candidate reports ↗Are there remote work or hybrid options available?
While remote work options may vary by role and location, Bosch Rexroth has been increasingly flexible in offering hybrid work arrangements in response to employee needs.
Bosch Rexroth Software Engineer candidate reports ↗What topics does Bosch Rexroth test in interviews?
Bosch Rexroth interviews most often cover Problem Solving, Communication Skills, Test Planning, Stakeholder Management, and Test Case Design. The exact emphasis depends on the specific role you apply for.
Bosch Rexroth Software Engineer candidate reports ↗Sources & methodology 3 sources ↗
No official company page is cited. Rounds and questions come from candidate reports and PracHub editorial material; each source shows the date it was read.
- 01Bosch Rexroth Software Engineer candidate reports ↗
Company-reported rounds, questions and FAQ.
Candidate reports · Accessed 2026-09-22 - 02PracHub Software Engineer practice ↗
PracHub practice material, not company-reported.
PracHub page · Accessed 2026-09-22 - 03PracHub preparation framework ↗
PracHub preparation guidance.
PracHub page · Accessed 2026-09-22
Explore related engineering environments and compare the preparation focus.
Cognition Software Engineer Interview Guide
What Cognition asks Software Engineer candidates, from reported rounds and questions.
Vercel Software Engineer Interview Guide
Debugging practice for Vercel software engineer prep built on a reproduction you trust, narrowing to the smallest failing input, and changing one variable per run so the result stays attributable.
Together Ai Software Engineer Interview Guide
Failure-handling practice for Together Ai software engineer candidates: requests whose outcome a timeout leaves unknown, where a retry is safe, and deduplicating at the receiver instead of assuming exactly-once delivery.
Spotify Software Engineer Interview Guide
Timed practice for Spotify software engineer candidates who lose time to the clock: short problems taken end to end, then reviewed against a written rubric rather than a passing test run.