What the work actually involves
You will spend most of your time producing and critiquing research artifacts rather than writing them for a client base. A typical task set might ask you to build a three-statement model for a mid-cap name from its 10-K and last four earnings releases, then write the reasoning trail an analyst would follow — why revenue was segmented that way, which margin assumption is the swing factor, what a valuation bridge from EV/EBITDA to DCF implies. Other tasks flip the direction: a model output is placed in front of you and you write a detailed evaluation of where its estimate revision logic, peer set construction, or catalyst identification breaks down. Event-driven work appears too — a print lands, and you produce the concise update note plus the rubric explaining what a good note must contain.
What the platform screens for
micro1's screen is AI-conducted and pushes on specifics. Expect to be asked which tickers you covered, who your publishing analyst was, how many names you carried, and what your model looked like at the line-item level. Vague sector claims collapse fast under follow-up; the interviewer will ask for a sector-specific metric and then ask why it matters more than the obvious alternative. The other half of the assessment is evaluation judgment: can you say clearly why one piece of analysis is better than another, and can you write that reasoning down in a way a non-expert reviewer could audit. No AI or machine learning background is expected or credited.
Logistics
- Contractor engagement, fully remote, project-scoped rather than salaried.
- Asynchronous — task batches with deadlines rather than fixed hours; most contributors commit 10–20 hours per week, and availability is explicitly discussed in screening.
- Observed pay band of $175–300/hr, set by sector depth and seniority; rates are as reported, not guaranteed.
- Work is written-output heavy, so expect to be judged on prose quality alongside numerical accuracy.