Customer Enablement Manager

Baseten names Sheila Vashee Chief Marketing Officer. Former Figma CMO brings experience scaling some of technology's most influential product-led companies as Baseten enters its next phase of growth SAN FRANCISCO-(BUSINESS WIRE)-Baseten, the AI inference company powering the world's most advanced AI products, today announced that Sheila Vashee has joined the company as Chief Marketing Officer. Vashee most recently served as Chief Marketing Officer at Figma and brings two decades of experience building and scaling marketing, growth, and go-to-market organizations at companies including Figma, Ethos, Opendoor, and Dropbox. "Shelia is a proven leader with an incredible track record of elevating beloved, product-led technology companies into defining market leaders." Share Baseten has rapidly been assembling an experienced leadership team to build the intelligence infrastructure stack powering AI and enterprise leaders including Cursor, Harvey, HubSpot, Lovable, Notion, Vercel, and Wayfair. The company works with thousands of customers, processes 40-50 trillion tokens per day with infrastructure spanning 90 clusters and 20 clouds globally, and reported 20X YoY revenue growth in June 2026. Vashee joins the Baseten executive team alongside Matt Slagle (CRO), Gabe Stern (Chief Legal Officer), Sameer Paranjpye (Head of Engineering), and Vivek Patel (Head of Compute), who all also joined earlier this year. "Sheila is a proven leader with an incredible track record of elevating beloved, product-led technology companies into defining market leaders. The growth and scale she's seen in spades, together with her mastery of community, brand, and growth will be a major accelerant as we increasingly become the de facto inference provider powering the open frontier," said Baseten CEO Tuhin Srivastrava. Sheila spent three years at Figma leading marketing, customer support, communications, brand and growth during a period in which the company crossed $1B in revenue and completed its IPO. During her tenure, Figma doubled its product lineup, built out its growth motion, expanded support and operations and strengthened its enterprise business. Previously, Sheila was the VP of Growth at Opendoor, where she was responsible for growth across the buyer and seller marketplace. She took Opendoor from four to 21 markets and billions in GMV in a few years. Prior to that, she was the second marketing hire at Dropbox, where she helped 12x the Dropbox user base to 600M users and >$1 billion in revenue. "AI is still in its early innings, and the scale to which it will grow is beyond what we can comprehend. Baseten's vision and execution around inference and broader intelligence infrastructure has placed it squarely at the center of this tectonic shift," said Baseten CMO Sheila Vashee. "What truly captivated me was seeing how the community and ecosystem surrounding Baseten has coalesced in parallel with the company's growth. Companies are only beginning to understand what intelligence can unlock, and Baseten has been steadily building the infrastructure to make that possible." About Baseten Baseten is the inference company behind a new generation of AI products. The company builds systems software that runs the entire workload for AI applications - from GPUs and autoscaling to observability, billing, and developer tools - so teams can focus on models and user experience instead of infrastructure. Baseten's customers include leading AI companies such as Abridge, Clay, Cursor, Lovable, Mercor, and OpenEvidence and others building specialized models for their domains. Founded in 2019 and based in San Francisco, Baseten has raised over $2 billion to date from investors including Altimeter Capital, Battery Ventures, Blackbird, BOND, CapitalG, Conviction, Durable Capital Partners, Greylock, IVP, NVIDIA, Sands Capital, Spark Capital, Verified Capital, Wellington Management, 01A and others.

AI speeds up prototyping, but teams still need to distinguish decisions from assumptions. Figma's Designer Advocate argued that AI can make prototypes look finished too early, which can hide dangerous assumptions. The easier it is to make something look finished, the more important it is to understand what the team actually decided. That was the starting point for Hugo Raymond, Designer Advocate at Figma, in his talk at Infobip Shift 2026. His main point was that AI becomes a problem when it fills in the gaps before decisions are made, because it can hide unresolved decisions. A prototype shouldn't try to look like a finished product. Hugo reminded ShiftMag that the purpose of a prototype is to help the team test an idea. He compared it to a model airplane: A model doesn't try to be a real airplane. ShiftMag use it to study specific characteristics of the airplane. The problem, he argued, is that AI can now create a very convincing prototype even when the original idea is still incomplete: In the past, gaps were easier to see. If a screen did not exist, a flow ended in a dead end, or the team had not defined a certain state, you could clearly see that nobody had made that decision yet. AI can now connect the flow, generate data, create loading and error states, and add behavior that nobody explicitly defined. In the end, everything looks like one coherent product, even though the team designed some parts and the model simply filled in the rest. Visual polish no longer proves that the team solved the problem. According to Hugo, this creates an especially important problem for developers: the more finished a prototype looks, the more authority ShiftMag give it and the more likely ShiftMag is to treat it as a specification that developers simply need to implement. Hugo warned that a polished prototype no longer means that someone has thought through every edge case, business rule, or technical constraint. One of his key points was that polish used to be expensive. If something looked highly refined, you could at least assume that someone had spent time thinking through the problem. Now, the tables had turned: AI has broken that connection. The first draft can now look like the final iteration. Teams therefore need to make a much clearer distinction between what they have actually decided and what is still only an assumption. Code is not the opposite of design. Hugo doesn't think the solution is to move design back into static mockups, quite the opposite: code is not the opposite of design but one of the materials ShiftMag use to design: A code prototype can use real data, react to unexpected input, and show states that a designer did not draw in advance. AI has made this kind of experimentation much more accessible. Still, code and a design canvas don't show the same things. Code is very good at showing what happens, while the canvas can do a better job of preserving why the team made a certain decision, which alternatives the team considered, and what the team still needs to solve. Because of that, he sees a future where teams combine different materials depending on what they're trying to learn. AI speeds up execution, but not decision-making. The final and most important point of his talk focused on the limits of automation. AI can take over a lot of repetitive work, speed up prototyping, and help teams test ideas more cheaply, but making something faster does not mean ShiftMag understand what to make any better. Hugo therefore makes a distinction between friction worth removing and friction that serves a purpose: ShiftMag can automate copying, waiting, and repetition. ShiftMag should not automate comparing options, testing assumptions, discussing trade-offs, and questioning decisions. As he pointed out, these moments help teams develop the judgment that AI cannot simply replace. "When almost every prototype can look finished, how convincing it looks is no longer the most important thing," he said. What matters is whether the team can still clearly see what it has decided, what it has assumed, and what it still needs to solve.

Figma Auto Layout: the complete 2026 guide. If you've ever resized a Figma frame and watched every element inside it stay exactly where it was - overlapping, spilling out, or leaving a huge gap - Auto Layout is the fix. It turns a static frame into one that resizes and rearranges itself as content changes, the same way a real webpage or app screen actually behaves. What Auto Layout actually does. Elements inside an Auto Layout frame are arranged automatically based on direction, spacing, padding, and alignment. Add a new button, remove a line of text, or resize an element, and everything else in the frame adjusts on its own - no manual repositioning. How to add Auto Layout. Select one or more layers, then either press Shift+A or click Add auto layout in the right sidebar. Figma wraps your selection in a new auto layout frame using sensible defaults, which you then adjust. The core properties. Direction. Vertical stacks elements along the y-axis - anything you add, remove, or reorder follows top to bottom. Horizontal does the same along the x-axis, left to right. This is the single most important setting, since it decides how the whole frame behaves. Spacing and padding. Spacing controls the gap between items inside the frame; padding controls the space between the items and the frame's own edge. Both can be set independently per side. Alignment. Controls how items line up within the frame - left, center, right, top, bottom, or stretched to fill the available space. Important: check which Auto Layout version you're on. Figma rolled out a new Auto Layout version in 2026 that changes how padding, inside strokes, and auto-gap stacks behave compared to the original. The older version (now called Legacy) is still available frame by frame, but Figma has said it will be phased out by January 2027. Check a frame's Layout panel - it will say either Latest or Legacy. If you're starting a new file, use Latest; if you're opening an older project, expect to see Legacy frames until you update them. When to use Auto Layout. Reach for it any time you're designing something with content that could realistically change length - buttons, list items, cards, form fields, navigation bars. It's less necessary for a one-off hero illustration where nothing will ever resize. As a rule of thumb: if the real, coded version of this element would need CSS flexbox to work, it should probably be an Auto Layout frame in Figma. Frequently asked questions. What's the keyboard shortcut for Auto Layout in Figma? Shift+A adds Auto Layout to your current selection. Can I nest Auto Layout frames inside each other? Yes - nesting Auto Layout frames is a common way to build complex, fully responsive components like cards or navigation bars. Should I use Latest or Legacy Auto Layout? Use Latest for any new work. Only stay on Legacy if you're working inside an existing file that hasn't been updated yet, and plan to migrate before Figma phases it out. Auto Layout is one of the fastest ways to make a Figma file actually reflect how a real interface will behave. If you'd rather have that translated into a live, coded site without doing the handoff yourself, see its UX/UI design services.