№ 07 How it works · The four moments

Four moments. Every application.

The feature tour walks the four screens you'll use. This page walks the four moments that fire under the hood every time TimeBaQ submits an application — the form fill, the cover letter, the Q&A library lookup, the CAPTCHA solve. One chapter per, with the actual moving thing on the right.

I. Form filling · the part you'd otherwise type

Every application form is a re-enactment of the last one. Name, email, phone, address, eligibility, work history, the same paragraph about why you want this role — retyped, in a slightly different layout.

TimeBaQ reads the form, matches each field to your saved profile, and fills it. Name → name field. Phone → phone field. Résumé → file picker. The fields it can't auto-match it flags so you can spot-check before it submits.

~95% of fields auto-filled with zero review on a typical Indeed/LinkedIn form. The remainder are bespoke fields the AI handles in the next chapter.

II. AI cover letter · a tailored first draft, every time

The blank cover-letter page is what kills application momentum. You either ship a generic AI draft (which ATS systems flag with ~80% accuracy) or you stop applying for the rest of the evening.

TimeBaQ reads the listing, reads your profile, and writes a first draft in seconds. The Power tier learns your tone from a handful of samples and tunes future drafts to match — one that reads like you wrote it, on Tuesday at 4pm, after coffee.

All tiers: per-job draft. Power tier: voice-tuned from your samples. Always: proxied through Cloudflare AI Gateway with logs off.

Job description

Senior Backend Engineer · Stripe

We’re hiring engineers with strong Postgres experience and ETL background. Familiarity with payment systems a plus. Remote OK.

Generated in 8 seconds

Dear Hiring Team,

I noticed you’re looking for backend engineers with strong Postgres and ETL experience. I built a real-time analytics pipeline at Bramble Health that processed 12M events/day across 8 Postgres schemas — happy to walk through the architecture choices.

Payment systems are new ground for me, but I’ve shipped accounting-adjacent systems and read about Stripe’s idempotency-key approach. I’d love to get my hands dirty there.

Available for a 30-min intro call this week or next.

— Alex

III. Q&A library · screening questions, answered once

"Are you authorized to work in the United States?" — you've typed that yes six thousand times. "What are your salary expectations?" — you've typed that one six thousand more.

Every screening answer TimeBaQ sees becomes a saved entry in your local Q&A library. The next time the same question shows up — on a different platform, in a different layout — TimeBaQ auto-fills it in one keystroke. Anything new, the AI drafts using your profile, then asks if you want to save it.

42saved average library size after two weeks of dogfooding. The top answer alone fired 47 times on the first month's apps.

IV. CAPTCHA · three kinds, resolved in the background

The place every competitor stumbles. LazyApply's most-cited Trustpilot complaint is broken Indeed CAPTCHAs. The application looks submitted, but no one ever sees it on the other end.

TimeBaQ handles all three of the CAPTCHAs job sites actually use — Cloudflare Turnstile, hCaptcha, and reCAPTCHA — through a paid solver, resolved in the background while the rest of the application keeps going. Each tier ships with a monthly solve quota; nothing to configure.

Resolved: 3 types. Typical latency: <8s. On fail: retry, then escalate to the next platform.

End of how it works

Four moments, one queue.

All four fire on every application TimeBaQ submits. The screens that show them are on the features tour; the visuals are on the screenshots page.