Describe a time when you had to get a project or initiative completed with limited resources.

In my internship, I was helping add an export feature to an internal dashboard, and about a week before the deadline we learned the engineer mentoring me had to switch to a production issue, so I had much less support than expected. I listed the pieces that were actually required for the first release and checked with my lead which ones mattered most to users. Instead of building every export option we had talked about, I focused on the CSV path, basic validation, and a clear error message, and I used a smaller test data set so I could verify the flow without waiting on a full environment setup. I sent short updates each day so there were no surprises and asked targeted questions when I got stuck rather than waiting. We shipped the limited version on time, and it covered the main workflow the operations team needed. The other formats were added later, but the urgent need was solved with the time and support we had.

At a small non-profit where I’m the only developer, I was asked to build an online registration page for a community workshop with just two weeks and no budget for a designer or paid tools. I mapped out the absolute must-have fields with the program manager, picked a clean open-source template, and integrated a free payment provider’s basic form instead of trying to customize a full checkout flow. To keep it accessible, I made the page mobile-first and reduced the questions to essentials so staff could easily process signups by hand if needed. I enlisted a couple of volunteers to run quick usability checks on different phones and iterated based on their feedback. I also wrote a one-page guide so non-technical staff could edit copy and export attendee lists. The page launched on time, the workshop filled to capacity, and staff appreciated having something low-maintenance they could keep using for future events.