A Software Engineer at Packsize International plays a critical role in revolutionizing the packaging and logistics industry. Packsize is not just a software company; it is an on-demand packaging powerhouse that integrates complex software systems with physical, high-throughput industrial machinery. As a engineer here, your code directly controls how custom-sized boxes are calculated, designed, and manufactured in real-time, drastically reducing packaging waste, shipping costs, and environmental impact for global brands. In this role, you will work at the fascinating intersection of cloud SaaS applications, local machine control software, and industrial IoT. You will be responsible for building robust, scalable APIs, designing intuitive workflows, and ensuring seamless integration with customer Warehouse Management Systems (WMS) and ERPs. The software you build must be highly reliable, as any downtime directly halts physical warehouse operations and packaging production lines. This position demands a unique blend of hardware-software empathy, strong architectural thinking, and a commitment to high-quality code. You will collaborate closely with mechanical engineers, product managers, and field service teams to deliver end-to-end automated solutions. For developers who thrive on seeing their virtual code drive physical, real-world machines, the role at offers an incredibly rewarding and tangible engineering challenge. Software Engineer Packsize
Recruiter Phone Screen
reportedInitial call to assess your background, career goals, and alignment with the role.
What to demonstrate
- Initial call to assess your background, career goals, and alignment with the role
- Depth in API integration
How to prepare
- Be able to walk your CV end to end in two minutes, and say why this company specifically.
- Have your salary expectations, notice period and location constraints ready, and ask for the rest of the loop in writing.
Technical Screening Call
reportedCall with a hiring manager or team lead focusing on system design experience and past projects.
What to demonstrate
- Call with a hiring manager or team lead focusing on system design experience and past projects
- Depth in API integration
How to prepare
- Be able to walk your CV end to end in two minutes, and say why this company specifically.
- Have your salary expectations, notice period and location constraints ready, and ask for the rest of the loop in writing.
Final Interview
reportedIntensive multi-part interview including resume walkthrough, pair programming, and behavioral discussion.
What to demonstrate
- Intensive multi-part interview including resume walkthrough, pair programming, and behavioral discussion
- Depth in API integration
How to prepare
- Answer aloud and timed: Describe a scenario where a software deployment caused an unexpected physical bottleneck on a production line. How would you diagnose and resolve it?
- Answer aloud and timed: How do you handle data synchronization between an on-premise machine controller and a cloud-based analytics platform when internet connectivity is intermittent?
PracHub editorial advice for the preparation topics above.
Organize Your Portfolio in Advance
Be ready to show and walk through your past projects. Interviewers may ask you to share your screen and present code you have written previously without prior warning. Having a clean, well-structured GitHub repository or project directory ready to present is a major advantage.
Commit Entirely to TDD
Do not treat TDD as a buzzword. If you are asked to write code, write your tests first. If you write the functional code first and try to add tests at the end as an afterthought, it will be viewed as a red flag by the engineering team.
Arguing past a hint
When the interviewer asks what happens for a particular input or floats a different data structure, stop and take it seriously; it is almost always a correction rather than idle curiosity. Talking over it converts a recoverable wrong turn into a data point about how you handle review.
Choose a category, try a prompt, then open its approach, worked solution or follow-up when you need it.
Walk through how you would handle asynchronous operations and state management when communicating with physica
Walk through how you would handle asynchronous operations and state management when communicating with physical machine sensors.
Approach
- Say what the runtime actually does before reasoning about the code.
- Name what is shared across threads and what owns each piece of state.
- Identify the window where an invariant is briefly untrue.
- Distinguish a value from a reference to it, and say which one you handed out.
Follow-up
- What happens if two callers reach this at the same time?
- Where could this allocate more than you expect?
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?
Archive a resource graph without breaking live references or recursing
Resources reference other resources within a tenant; for the largest tenant the reference table holds up to 2,000,000 nodes and 8,000,000 edges. Archiving a resource must archive everything reachable from it that nothing outside the set still references, refuse when a live external referrer exists, and terminate when references form cycles, which they legitimately do. Produce the archive order and the refusal list, targeting O(V+E). Say what stops the traversal crossing a tenant boundary, and why recursion is the wrong control structure at this size.
Approach
- Load the subgraph with the tenant predicate on both endpoints of the edge, not only on the side you started from. Scoping the left table alone is the classic cross-tenant leak: one mis-entered edge then pulls another tenant's resources into the traversal and, worse, into the archive.
- Traverse iteratively with an explicit stack. A 2,000,000-node graph can hold a chain deep enough to exhaust a native stack in the low tens of thousands of frames, and that failure is a process crash rather than an error you can return.
- Treat cycles as data rather than corruption: compute strongly connected components with Tarjan in O(V+E) using its own explicit stack, then condense. The condensation is a DAG, so a topological order over it gives the archive order, and every member of a component archives in one transaction because no order within a cycle is valid.
- Decide refusals with reverse edges. A candidate is archivable only if every in-edge originates inside the candidate set, so build the transpose or count in-degrees restricted to the visited set, and emit each blocked resource with the id of the external referrer, which is the only part of the answer an operator can act on.
Follow-up
- The graph is read in one query and the archive writes a minute later. What can change in between, and how do you make the write safe?
- The candidate set is 400,000 resources. Is that one transaction, and if not, what does a half-finished archive look like to a reader?
Find version gaps and relay lag with window functions
outbox_event holds event_id, aggregate_type, aggregate_id, aggregate_version, event_type, payload, status ('pending','published','dead'), attempts, created_at, published_at. A projection is missing rows and you must decide whether the relay skipped events or the consumer dropped them. Write three queries over the last seven days: one listing every aggregate_id whose published aggregate_version sequence has a hole, one giving per-day counts with a running total, and one returning the newest published event per aggregate. For each, say where the window function is evaluated relative to WHERE and LIMIT. PostgreSQL 16.
Approach
- Gaps: compute lead(aggregate_version) OVER (PARTITION BY aggregate_id ORDER BY aggregate_version) in a subquery, then filter next_version <> aggregate_version + 1 in the outer query. Window functions are evaluated after WHERE, GROUP BY and HAVING and before the outer ORDER BY and LIMIT, so the predicate cannot sit in the same WHERE clause and PostgreSQL 16 has no QUALIFY.
- Say what the seven-day filter does to the answer: it truncates every partition, so the first row per aggregate has no predecessor inside the window and a hole spanning the boundary is invisible. Widen the window, or join to resource.version as the authority for the true maximum.
- Running total: SELECT date_trunc('day', created_at) AS d, count() AS n, sum(count()) OVER (ORDER BY date_trunc('day', created_at) ROWS UNBOUNDED PRECEDING). An aggregate inside a window call is legal because grouping runs before windowing. The grouping key is unique per row here so ROWS and RANGE agree, but write the frame anyway — over ungrouped rows with tied timestamps the default RANGE frame pulls in every peer row and the total jumps.
- Newest per aggregate: DISTINCT ON (aggregate_id) ... ORDER BY aggregate_id, aggregate_version DESC is the cheap PostgreSQL-only form when an index matches that order; row_number() OVER (PARTITION BY aggregate_id ORDER BY aggregate_version DESC) = 1 is the portable form and needs a subquery for the same evaluation-order reason as the gap query.
Follow-up
- Relay failover redelivers events. Does a duplicate break the gap query, and how would you detect one from this table alone?
- Turn the gap check into a continuous monitor rather than a query someone runs after an incident. What does it watch?
Keep soft-deleted accounts from blocking re-registration
app_user holds user_id, tenant_id, email CITEXT, password_hash (NULL for SSO principals), email_verified_at, auth_version, status ('invited','active','suspended','deactivated'), created_at, updated_at, deleted_at. Two live accounts for one address inside a tenant must be impossible, but an address freed by a soft delete must be reusable, and the same tenant may delete and re-register it repeatedly. Write the uniqueness DDL for PostgreSQL 16, then the equivalent for MySQL 8 where partial indexes do not exist, and say what each permits once three deleted rows already hold that address.
Approach
- Start from what is actually unique: not (tenant_id, email), but (tenant_id, email) among live rows. PostgreSQL says that directly — CREATE UNIQUE INDEX app_user_live_email ON app_user (tenant_id, email) WHERE deleted_at IS NULL. A full constraint over the same two columns burns the address permanently the first time someone deletes an account.
- Keep case-insensitivity in the type or the index, never in the application: CITEXT as given, or UNIQUE (tenant_id, lower(email)) as an expression index where the extension is unavailable. A case-sensitive unique column is exactly how two accounts for one human appear.
- For MySQL 8 the predicate has to move inside the key: add a discriminator column that is a constant 0 while the row is live and is set to user_id on delete, with UNIQUE (tenant_id, email, deleted_marker). Live rows share the constant and still collide; deleted rows differ from each other and stop colliding.
- State the NULL variant and its dependency: leaving the marker NULL for deleted rows also works, because a unique index treats NULLs as distinct — true in MySQL, and true in PostgreSQL only under the default NULLS DISTINCT, which PostgreSQL 15 lets you reverse. Check the polarity against the three existing deleted rows: constant-on-live is what preserves the collision you want, and reversing it silently admits duplicate live accounts.
Follow-up
- A deleted account re-registers with the same address the next day. Do the old resource rows follow the new user_id, and how does the API keep the two principals apart?
- How do you honour an erasure request while resource_revision.actor_user_id still references this table?
How would you design and implement a RESTful API to handle real-time packaging dimensions from a client wareho
How would you design and implement a RESTful API to handle real-time packaging dimensions from a client warehouse?
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?
Explain the principles of Test-Driven Development (TDD) and how you would apply them to refactor a legacy code
Explain the principles of Test-Driven Development (TDD) and how you would apply them to refactor a legacy codebase.
Approach
- Say who the caller is and what they do when the call fails halfway.
- Define the identity of a request so a retry cannot double-apply it.
- Separate accepted, pending, failed and confirmed; they are different facts.
- Design the error taxonomy before the success shape; callers branch on it.
Follow-up
- What happens if the caller retries after a timeout?
- How does a client discover it is on an old version of this contract?
What are the primary differences between interfaces and abstract classes in C#, and when would you choose one
What are the primary differences between interfaces and abstract classes in C#, and when would you choose one over the other?
Approach
- Say who the caller is and what they do when the call fails halfway.
- Define the identity of a request so a retry cannot double-apply it.
- Separate accepted, pending, failed and confirmed; they are different facts.
- Design the error taxonomy before the success shape; callers branch on it.
Follow-up
- What happens if the caller retries after a timeout?
- How does a client discover it is on an old version of this contract?
Describe a scenario where a software deployment caused an unexpected physical bottleneck on a production line.
Describe a scenario where a software deployment caused an unexpected physical bottleneck on a production line. How would you diagnose and resolve it?
Approach
- Say who the caller is and what they do when the call fails halfway.
- Define the identity of a request so a retry cannot double-apply it.
- Separate accepted, pending, failed and confirmed; they are different facts.
- Design the error taxonomy before the success shape; callers branch on it.
Follow-up
- What happens if the caller retries after a timeout?
- How does a client discover it is on an old version of this contract?
Walk us through your approach to optimizing database queries for a system processing thousands of custom packa
Walk us through your approach to optimizing database queries for a system processing thousands of custom packaging orders per hour.
Approach
- Say who the caller is and what they do when the call fails halfway.
- Define the identity of a request so a retry cannot double-apply it.
- Separate accepted, pending, failed and confirmed; they are different facts.
- Design the error taxonomy before the success shape; callers branch on it.
Follow-up
- What happens if the caller retries after a timeout?
- How does a client discover it is on an old version of this contract?
I noticed a transition in your career path on your resume. Can you explain the decisions behind this change an
I noticed a transition in your career path on your resume. Can you explain the decisions behind this change and how it shaped your engineering approach?
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?
Walk us through the architecture of the most complex project listed on your resume. What would you design diff
Walk us through the architecture of the most complex project listed on your resume. What would you design differently if you had to start over today?
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?
Explain a specific technical challenge from your past role that is not detailed in your resume, focusing on yo
Explain a specific technical challenge from your past role that is not detailed in your resume, focusing on your individual contribution.
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?
Read latency spikes on a sixty-second sawtooth
The cached listing read path serves about 14k reads/second at an 85% hit rate. p99 sits at 35 ms for 57 seconds, jumps to 900 ms for 3, and repeats. During each spike the primary shows several hundred identical listing queries starting within the same millisecond, all carrying one large tenant's id. Cache entries use a 60-second TTL. Give the mechanism, the ordered checks, the fix, and the correctness hazard your fix must not introduce.
Approach
- Match the period to a configured number before theorising about load. A spike every 60 seconds against a 60-second TTL is an entry expiring, and you confirm it by correlating spike timestamps with the entry's write time rather than with the traffic curve. If the period had matched a cron or a GC interval instead, this is a different investigation.
- Establish the concurrency of the miss. Several hundred identical queries in one millisecond means the miss path has no coalescing: every request that arrives between expiry and repopulation recomputes. The herd size is that key's arrival rate times its recompute time, so at 1.2k reads/second for the hot key and a 250 ms recompute you expect about 300 concurrent misses, which matches what is observed.
- Add single-flight on the miss path so one caller per key recomputes under a short-lived lock while the rest wait for its result. Prefer stale-while-revalidate where the read tolerates it: return the expired value immediately and refresh asynchronously, which removes the latency spike rather than serialising it into a queue of waiters.
- De-synchronise the keys. Write TTLs with jitter, for example 60 seconds plus or minus 10%, so a deploy or a mass invalidation does not align every key on the same second and turn a per-key herd into a fleet-wide one.
Follow-up
- The same sawtooth appears on a key that is invalidated on write rather than expired. Is that the same bug?
- How does your answer change if the recompute takes 4 seconds instead of 250 ms?
Built from the rounds and topics Packsize International candidates report.
Prepare, practise & reflect
One practical outcome each day. Spend longer where you need it.
0 / 7 done01Map the Packsize International loop
- Write out the reported sequence: Recruiter Phone Screen, Technical Screening Call, Final Interview.
- 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 API integration
- Spend the session on API integration, which Packsize International candidates report being tested on.
- Write one worked example in API integration and time yourself on it.
Deliverable: One timed worked example in API integration.
03Work Testing (TDD)
- Spend the session on Testing (TDD), which Packsize International candidates report being tested on.
- Write one worked example in Testing (TDD) and time yourself on it.
Deliverable: One timed worked example in Testing (TDD).
04Work Hands-on API-driven coding exercise
- Spend the session on Hands-on API-driven coding exercise, which Packsize International candidates report being tested on.
- Write one worked example in Hands-on API-driven coding exercise and time yourself on it.
Deliverable: One timed worked example in Hands-on API-driven coding exercise.
05Answer out loud: Technical & API Design
- Answer aloud, timed: How would you design and implement a RESTful API to handle real-time packaging dimensions from a client warehouse?
- Answer aloud, timed: Explain the principles of Test-Driven Development (TDD) and how you would apply them to refactor a legacy codebase.
Deliverable: Spoken answers to 2 reported Technical & API Design question(s), under time.
06Answer out loud: System Integration & Problem Solving
- Answer aloud, timed: Describe a scenario where a software deployment caused an unexpected physical bottleneck on a production line. How would you diagnose and resolve it?
- Answer aloud, timed: How do you handle data synchronization between an on-premise machine controller and a cloud-based analytics platform when internet connectivity is intermittent?
Deliverable: Spoken answers to 2 reported System Integration & Problem Solving question(s), under time.
07Answer out loud: Behavioral & Team Collaboration
- Answer aloud, timed: Describe a time when you had a strong disagreement with a teammate regarding software architecture. How did you resolve it?
- Answer aloud, timed: How do you handle receiving constructive, direct feedback on your code during a live, multi-developer review session?
Deliverable: Spoken answers to 2 reported Behavioral & Team Collaboration 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.
How do you handle data synchronization between an on-premise machine controller and a cloud-based analytics pl
How do you handle data synchronization between an on-premise machine controller and a cloud-based analytics platform when internet connectivity is intermittent?
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?
Describe a time when you had a strong disagreement with a teammate regarding software architecture. How did yo
Describe a time when you had a strong disagreement with a teammate regarding software architecture. How did you resolve it?
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 receiving constructive, direct feedback on your code during a live, multi-developer review s
How do you handle receiving constructive, direct feedback on your code during a live, multi-developer review session?
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?
Give an example of a project where you had to quickly learn a new technology or domain. What was your strategy
Give an example of a project where you had to quickly learn a new technology or domain. What was your strategy for getting up to speed?
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
How do you handle data synchronization between an on-premise machine controller and a cloud-based analytics platform when internet connectivity is intermittent?
- 02
Describe a time when you had a strong disagreement with a teammate regarding software architecture. How did you resolve it?
- 03
How do you handle receiving constructive, direct feedback on your code during a live, multi-developer review session?
- 04
Give an example of a project where you had to quickly learn a new technology or domain. What was your strategy for getting up to speed?
How technical and difficult is the coding portion of the interview?
The coding portion is moderately difficult but highly focused on practical application rather than abstract algorithmic puzzles. You will be evaluated on your ability to write clean, functional code, design basic APIs, and strictly follow TDD principles. They care more about your problem-solving approach, your code structure, and your test coverage than whether you can solve complex LeetCode brain teasers.
Packsize International Software Engineer candidate reports ↗What is a "mobbing" session and how should I prepare for it?
A mobbing session involves writing code collaboratively with 2 to 4 Packsize developers. One person drives (types) while the others navigate (suggest ideas and review). To prepare, practice verbalizing your thought process while coding, get comfortable receiving real-time suggestions, and focus on being a highly collaborative, ego-free team player.
Packsize International Software Engineer candidate reports ↗Does the role require working with physical hardware?
Yes, depending on the specific team, you will write software that directly interfaces with, configures, or monitors physical packaging machinery. While you do not need a background in hardware engineering, you must have an interest in learning how software interacts with physical systems and IoT devices.
Packsize International Software Engineer candidate reports ↗What is the typical timeline from the first screen to an offer?
The process can take anywhere from three weeks to a couple of months. Because Packsize coordinates interviews across multiple team leads and occasionally schedules on-site visits or team lunches, the scheduling can sometimes take time. Maintaining regular, polite follow-ups with your recruiter is highly recommended.
Packsize International Software Engineer candidate reports ↗What topics does Packsize International test in interviews?
Packsize International interviews most often cover Pricing Strategy, Complex Sales, API integration, Integrated packaging solutions, and Financial Analysis. The exact emphasis depends on the specific role you apply for.
Packsize International 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.
- 01Packsize International 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