A Software Engineer at Givzey plays a pivotal role in revolutionizing the fundraising landscape. As a pioneering financial technology platform dedicated to the nonprofit sector, Givzey introduces flexible giving solutions, such as "Give Now, Pay Later" (GNPL), donor-managed accounts, and automated giving pipelines. In this role, you will build and scale the secure, high-performance infrastructure that bridges the gap between passionate donors and impactful nonprofit organizations. Whether your focus is as a Systems Engineer, Full Stack Engineer, Front End Engineer, or Web Developer, your work directly impacts how millions of dollars are processed, tracked, and deployed. You will tackle complex challenges surrounding transactional integrity, real-time ledger management, and seamless donor user experiences. The engineering team at Givzey operates with a high degree of autonomy, meaning you will have a direct hand in product decisions, architectural choices, and technical strategy from day one. This is an environment where code quality, security compliance, and user empathy intersect. You will work on products that help nonprofits secure larger gifts, improve donor retention, and streamline their operations. For an ambitious engineer, this role offers the unique opportunity to solve sophisticated fintech problems while driving measurable social impact.
Initial Conversation
reportedAlign on career goals and company culture.
What to demonstrate
- Align on career goals and company culture
- Depth in Full-Stack Development
How to prepare
- Answer aloud and timed: Implement a function to calculate payment schedules for a flexible giving plan, accounting for custom frequencies and leap years.
- Answer aloud and timed: Write a function that takes an array of donor transactions and groups them by campaign, returning the top three campaigns by total volume.
Technical Capabilities Assessment
reportedEvaluate your technical skills through practical engineering scenarios.
What to demonstrate
- Evaluate your technical skills through practical engineering scenarios
- Depth in Full-Stack Development
How to prepare
- Answer aloud and timed: Given an API response containing nested organization data, write a utility to flatten the data structure for efficient frontend rendering.
- Answer aloud and timed: Design an algorithm to detect duplicate donor profiles based on matching names, emails, and fuzzy-matched addresses.
Team Interactions
reportedEngage with various members of the engineering, product, and leadership teams.
What to demonstrate
- Engage with various members of the engineering, product, and leadership teams
- Depth in Full-Stack Development
How to prepare
- Answer aloud and timed: Design a secure, idempotent payment processing system that integrates with third-party gateways like Stripe.
- Answer aloud and timed: How would you architect a real-time notification system to alert fundraisers when a high-value donor completes a pledge?
Feedback and Questions
reportedReceive prompt feedback and discuss your questions about the company.
What to demonstrate
- Receive prompt feedback and discuss your questions about the company
- Depth in Full-Stack Development
How to prepare
- Answer aloud and timed: Design the database schema for a flexible giving platform that supports recurring donations, split-campaign payouts, and multi-tenant access control.
- Answer aloud and timed: How would you design a rate-limiting mechanism to protect public-facing donation widgets from automated card-testing attacks?
System Design and Collaboration
reportedDeep dive into system design and evaluate cross-functional collaboration.
What to demonstrate
- Deep dive into system design and evaluate cross-functional collaboration
- Depth in Full-Stack Development
How to prepare
- Answer aloud and timed: Tell me about a time you had to make a technical trade-off to meet a tight product deadline. What was the outcome?
- Answer aloud and timed: How do you handle disagreements with product managers or designers regarding the implementation details of a feature?
PracHub editorial advice for the preparation topics above.
Think like a product owner
When writing code or designing a system, always relate your decisions back to the user experience. Ask yourself: How does this database schema affect page load times for a donor on a mobile connection?
Prioritize simplicity over cleverness
Write clean, readable code. Avoid over-engineering solutions to simple problems during coding assessments. A simple, working, and well-tested solution is always preferred over an incomplete, overly complex one.
Avoid skipping error handling in your coding sessions
At a fintech startup like Givzey, handling failures gracefully is just as important as writing the happy path.
Choose a category, try a prompt, then open its approach, worked solution or follow-up when you need it.
Implement a function to calculate payment schedules for a flexible giving plan, accounting for custom frequenc
Implement a function to calculate payment schedules for a flexible giving plan, accounting for custom frequencies and leap years.
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 function that takes an array of donor transactions and groups them by campaign, returning the top thre
Write a function that takes an array of donor transactions and groups them by campaign, returning the top three campaigns by total volume.
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?
Merge partitioned event streams into one ordered feed with bounded lateness
The read-model service consumes 64 log partitions carrying about 4,000 events per second in total. Each partition is ordered within itself, but partitions drift by up to 30 seconds, and the activity feed must present a tenant's events in occurred_at order. Produce the merge. State its complexity, the buffer it requires in events and in bytes, what happens when one partition is idle, and what you do with an event that arrives after you have already emitted its position. Payloads average 1 KB.
Approach
- Merge with a min-heap over the 64 partition heads keyed on (occurred_at, event_id): O(log P) per event and O(n log P) overall. The tie-break on event_id is what makes the output deterministic when two partitions carry the same millisecond, which matters because the feed is paginated and a non-deterministic order reorders pages under the reader.
- Emitting the heap head is only correct once every partition has produced everything up to that timestamp, so the emit condition is a watermark: the minimum across partitions of the highest occurred_at seen, less the allowed lateness. Events are held until the watermark passes them, which is what turns individually ordered streams into a jointly ordered one.
- Size the buffer from the lateness rather than guessing: 4,000 events per second times 30 seconds is 120,000 buffered events, and at 1 KB each about 120 MB of heap. That number is the real price of the ordering guarantee and belongs in front of whoever asked for it.
- Handle the idle partition explicitly, because it fails the feed rather than corrupting it: a partition with no traffic never advances its own maximum, so the watermark freezes and output stops entirely. Either every partition emits a periodic idle marker carrying the broker's current time, or the watermark falls back to wall clock for a partition silent beyond a threshold.
Follow-up
- The lateness budget is raised to five minutes. What is the new buffer, and what besides memory changes?
- The consumer restarts. Where does it resume from, and what does the feed look like for the first 30 seconds?
Design the database schema for a flexible giving platform that supports recurring donations, split-campaign pa
Design the database schema for a flexible giving platform that supports recurring donations, split-campaign payouts, and multi-tenant access control.
Approach
- Name the grain you start from and join outward from it.
- Check whether any join is one-to-many before aggregating, or the sums inflate.
- Say which index the query would use, and what makes it unusable.
- Handle the rows that do not match: that is usually the actual question.
Follow-up
- How does the query change if that join becomes one-to-many?
- What happens to this when the table is ten times larger?
Stop tag and share joins from fanning out a page
resource_tag is (resource_id, tag_id) with PK (resource_id, tag_id); resource_share is (resource_id, shared_with_user_id, permission). The tagged-and-shared listing inner-joins resource to both, filters tenant_id, tag_id = ANY($2) and shared_with_user_id = $3, orders by updated_at DESC and takes 50. Pages come back with fewer than 50 distinct resources and the total in the header is far too high. Explain the row multiplication, rewrite both the page query and the count query so each is correct, and name the index each one needs. PostgreSQL 16.
Approach
- Do the arithmetic against the predicates that are actually there. An inner join emits one row per matching child row, and both joins are filtered: tag_id = ANY($2) admits only the requested tags, shared_with_user_id = $3 admits one user's share rows. So a resource holding three of the requested tags and shared with $3 once yields three rows, not one — the multiplier is its count of matching tags times its share rows for that single user, and that second factor is 1 unless the table admits duplicate (resource_id, shared_with_user_id) pairs. LIMIT 50 then limits rows rather than resources, and COUNT(*) counts pairs — the header is the product, not the population.
- Reject DISTINCT as the fix. It deduplicates after the product has been built, so the planner must materialise and sort the fanned-out set before the LIMIT can apply, and it leaves any SUM or AVG in the same select list wrong.
- Rewrite both filters as semi-joins, keeping resource as the only row source: AND EXISTS (SELECT 1 FROM resource_tag rt WHERE rt.resource_id = r.resource_id AND rt.tag_id = ANY($2)) and the same shape against resource_share. A semi-join stops at the first match per resource and preserves the driving index order, so ORDER BY updated_at DESC, resource_id DESC LIMIT 50 still stops after 50 rows.
- Count with the same predicates and no join at all: SELECT count(*) FROM resource r WHERE r.tenant_id = $1 AND r.status = 'active' AND EXISTS (...) AND EXISTS (...). Nothing multiplies a resource, so the number is the population.
Follow-up
- The filter changes from 'any of these tags' to 'all of these tags'. Rewrite it and state what it costs relative to the ANY form.
- A resource can be shared with the same user twice under different permissions. Does your count change, and should it?
Given an API response containing nested organization data, write a utility to flatten the data structure for e
Given an API response containing nested organization data, write a utility to flatten the data structure for efficient frontend rendering.
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 an algorithm to detect duplicate donor profiles based on matching names, emails, and fuzzy-matched addr
Design an algorithm to detect duplicate donor profiles based on matching names, emails, and fuzzy-matched addresses.
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 secure, idempotent payment processing system that integrates with third-party gateways like Stripe.
Design a secure, idempotent payment processing system that integrates with third-party gateways like Stripe.
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?
How would you architect a real-time notification system to alert fundraisers when a high-value donor completes
How would you architect a real-time notification system to alert fundraisers when a high-value donor completes a pledge?
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 design a rate-limiting mechanism to protect public-facing donation widgets from automated card-t
How would you design a rate-limiting mechanism to protect public-facing donation widgets from automated card-testing attacks?
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 critical production issue under pressure. How did you communicat
Describe a situation where you had to debug a critical production issue under pressure. How did you communicate with stakeholders?
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 Givzey candidates report.
Prepare, practise & reflect
One practical outcome each day. Spend longer where you need it.
0 / 7 done01Map the Givzey loop
- Write out the reported sequence: Initial Conversation, Technical Capabilities Assessment, Team Interactions, Feedback and Questions, System Design and Collaboration.
- 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 5 reported rounds, with the weakest marked.
02Work Full-Stack Development
- Spend the session on Full-Stack Development, which Givzey candidates report being tested on.
- Write one worked example in Full-Stack Development and time yourself on it.
Deliverable: One timed worked example in Full-Stack Development.
03Work Front-End Development
- Spend the session on Front-End Development, which Givzey candidates report being tested on.
- Write one worked example in Front-End Development and time yourself on it.
Deliverable: One timed worked example in Front-End Development.
04Work Web Application Development
- Spend the session on Web Application Development, which Givzey candidates report being tested on.
- Write one worked example in Web Application Development and time yourself on it.
Deliverable: One timed worked example in Web Application Development.
05Answer out loud: Coding & Algorithmic Problem Solving
- Answer aloud, timed: Implement a function to calculate payment schedules for a flexible giving plan, accounting for custom frequencies and leap years.
- Answer aloud, timed: Write a function that takes an array of donor transactions and groups them by campaign, returning the top three campaigns by total volume.
Deliverable: Spoken answers to 2 reported Coding & Algorithmic Problem Solving question(s), under time.
06Answer out loud: System Design & Architecture
- Answer aloud, timed: Design a secure, idempotent payment processing system that integrates with third-party gateways like Stripe.
- Answer aloud, timed: How would you architect a real-time notification system to alert fundraisers when a high-value donor completes a pledge?
Deliverable: Spoken answers to 2 reported System Design & Architecture question(s), under time.
07Answer out loud: Behavioral & Cultural Alignment
- Answer aloud, timed: Tell me about a time you had to make a technical trade-off to meet a tight product deadline. What was the outcome?
- Answer aloud, timed: How do you handle disagreements with product managers or designers regarding the implementation details of a feature?
Deliverable: Spoken answers to 2 reported Behavioral & Cultural Alignment 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 you had to make a technical trade-off to meet a tight product deadline. What was the outc
Tell me about a time you had to make a technical trade-off to meet a tight product deadline. What was the outcome?
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 disagreements with product managers or designers regarding the implementation details of a f
How do you handle disagreements with product managers or designers regarding the implementation details of a feature?
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?
Why are you interested in building financial technology specifically for the nonprofit sector?
Why are you interested in building financial technology specifically for the nonprofit sector?
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 you had to make a technical trade-off to meet a tight product deadline. What was the outcome?
- 02
How do you handle disagreements with product managers or designers regarding the implementation details of a feature?
- 03
Why are you interested in building financial technology specifically for the nonprofit sector?
What is the tech stack at Givzey?
Givzey utilizes modern, scalable technologies tailored to rapid feature deployment and reliable performance. The stack heavily leverages JavaScript/TypeScript (React and Node.js), supported by robust relational databases and cloud-native infrastructure hosted on AWS.
Givzey Software Engineer candidate reports ↗How fast does the interview process move?
The typical interview loop from the initial recruiter screen to a final decision takes between two to three weeks. Givzey values clear communication and will keep you updated on your status at each stage of the process.
Givzey Software Engineer candidate reports ↗Does Givzey support remote work?
Yes, Givzey supports remote-first work environments for engineers based in the United States. The team leverages modern collaboration tools to ensure seamless communication, virtual pair programming, and cohesive team building across time zones.
Givzey Software Engineer candidate reports ↗What differentiates a good candidate from a great candidate at Givzey?
Great candidates do not just write code that passes tests; they demonstrate a deep curiosity about the business problem they are solving. Showing that you understand how your code impacts a nonprofit's fundraising goals or a donor's payment experience will make you stand out.
Givzey Software Engineer candidate reports ↗What topics does Givzey test in interviews?
Givzey interviews most often cover Account Executive (sales) Skills, Full-Stack Development, MLOps (Machine Learning Operations), Front-End Development, and Healthcare Domain (vertical sales). The exact emphasis depends on the specific role you apply for.
Givzey 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.
- 01Givzey 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.
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.
Rystad Energy Software Engineer Interview Guide
Prepare for Rystad Energy software interviews with worked Python validation, OOP and decorator examples, plus an ingestion case and practical checks.
Zwift Software Engineer Interview Guide
What Zwift asks Software Engineer candidates, from reported rounds and questions.
Zumper Software Engineer Interview Guide
What Zumper asks Software Engineer candidates, from reported rounds and questions.