Software Engineer New Grad

Introducing App Templates: skip the blank page. Colin Dolese Product Manager July 8, 2026 Today Sigma Computing Inc. is launching App Templates in public beta. App Templates are a curated collection of Sigma-built templates covering common app use cases. Go from zero to a working app in minutes, connected to your own warehouse data. Starting from scratch is hard. Sigma gives teams everything they need to build powerful, AI-driven applications: Input Tables for writeback, Sigma Agents that take action, AI Columns to enrich and classify data, and action sequences that trigger external systems. But knowing how to structure those pieces for a new use case, or even knowing what's possible in the first place, isn't obvious from a blank workbook. Most teams end up doing one of two things: spending significant time figuring out patterns that others have already solved, or not starting at all. A revenue operations team building a territory management app has to hand-wire the input table logic, the layout, the controls, and the agent workflows from zero. A finance team tackling demand planning does the same. The patterns exist - but until now, there's been no good way to see them in a working context. That's what App Templates are for. Any time you're tackling a new use case, they give you a faster, better starting point than a blank canvas. How App Templates work in Sigma. Choose a template for a common use case. Sigma's template system lets you start from a working example rather than an empty workbook. App Templates are a new collection of Sigma-built templates covering common use cases, starting with 10 today: Each template opens with sample data pre-loaded so you can see exactly how the app works before connecting it to your own warehouse. Connect your own data. Once you've selected a template, connecting it to your own warehouse is a guided flow. Most of the sample data in each template is written directly to your warehouse using Sigma's writeback functionality - so swapping to your own data is largely a matter of pointing the connection to your own tables. A small number of common datasets, like users, will need to be mapped to your own equivalents. Learn the patterns that make apps powerful. Each App Template is a working example of Sigma's most powerful capabilities: Input Tables, agent workflows, AI Columns, and action sequences. Seeing these patterns in a working app is a fundamentally different experience than reading about them. For teams new to building in Sigma, App Templates are the fastest path to understanding what's possible. For experienced builders, they're reusable patterns - open a template, study the structure, and take what you need for your next build. Some templates are close enough to production-ready that teams can open one, connect to their own data, and ship with minimal customization. How Sigma Labs builds App Templates. Every App Template is built by Sigma's Labs team, a group of product experts who spend their time building real apps that can easily be adapted to meet each customer's unique needs. Each template is carefully crafted to reflect how a production app should actually be structured, and ships with a built-in ReadMe page and short video walkthrough so you can get oriented before you start customizing. The Project Management template, called Throughline, is a good example of what that means in practice. Throughline is a complete project management workspace, built entirely on Sigma Input Tables. It includes milestone planning, a Kanban board, ticket tracking, and a portfolio view across all active projects. A project manager can plan milestones, track execution, flag blockers, and communicate status to stakeholders, all from a single app where every page stays in sync. Update a ticket on the Board and it reflects immediately on the Home page and in the Plan. The Kanban board is one particularly strong example of the power of Sigma's app-building capabilities. It's a live, interactive board with columns for To Do, Blocked, In Progress, and Done. It's fully functional, built on Sigma's repeater element and Actions framework. Creating a new ticket triggers a multi-step flow that uses Sigma's AI capabilities to check for duplicate tickets before writing the new record to your warehouse. That's the pattern App Templates are designed to surface: how to put the pieces together in a way that actually works. Governed by default, warehouse-native throughout. App Templates are built on the same warehouse-native architecture as everything else in Sigma. When you open a template, Input Tables are created directly in your warehouse, so you're not working with copies or static files. Access controls, row-level security, and column masking you've already configured on your connection carry over automatically. There's nothing to re-govern when you go from template to production app. Start building with App Templates. App Templates are available in public beta for all Sigma customers today. Open a new workbook and select a template from the gallery to get started, or reach out to your account team to learn more. New to Sigma? Request a demo or start a free trial to see App Templates alongside the rest of the platform. Frequently asked questions. Can I customize an App Template after opening it? Yes. Every template opens as a fully editable workbook. You can modify any element: add columns, adjust the layout, change the agent logic, or extend the app with new capabilities. Can I still create my own templates? Yes. App Templates are a curated set of Sigma-built templates, but Sigma's template system supports custom templates too. Any workbook can be saved as a template and shared within your org. How is this different from Sigma Public? Sigma Public is a public sandbox where anyone can explore Sigma-built demos and community examples without logging in. App Templates live inside your own Sigma org - you connect them to your own warehouse data and own the output. What data platforms do App Templates work with? App Templates work with any warehouse connection in Sigma that supports writeback, including Snowflake, Databricks, BigQuery, and Redshift. See the documentation for details on source swap behavior by connection type. Are there any requirements to use App Templates? To take advantage of all AI app features included in App Templates, enabling Sigma's writeback and Sigma Agents functionality is recommended. But all App Templates can still be viewed and explored in all Sigma orgs even without these features.

Sigma Agents: introducing the new Agent Builder Assistant. Riley Gamboa Sr. Strategic Marketing Manager July 6, 2026 Building a custom AI agent in Sigma used to mean clicking through configuration screens and setting up each tool by hand. Now you can describe the workflow you want in plain language and let Sigma handle the setup. The new Agent Builder Assistant ("ABA" for short) is a natural language interface for designing Sigma Agents, the custom AI agents that run inside the security and governance of your cloud data warehouse. The Agent Builder Assistant is the first update in "Month of Agents," a July series where Sigma Computing Inc. release a new video each week covering a recent enhancement to Sigma Agents. Use ABA to: * Add a data source and get suggestions for agents you can build from its metadata * Describe a workflow in plain language and turn it into supported action tools * Generate and update your agent's instructions automatically Watch the full video above to see the Agent Builder Assistant in action, or read the accompanying transcript to understand how its Product, Design, and Engineering teams approached the ABA build. Of course, the best way to learn about Sigma Agents is to build one yourself. Sigma Agents are a public beta feature, and they're available by default to all Sigma customers that have enabled an AI provider. Reach out to your Sigma representative with any questions. If you're not a Sigma customer yet, you can request a demo or start a free trial to learn more. Next week in its Month of Agents series, Sigma Computing Inc.'ll cover governance, permissions, and using warehouse agents as tools. Return to the Sigma blog or follow its team on LinkedIn, X, or YouTube to catch the latest updates. Read on to see the full video transcript. What's new in Sigma's Agent Builder? Zalak: Hey, everyone. My name is Zalak Trivedi. I'm a Director of Product at Sigma. Over the next few weeks, Sigma Computing Inc. is going to be talking about agents: the way you build them, govern them, permission them, observe them, and a little bit about what's coming in the future. With me, I have Justine and Juwon, who are going to be talking about Agent Builder. You guys want to introduce yourselves? Juwon: I'm Juwon. I'm a Product Designer working on agents. Justine: I'm Justine. I'm a Software Engineer also working on agents. Zalak: Let's start simple. For someone who hasn't used Agent Builder in the last few weeks since the update, tell me what's new. Juwon: The new updates Sigma Computing Inc. has for agents give you a more intuitive way of building them. No matter who you are, whether you're a more technical user or an average business user, you can build an agent in a couple of clicks and a couple of prompts. Sigma Computing Inc. has also updated it so it's more data-source forward, so the first step you take is adding a data source to an agent so that agent has context. And Sigma Computing Inc. has the Agent Builder Assistant on the left (Sigma Computing Inc. call it ABA) to help you build the agents. How does the Agent Builder Assistant (ABA) turn natural language into agent tools? Zalak: In its first release, Sigma Computing Inc. had natural language instructions, which was pretty cool. I know people were ping-ponging between different systems for that. But Justine, you added natural language to tooling capabilities. Talk to me a little bit about that. Justine: Previously, you could set up your tools in the Agent Builder, but that required a few different clicks for manually configuring your tools. That process was a little tedious, because you'd be manually setting up every single configuration for each tool. What Sigma Computing Inc. introduced is that ABA is now able to build these tools for you. You write a couple of sentences in natural language, just describing your workflow, and ABA looks at that prompt, compares it to the list of supported tools Sigma Computing Inc. has, and translates your prompt into those tools. Zalak: Got it. Maybe give me an example. Justine: A common example is you want to filter your data down by some control value, and then you want your agent to run a query against that filtered data and return results. You describe this workflow to ABA, and ABA sees that Sigma Computing Inc. can set up a Set control value action tool, which updates your control value to whatever input the user requests. ABA also knows to update the instructions on the agent to describe how to actually use this tool, so the next time you pull up your agent, it knows exactly what to do. Zalak: Very cool. So it works with its entire actions framework. Justine: Exactly. Why did Sigma redesign the Agent Builder? Zalak: Juwon, before this redesign, I'm sure Sigma Computing Inc. thought through a lot of the user journeys. Where did people typically get stuck, and how are Sigma Computing Inc. helping them now? Juwon: One of the main pain points Sigma Computing Inc. wanted to solve with the Agent Builder redesign is that Sigma Computing Inc. wanted the agent-building experience to be as efficient and impactful as possible. Previously, users were kind of daunted coming up to Agent Builder, not necessarily knowing what the first step was or what agent they could make, and needing a couple rounds of prompting to get to the point they wanted to reach. With the new design, Sigma Computing Inc. is introducing a way to immediately get to an agent. For example, if you add some data sources using ABA, ABA can make an LLM tool call to suggest what agents you could possibly build. So within a couple of clicks, you're able to experience and interact with an agent, and then use that as a starting point for your agent-building experience. Zalak: Got it. So it's really for any technical level, from the marketing team all the way to somebody who knows how to write SQL. Very cool. Alright, Justine, do you want to show a quick demo of how this looks? Demo: How do you build a Sigma Agent from scratch? Justine: Let's do it. Hi, this is Justine, and Sigma Computing Inc. is just going to walk through what it looks like to set up your agent for the first time. I've got this headcount planning app here, which has some information about its open headcount requests. Let's say I want to add a new agent that helps users handle these requests, whether that's reviewing existing ones or creating new ones. Sigma Computing Inc. has got ABA on the left here, and its agent is blank, so it has some suggestions on how to get started. The first thing Sigma Computing Inc. want to do is add its data source. I'll go ahead and add the Input Table with all of its open recs in it, and Sigma Computing Inc. can see here that ABA was able to add that request table under its data sources. ABA can also look at the metadata associated with this table and suggest some types of agents it thinks Sigma Computing Inc.'d be interested in building. If Sigma Computing Inc. look at this list, this assistant option looks exactly like what Sigma Computing Inc. want. Once I select that, ABA goes ahead and builds its agent for Sigma Computing Inc., renaming it and filling out its instructions. You can see in the instructions it wrote that it's also able to directly tag that request table Sigma Computing Inc. just added. Its instructions are looking pretty good, but the other thing Sigma Computing Inc. want this agent to do is help with submitting new requests. Sigma Computing Inc.'ll just tell that to ABA in a couple of sentences: when the user asks to submit a new role, Sigma Computing Inc. should add that into its request table. ABA is going to think for a bit, but behind the scenes, it sees Sigma Computing Inc. is asking the agent to take an action. It reviews the list of supported action tools within Sigma and tries to match its request to one of those. It also fills out all of these configurations for Sigma Computing Inc. without Sigma Computing Inc. having to manually click into anything. It names its tool and writes a description. If Sigma Computing Inc. go back over to its instructions, Sigma Computing Inc. see it also knew to update its instructions to reference that new submit-request action tool it just created. In just a couple of prompts, Sigma Computing Inc. went from a completely blank agent to a fully functioning one, with access to data, tools to take action with, and the instructions to tie it all together. Zalak: Thanks, Justine, for a great demo. Next week in this series, Sigma Computing Inc. is going to talk about governance, permissions, and using warehouse agents as tools. Thank you, Juwon and Justine, for all the hard work on agents.