Surely it will be called Antigravity Notebook in a few months.
HN user
getravi
Location: SF Bay Area Remote: Yes, also open to hybrid or onsite in the Bay Area Willing to relocate: No, but open to Bay Area onsite roles Technologies: Python, SQL, TypeScript/React, Node.js, PostgreSQL, Snowflake, dbt, Airflow, APIs, Anaplan, NetSuite, Workday, Salesforce, Tableau, Power BI, Microsoft Power Apps, Claude Code, Codex, Hermes Agent, Vercel v0 Résumé/CV: https://www.linkedin.com/in/getravi/ Email: getravi at gmail dot com
Finance systems and data platform leader with 18+ years across eBay, Sonder, Adobe, and McAfee. I build planning platforms, internal tools, data products, workflow automation, and decision-support systems for Finance, Operations, and executive teams.
Most recently, I own FP&A planning systems and the Anaplan Center of Excellence at eBay. Previously, I founded the Finance Systems function at Sonder, migrated FP&A from Adaptive Insights to Anaplan, built planning/data pipelines with Snowflake, Python, SQL, dbt, and Airflow, integrated systems like NetSuite, Workday, Salesforce, and Tableau, and supported 150+ users across Finance and Operations. At Adobe, I built enterprise planning systems supporting $10B+ in annual spend.
I’m looking for roles where I can keep moving closer to software engineering while using my finance systems and data background: product engineering, data engineering, internal tools, forward-deployed engineering, technical product, finance/operations platforms, or AI workflow automation.
Best fit: teams building software around complex business workflows, data integrations, planning systems, analytics, automation, and tools for domain experts. I bring strong product judgment, finance/operations domain depth, systems thinking, and hands-on experience building with modern data tools and AI-assisted engineering.
Location: San Francisco Bay Area, CA
Remote: Yes
Willing to relocate: For the right opportunity
Technologies: AI Agents, LLMs, Workflow Automation, Anaplan, Adaptive Planning, Pigment, SQL, Python, Snowflake, dbt, Tableau, Power BI, NetSuite, Workday, Salesforce, Financial Systems, FP&A, Analytics Engineering, Data Platforms, Business Systems
Résumé/CV: linkedin.com/in/getravi
Email: getravi at gmail dot com
Finance Systems, Analytics, and AI Automation leader with 18+ years of experience building internal platforms, planning systems, data products, and automation solutions at enterprise and high-growth technology companies.
My background sits at the intersection of finance, operations, data, and software. I’ve built finance systems functions from the ground up, led enterprise planning transformations, implemented data platforms, and recently focused on AI-native workflows and agentic automation.
Areas where I can add value:
* AI agents and internal automation * Finance and business systems leadership * FP&A platforms (Anaplan, Adaptive, Pigment) * Data and analytics platforms * Process redesign and operational scaling * Enterprise software product strategy * Technical program and cross-functional leadership
Open to full-time leadership roles, individual contributor roles with significant ownership, consulting engagements, and advisory work.
Location: San Francisco Bay Area
Remote:Yes
Willing to relocate: Yes
Technologies:
Résumé/CV: https://www.linkedin.com/in/getravi (happy to send you a pdf over email)
Email: getravi at gmail
Tech-forward finance systems / data engineer (18+ yrs) at the intersection of FP&A, data infra, and internal tooling (currently at eBay; previously Sonder, Adobe).
I build systems that replace spreadsheet-heavy workflows using Python, SQL, Snowflake/dbt/Airflow, and Anaplan.Recently focused on using AI coding assistants to create real software products. I love to create deterministic systems using generative AI. It has truly unlocked my capacity to build at a rapid pace.
Happy to connect.
Location: San Francisco Bay Area
Remote:Yes
Willing to relocate: Yes
Technologies:
Résumé/CV: https://www.linkedin.com/in/getravi (happy to send you a pdf over email)
Email: getravi at gmail
Tech-forward finance systems / data engineer (18+ yrs) at the intersection of FP&A, data infra, and internal tooling (currently at eBay; previously Sonder, Adobe).I build systems that replace spreadsheet-heavy workflows using Python, SQL, Snowflake/dbt/Airflow, and Anaplan.
Recently focused on applying LLMs to real workflows (financial analysis, variance commentary, lightweight agents on top of data pipelines).
Interested in applied AI / data-product roles or forward deployment. Strong bias toward practical systems and shipping end-to-end.
Happy to connect.
Agreed. It matches my experience as well. I boil it down to personality and orientation than seniority in the org honestly. I have seen VP/Director level people who secretly tinker in SQL alongside delegation 99% of the time. Those who want to learn SQL will do it soon and the rest have some kind of mental block.
What are those constraints? Really usable SQL for Business people can be learnt in a day long workshop or less time. If they can do Excel, they can do SQL too.
Never knew Improv existed. There are tools that are similar to the vision of Improv. I use Anaplan at work everyday and it is exactly what a modern cloud based SaaS version of Improv would feel like. It is a multi billion dollar company and it worked because it did not go after the spreadsheet space but played along nicely with it.
The Improv article concludes "the key strategy mistake was to try to market Improv to the existing spreadsheet market. Instead, if the product were marketed to a segment where the more structured model was a ‘feature’ not a ‘bug’ would have given Lotus the time to learn and improve and refine the model to a point where it would have satisfied the larger market as well." and Anaplan seems to not have made this mistake. They have carved out a niche in the EPM (Enterprise Performance Management) market.
Thank you. I will be more thoughtful next time.
Water is wet.
Grifters gonna grift.
I would go even further and say that "GROUP BY ALL" and "ORDER BY ALL" should be implied if not provided in the query.
EDIT: Typo