Alabama's network of builders & guidesAlabama's network of builders & guidesAlabama's network of builders & guidesAlabama's network of builders & guidesAlabama's network of builders & guidesAlabama's network of builders & guidesAlabama's network of builders & guidesAlabama's network of builders & guides
TT

Tsegereda Tefarie

BuilderWashington D.C., DC, USA
Where they're at

I’m already building something and want to take it further

Something they're proud of

m building a job application dashboard that rivals tools like Teal HQ — an all-in-one system so I don't have to pay for fragmented tools or lose track of where I am in every pipeline. Building it has taught me how to vibe-code and what systems thinking actually feels like in practice. I plan to keep using it even after I land a role so switching jobs is always efficient. I'm also in the early stages of a startup in the VC/AI space, but that's a story for another question.

Weekly submissions (7)
Week 1

Ops Command Center – I'm making a LinkedIn Job Search Automation Tool that generates one-click search URLs with hidden time filters (past hour / past 24 hours) to help job seekers see and apply to fresh postings before the majority of other applicants.

Week 2

Execute AI It automates finding, tracking, and applying to jobs, helping job seekers work smarter, not harder.

Made the web app version of it and 13 of my features work of the 26. Will be doing a demo of some of my features cause why not at this point.

Week 3

Execute ai and is a job search automation tool designed to help job seekers work smarter, not harder.

Here it is: --- Built a 10 second coded promotional video for Execute AI using Remotion and Claude Code — branded with my owl mascot Owly and my own voice. Published my week 3 LinkedIn post with the video attached. Relaunched my Twitter to build in public and started engaging with VCs and founders in the startup community on day one. Two people from my audience asked to use Execute AI before launch which validated the problem and the positioning. Also continued refining all five modules on the live site. Biggest struggle is managing Execute AI, Worth It AI, LvlUp dealflow, and a job search simultaneously. But the momentum is real and I am not stopping.

Week 4

Execute.ai — a job search command center that automates finding, tracking, and applying so job seekers spend their hours interviewing, not filling out forms.

Week 4 of the Unlock Alabama 8-week builder challenge. I launched Execute.ai on Product Hunt, Reddit, and with three beta users. A senior associate from a global investment bank reached out after the Product Hunt launch. Nine people followed the product. Four followed it on Product Hunt. People who tried it said the "last hour" job filter was smart and the fit score saved them from applying to the wrong roles. On Reddit, job seekers said they're either using complicated systems that get in their way or just a folder with printed pages because nothing else works well enough. I also used Feedback Labs — it told me what I already knew: I need to move from a waitlist to a live demo where people can paste a job listing and see it work right away. That's what I'm working on next. I'm using Execute.ai myself and critiquing it because if I wouldn't use it, why would anyone else?

Week 5

Execute.ai — a job search command center that automates finding, tracking, and applying so job seekers spend their hours interviewing, not filling out forms.

Week 5 of the Unlock Alabama 8-week builder challenge. The challenge was to talk to users, so I started with myself — the only user I had at the time. I used Execute.ai to track my own applications and walked myself through the full journey from landing page through all seven workflow steps. I caught things I would've missed otherwise — the onboarding wasn't clear, the flow didn't feel natural — so I fixed it. I asked myself the hard questions: "When was the last time you had this problem?" "How are you solving it today?" "What would have to be true for this to be worth paying for?" If I couldn't answer these questions honestly, I couldn't expect anyone else to either. I also shared a post about the front end being polished and the back end being a skeleton — keeping it real about where the product actually is. I reached out to potential users and have real interviews scheduled for next week. Next up: Supabase, user auth, real data persistence, and real user interviews. Talking to myself was step one. Real users are step two.

Week 7

Execute.ai — a job search command center that covers the whole journey: find jobs, track applications, score your fit, generate interview answers, polish your resume, and see it all on one dashboard.

Shipped my one-minute pitch video for Execute.ai this week and posted it with a breakdown of what I learned building and launching. Biggest lesson: repositioning from "job tracker" to "command center" is what made people actually get it. Also tightened the pitch deck — verified competitor pricing, fixed a few credibility gaps, and reworked the market sizing to be honest about what's illustrative math vs. sourced data. Continuing to prep for the paid tier launch.

Week 8

Execute.ai — AI-powered job search tracker that finds early postings, tracks applications, and scores resume fit before you apply.

This week I'm preparing to present Execute.ai live at Builder Nights DC on Thursday—only a handful of builders were selected to demo in-progress AI projects to founders and investors. I didn't just submit an application. I walked a judge through the live product, and out of everyone who applied, I was one of the few picked to take the stage. Execute.ai started as a vibe-coded mess of App Script on a Google Sheet—just features I hacked together to fix my own job search chaos. I used it myself to land my current role as a venture scout, and now 3 other people are using it too. Still early. Three users, one stage. But real people are using something I built out of my own frustration, and that's what I'm most proud of this week.