Computing for All is a nonprofit organization committed to helping those who are under-represented in the IT industry to prepare for and secure equitable, upwardly mobile careers in information technology. We have been serving the Seattle area for 5 years through our innovative project work education model that prepares students to succeed in technical careers. We are committed to helping young adults experience a career in Information Technology through both virtual instruction and active engagement in a hands-on, immersive, blended learning setting. Employer mentors provide structured training experiences for students to develop IT skills applying academic learning to real-time work.
Computing For All doesn't have any open opportunities at this time. Check back later for new postings.
You're building a simple REST API for a small "Task Tracker" web app where users can create, read, update, and delete their tasks (title, status, due date). Scenario: "The Task Tracker API" Design the basic structure for the API (routes, request/response format), explain how you'd handle errors, and describe one simple test case. Example: GET /tasks → returns list of user tasks POST /tasks → creates a new task with title + due date Record a video walking through your API design and reasoning. You'll also submit a written document outlining your endpoints and testing approach.
This challenge is for the UX Designer role at CFA (Community Financial Access), an early-to-mid level position in the UI/UX Design / Web & Digital Interface Design pathway. Scenario — "Simplify the Appointment Booking Flow" A community nonprofit's site lets users book appointments for free tech support. Feedback shows that users often abandon the booking process midway, the form feels long and confusing, people aren't sure what information is required versus optional, and confirmation and next steps aren't clear. Your Task Design a simpler, clearer booking flow that reduces friction and improves completion rate, provides clear guidance at each step, builds user confidence throughout the process, and can be tested and validated with real users. Propose specific changes to the flow such as fewer steps, better layout, or clearer messaging, and explain how you'd measure success. Record a video walking us through your approach. Submit written artifacts including your flow redesign summary and testing plan.
Scenario — "The Task Tracker API" You're building a simple REST API for a small "Task Tracker" web app. Users need to be able to create, read, update, and delete their tasks. Each task includes a title, status, and due date. Your Task Design a reliable API that provides clear routes and request/response formats for task management, handles errors and invalid input safely with appropriate status codes, follows REST conventions and best practices, can be tested reliably to ensure it works correctly, and is documented well enough for other developers to use. Focus on clarity, testing, and reasoning rather than complex code. Record a video walking us through your approach and submit written artifacts for your API design and reliability plan.
This challenge is for the Junior Web Developer role at CFA (Community Financial Access), an entry-level position in the Front-End / Web Development pathway. Scenario — "Make the Sign-Up Page Work for Everyone" A small business's website has a simple email sign-up page. Users have reported that it's hard to read on mobile devices and doesn't clearly communicate why they should sign up. Your task is to design improvements to make the page accessible to all users, including those using screen readers or keyboard navigation. The page should be readable and user-friendly on mobile devices, and more engaging with clear messaging about why users should sign up. Your improvements should be built using semantic HTML, CSS, and basic JavaScript. You don't need to write complete code—just explain the structure, improvements, and reasoning behind your decisions. Record a video walking us through your approach and submit your layout plan and enhancement notes as supporting documents.
