At the TechEquity AI Summit in Sunnyvale, California, Joseph Spisak, Director of Product at Meta’s Superintelligent Labs, revealed that the company is internally using a ChatGPT-like tool called “Metamate”​ to assist employees in preparing annual performance reviews.
“When it’s time for my annual performance review, I just call on Metamate, and it searches through all my documents—pulling together my work accomplishments, achievements, and feedback from others. It’s really useful,” Spisak said.
When asked whether employees might try to “game the system” or use the AI to inflate their performance ratings, Spisak joked that workers would likely find loopholes or hacks.
He also noted that Metamate​ is not limited to performance evaluations. The tool, trained on internal company data, is widely used for other internal tasks such as application development.
An anonymous Meta employee told Business Insiderthat while some staff are indeed experimenting with Metamate to draft performance reviews, the quality of the AI-generated output varies. Without detailed context about specific projects, the AI often struggles to accurately reflect individual contributions. However, the employee added that they still use Metamate to generate templates for peer feedback, which they then manually refine with concrete examples to improve efficiency.
Beyond performance reviews, Meta’s AI tools serve multiple functions. Models trained on internal data help with software development. Like other Silicon Valley tech firms, Meta is accelerating the internal integration of AI technologies. IT Homereported that Meta is also using an AI coding assistant called “Devmate”, and is developing gamified dashboards and data panels to track how employees are using AI tools.

How to interpret the development beyond the headline

Fast-moving technology and crypto stories should separate confirmed facts from forecasts, market reaction and interpretation. Product launch, adoption, liquidity, regulation and execution can all determine whether an early headline becomes a durable shift.

The useful follow-up is concrete evidence: shipped capability, user growth, audited transactions, financial guidance or regulatory decisions that confirm or weaken the initial narrative.

Watch second-order effects

Major developments can change incentives for developers, creators, exchanges, infrastructure providers and users. The practical impact may appear through costs, standards, distribution or policy rather than through the headline event itself.

Keeping long-term scenarios conditional makes later updates easier to interpret without rewriting early speculation as fact.

Separate market sentiment from product execution

Price movement and social attention can react instantly, while technology deployment takes longer. A useful analysis asks what operational milestone would prove that the story has changed real behavior.

That milestone might be production use, a measurable cost change, a regulatory approval or sustained customer demand rather than one day of market volatility.

Identify the assumptions behind the forecast

Every long-term scenario depends on assumptions about adoption, competition, capacity and policy. Making those assumptions explicit helps readers understand what evidence would cause the outlook to improve or weaken.

Practical implementation check

Before adopting the mechanism described above, define the exact business rule, who controls it and what evidence will show that it worked. Test the failure path as carefully as the successful path, especially when rights, payments or wallet actions are involved.

The final system should also document versioning, rollback and the assumptions that may become stale over time. That turns a one-off experiment into an operating model that creators, users and developers can understand.