Infracost helps engineering teams understand cloud costs before they deploy infrastructure changes. We’re looking for a Senior Software Engineer to help us solve challenging problems at scale.
What we’re looking for:
* Solid experience with statically typed languages. Our core parsing functionality is in Golang.
* Knowledge of Node.js and TypeScript—our APIs and business logic rely heavily on them.
* Experience building and maintaining complex systems, solving integration, performance, and scalability challenges.
* (Preferred) Familiarity with Terraform, Kubernetes, and AWS—we use these tools, and so do our customers.
Recent challenges we’ve tackled:
* Refactoring our Terraform HCL evaluator to handle monorepos with thousands of projects.
* Mapping Terraform resources to their deployed cloud counterparts accurately.
* Scaling our APIs and onboarding to support customers with thousands of GitHub orgs and tens of thousands of repos.
Great point about the multiple API calls. One of the big problems we’ve heard about using SCPs is that they are too late. If a deployment fails because of them the developer needs to go through another pull request/code review.
Estimating costs for serverless technologies upfront is definitely challenging. We're thinking of bringing in the last 30 days of usage for these resources to give engineers some visibility.
Awesome, yeah we’ve seen people using this method and the main complaint we’ve heard is this is annoying for developers since it blocks their deployments when they run `terraform apply`, so they need to create new pull requests and wait for another code review. Combining both can definitely help with this.
Thanks, running on self managed clusters or bare metal can save costs in some circumstances, but comes with trade-offs and overheads as well. In our previous company we were managing Kubernetes on bare-metal and what we found was every team started using more and more resources until we ended up with a sprawl of over-provisioned and under-utilized services. We want to support this use case as well by allowing price books to be set up for custom environments so each developer can see a "cost" for these cases as well.
> can save costs in some circumstances [...] and what we found was every team started using more and more resources until we ended up with a sprawl of over-provisioned and under-utilized services
This can happen but already for medium deployments the costs are so much lower that you can hire a bunch of devops managing a proper centralized RBAC-based k8s cluster which isn't over-provisioned nor under-utilized. And even if, it should be still significantly cheaper than anything from Google and AWS. But again, if a company runs a strong-margin business model cloud cost optimizations are the wrong thing to think about. Whatever, your solution is definitely a big step in the right direction.
Agree, state files can contain sensitive information. We parse the Terraform client side and only send the details to the API that are needed to determine the price, i.e. the instance type, region, etc.
Yeah! When we started in the cloud cost space about 9 years ago I remember AWS had about 10,000 unique price points... now it's over 2 million! The level of services/options available now is incredible, but that just means the pricing complexity keeps increasing.
Do you know if they have public pricing available? Or are you using negotiated rates? If so, we're looking to add support for custom price books in the future.
Also, we have a huge infrastructure group that adds a markup and conditions to the published pricing. For example, my line of business pays a different rate for using a Azure VM than the price published by Azure for the VM. Being able to plugin "lob" price as opposed the prices posted by the vendor is very useful to us.
once you guys have it workable for Azure, email me at manish dot sharan at tee dee dot com. I will get you in front of the architecture group -- cost projections is a contant pain in the ass for us.
Infracost helps engineering teams understand cloud costs before they deploy infrastructure changes. We’re looking for a Senior Software Engineer to help us solve challenging problems at scale.
What we’re looking for:
* Solid experience with statically typed languages. Our core parsing functionality is in Golang.
* Knowledge of Node.js and TypeScript—our APIs and business logic rely heavily on them.
* Experience building and maintaining complex systems, solving integration, performance, and scalability challenges.
* (Preferred) Familiarity with Terraform, Kubernetes, and AWS—we use these tools, and so do our customers.
Recent challenges we’ve tackled:
* Refactoring our Terraform HCL evaluator to handle monorepos with thousands of projects.
* Mapping Terraform resources to their deployed cloud counterparts accurately.
* Scaling our APIs and onboarding to support customers with thousands of GitHub orgs and tens of thousands of repos.
More info & apply: https://www.ycombinator.com/companies/infracost/jobs/vdMNDwh...