A Software Engineer at Propel works at the unique intersection of modern financial technology and social impact. Propel builds software designed specifically for low-income Americans, most notably through their flagship product, Providers (formerly Fresh EBT). This platform helps millions of users manage their SNAP benefits, track their spending, and access critical financial services. As an engineer here, you are not just writing code to optimize click-through rates; you are building highly accessible, secure, and robust systems that directly impact the daily financial survival of millions of families. The technical challenges at Propel are vast and deeply rewarding. Engineers are responsible for scaling platforms that handle high-volume traffic, integrating with complex and legacy government portals, and maintaining strict data privacy and security standards. Whether you are joining as a Senior Full Stack Engineer, a Senior Platform Engineer, or a Staff Software Engineer, your work will directly influence product architecture, system reliability, and the overall user experience. You will collaborate closely with product managers, designers, and operations teams to ship features that are intuitive, lightweight, and performant on low-bandwidth connections. Working at Propel requires a unique blend of technical excellence and deep user empathy. The engineering team values pragmatic problem-solving, clean and maintainable code, and a strong sense of ownership.
Application Review
reportedInitial review of the application to assess qualifications and fit for the role.
What to demonstrate
- Initial review of the application to assess qualifications and fit for the role
- Depth in Programming (General Coding Skills)
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.
Aptitude Round
reportedTime-sensitive round focusing on logical reasoning and reading comprehension.
What to demonstrate
- Time-sensitive round focusing on logical reasoning and reading comprehension
- Depth in Programming (General Coding Skills)
How to prepare
- Answer aloud and timed: Interpret a technical specification sheet for a legacy government API and identify potential integration risks.
- Answer aloud and timed: Analyze a short passage detailing a compliance policy and answer comprehension questions regarding its technical implementation.
Coding Challenge
reportedPractical coding assessment to evaluate coding skills and problem-solving abilities.
What to demonstrate
- Practical coding assessment to evaluate coding skills and problem-solving abilities
- Depth in Programming (General Coding Skills)
How to prepare
- Answer aloud and timed: Write a function to parse and clean unstructured transaction description strings from legacy bank feeds.
- Answer aloud and timed: Implement an algorithm to find the most efficient path for synchronizing user benefit balances across multiple external databases.
Technical Interviews
reportedCollaborative technical discussions focusing on real-world problem-solving and architectural design.
What to demonstrate
- Collaborative technical discussions focusing on real-world problem-solving and architectural design
- Depth in Programming (General Coding Skills)
How to prepare
- Answer aloud and timed: Design a rate-limiter to prevent abuse on a public-facing API endpoint while ensuring legitimate users are not blocked.
- Answer aloud and timed: Write a program to detect duplicate user profiles based on fuzzy matching of names and addresses.
Behavioral Interviews
reportedDiscussions to assess cultural alignment and behavioral fit within the team.
What to demonstrate
- Discussions to assess cultural alignment and behavioral fit within the team
- Depth in Programming (General Coding Skills)
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 interviews above and write down what you would ask to confirm before it.
Final Decision
reportedReview of all evaluations to make a final hiring decision.
What to demonstrate
- Review of all evaluations to make a final hiring decision
- Depth in Programming (General Coding Skills)
How to prepare
- Answer aloud and timed: Design a caching layer for a mobile application that frequently queries slow, unpredictable external government databases.
- Answer aloud and timed: Describe how you would migrate a monolithic backend service to a microservices architecture without causing downtime for active users.
PracHub editorial advice for the preparation topics above.
Understand the User Constraints
Remember that Propel's users often use older mobile devices, have limited data plans, and rely on the app for critical financial decisions. Keep performance, lightweight payloads, and offline capabilities in mind during system design discussions.
Choose Your Language Wisely
For the coding challenge, select the language you are most comfortable with. Writing clean, idiomatic code is far more important than trying to impress the interviewer with a language you rarely use.
Do not jump straight into writing code during your technical interviews
Always clarify requirements, state your assumptions, and walk the interviewer through your high-level approach first.
Choose a category, try a prompt, then open its approach, worked solution or follow-up when you need it.
Write a function to parse and clean unstructured transaction description strings from legacy bank feeds.
Write a function to parse and clean unstructured transaction description strings from legacy bank feeds.
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?
Implement an algorithm to find the most efficient path for synchronizing user benefit balances across multiple
Implement an algorithm to find the most efficient path for synchronizing user benefit balances across multiple external databases.
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?
Write a program to detect duplicate user profiles based on fuzzy matching of names and addresses.
Write a program to detect duplicate user profiles based on fuzzy matching of names and addresses.
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?
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?
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?
Given a set of user engagement metrics over a quarter, identify the primary drop-off points in the user journe
Given a set of user engagement metrics over a quarter, identify the primary drop-off points in the user journey and suggest potential technical bottlenecks.
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?
Solve a series of logical deduction puzzles involving data flow and system states.
Solve a series of logical deduction puzzles involving data flow and system states.
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?
Interpret a technical specification sheet for a legacy government API and identify potential integration risks
Interpret a technical specification sheet for a legacy government API and identify potential integration risks.
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?
Analyze a short passage detailing a compliance policy and answer comprehension questions regarding its technic
Analyze a short passage detailing a compliance policy and answer comprehension questions regarding its technical implementation.
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?
Design a rate-limiter to prevent abuse on a public-facing API endpoint while ensuring legitimate users are not
Design a rate-limiter to prevent abuse on a public-facing API endpoint while ensuring legitimate users are not blocked.
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?
Design a notification system capable of sending push alerts to millions of users simultaneously when governmen
Design a notification system capable of sending push alerts to millions of users simultaneously when government benefits are deposited.
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 architect a secure, HIPAA-compliant data pipeline for a healthcare-focused integration within th
How would you architect a secure, HIPAA-compliant data pipeline for a healthcare-focused integration within the Providers app?
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?
Design a caching layer for a mobile application that frequently queries slow, unpredictable external governmen
Design a caching layer for a mobile application that frequently queries slow, unpredictable external government databases.
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?
Describe how you would migrate a monolithic backend service to a microservices architecture without causing do
Describe how you would migrate a monolithic backend service to a microservices architecture without causing downtime for active users.
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?
Describe a situation where you had to debug a complex production issue with limited telemetry or logging. How
Describe a situation where you had to debug a complex production issue with limited telemetry or logging. How did you approach it?
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 Propel candidates report.
Prepare, practise & reflect
One practical outcome each day. Spend longer where you need it.
0 / 7 done01Map the Propel loop
- Write out the reported sequence: Application Review, Aptitude Round, Coding Challenge, Technical Interviews, Behavioral Interviews, Final Decision.
- 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 6 reported rounds, with the weakest marked.
02Work Programming (General Coding Skills)
- Spend the session on Programming (General Coding Skills), which Propel candidates report being tested on.
- Write one worked example in Programming (General Coding Skills) and time yourself on it.
Deliverable: One timed worked example in Programming (General Coding Skills).
03Work Coding Challenges
- Spend the session on Coding Challenges, which Propel candidates report being tested on.
- Write one worked example in Coding Challenges and time yourself on it.
Deliverable: One timed worked example in Coding Challenges.
04Work Fullstack Engineering
- Spend the session on Fullstack Engineering, which Propel candidates report being tested on.
- Write one worked example in Fullstack Engineering and time yourself on it.
Deliverable: One timed worked example in Fullstack Engineering.
05Answer out loud: Aptitude & Analytical Reasoning
- Answer aloud, timed: Given a set of user engagement metrics over a quarter, identify the primary drop-off points in the user journey and suggest potential technical bottlenecks.
- Answer aloud, timed: Solve a series of logical deduction puzzles involving data flow and system states.
Deliverable: Spoken answers to 2 reported Aptitude & Analytical Reasoning question(s), under time.
06Answer out loud: Coding & Algorithmic Problem Solving
- Answer aloud, timed: Write a function to parse and clean unstructured transaction description strings from legacy bank feeds.
- Answer aloud, timed: Implement an algorithm to find the most efficient path for synchronizing user benefit balances across multiple external databases.
Deliverable: Spoken answers to 2 reported Coding & Algorithmic Problem Solving question(s), under time.
07Answer out loud: System Design & Platform Architecture
- Answer aloud, timed: Design a notification system capable of sending push alerts to millions of users simultaneously when government benefits are deposited.
- Answer aloud, timed: How would you architect a secure, HIPAA-compliant data pipeline for a healthcare-focused integration within the Providers app?
Deliverable: Spoken answers to 2 reported System Design & Platform Architecture 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.
Tell me about a time when you had to make a technical compromise to meet a tight product deadline. What was th
Tell me about a time when you had to make a technical compromise to meet a tight product deadline. What was the impact, and how did you manage technical debt?
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 advocate for accessibility and performance optimizations when building features for users with olde
How do you advocate for accessibility and performance optimizations when building features for users with older devices or limited data plans?
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?
Share an experience where you had a disagreement with a product manager regarding a feature's implementation.
Share an experience where you had a disagreement with a product manager regarding a feature's implementation. 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?
- 01
Tell me about a time when you had to make a technical compromise to meet a tight product deadline. What was the impact, and how did you manage technical debt?
- 02
How do you advocate for accessibility and performance optimizations when building features for users with older devices or limited data plans?
- 03
Share an experience where you had a disagreement with a product manager regarding a feature's implementation. How did you resolve it?
What is the hybrid or remote work policy at Propel?
Propel is headquartered in Brooklyn, NY, and operates with a hybrid model for local employees, while also supporting fully remote engineers in the United States. Be sure to clarify the specific location expectations for your target role with your recruiter early in the process.
Propel Software Engineer candidate reports ↗How much time should I dedicate to preparing for the interview?
Candidates typically spend 1 to 2 weeks preparing. Focus your energy on practicing timed logical reasoning tests, reviewing core system design patterns (especially caching and API integrations), and writing clean code in your preferred programming language.
Propel Software Engineer candidate reports ↗What differentiates successful candidates at Propel?
Successful candidates demonstrate a rare combination of technical pragmatism and genuine empathy for the user base. They don't just build complex systems for the sake of complexity; they design simple, highly reliable solutions that solve actual human problems.
Propel Software Engineer candidate reports ↗How quickly does the interview process move?
The entire process, from the initial application to a final offer, typically takes between 3 to 5 weeks, depending on candidate availability and scheduling.
Propel Software Engineer candidate reports ↗What topics does Propel test in interviews?
Propel interviews most often cover Frontend Development, Backend Development, System Design, Stakeholder Communication, and Machine Learning (Production). The exact emphasis depends on the specific role you apply for.
Propel 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.
- 01Propel 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.
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.
Discord Software Engineer Interview Guide
Database practice for Discord candidates: how an index changes a query plan, and which anomalies survive a given isolation level, since read committed still permits non-repeatable reads.
Booking.com Software Engineer Interview Questions & Guide 2026
Systems practice for Booking.com software engineer candidates, weighted toward travel and hospitality work: the load that actually arrives, the failure modes that matter there, and the invariants a partial outage must not break.
Zebra Technologies Software Engineer Interview Guide
What Zebra Technologies asks Software Engineer candidates, from reported rounds and questions.