aliscott

Infracost | Senior Software Engineer | Remote (GMT+2 to GMT-6) | Full-time | €80K - €140K EUR

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...

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.

(co-founder here) Thanks! We started on this last August, so still pretty early and got a lot more we want to add.

Thanks, feel free to reach out if we can help with anything.

Thanks got it, will contact you when it's live.

Sure, it's https://twitter.com/leckie. Thanks!

Great, thanks for the details - supporting these negotiated rates and any custom price books is definitely on our roadmap.

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.

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.

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.

Azure support is in the works - it's also our most upvoted issue (https://github.com/infracost/infracost/issues/64). Are you using VMC on Azure as well?

Thanks! The site design was custom done by a friend of ours.

We are free and open source and support more AWS and Google services (https://www.infracost.io/docs/supported_resources).

We also fit in with existing toolsets - we think it’s important that users don’t need to change their workflow, so we integrate with different ways of running Terraform (Terragrunt, Terraform Cloud) different source control systems (GitHub, GitLab, etc) and CI/CD systems (Atlantis, CircleCI).

We also have additional features, like the ability to specify resource usage (for data transfer and Lambda, etc) and generate HTML and JSON reports so it can be integrated into your own systems.

You're right. It has to be a balance between the cost of the infrastructure and the developer's time. One feature we have for this is to only show comments in PRs if the cost increase is above a certain threshold.

Another idea we have is to allow developers to set alerts based on their actual project/IaC concepts instead of configuring alerts based on tags and services. Do you think this would help?

Haha thanks, great point - will fix!

Thanks, looking forward to your feedback!

Thanks! Yeah we think that making the costs visible to engineers will help remove the pain here. We're seeing some big companies like Netflix, Slack and Segment implement dev-focussed approaches to cost-management and think this will become more of a standard in the future.

Thanks! Yeah we've been in the same situation. Looking forward to your feedback.

We cover 70+ resources across AWS and GCP (the tool you mentioned only covers 12 AWS resources) and we support a number of integrations including GitHub Actions and Atlantis (https://www.infracost.io/docs/integrations/) so you can see diffs in pull requests. We're seeing a lot of users who are using multiple tools for deploying their services, for example Terraform + Kubernetes or CloudFormation + Serverless. In the future we want to work across multiple tools so we can support these use-cases as well.

Thanks! Yeah we're big proponents of IaC.

Hi HN, author here. I'm looking for feedback from devs/devops engineers on the tool in general as well as:

1. What is your biggest pain point with cloud costs?

2. Any ideas on how to handle non-baseline costs? - data transfer costs and other usage-based costs are often a significant portion of the bill and are also the hardest to predict and track down.

Edinburgh, UK. PlanForCloud (from RightScale)

* Quotes we love - "In God we trust; all others must bring data." - W. Edwards Deming - "Warning! Notice is given that any person found Pilfering, Stealing, Robbing, or Committing any code without first testing will be summarily hanged." - We have this as a big poster in our office

* What technology do we use? Ruby, Rails, Twitter Bootstrap, jQuery, PostgreSQL, GitHub, Heroku, Amazon Web Services and many open-source codebases. Our simulation software is based on Ali's PhD research.

* Who are we looking for? We are looking for smart front-end and back-end Software Engineers who can get things done, you'll be core member of the engineering team and take part in daily 15-min status meetings. Ideally you should have: - Strong computer science fundamentals gained through a degree in computer science or equivalent - Experience in developing web applications, and can show us your personal/work projects - Experience with a scripting language (Ruby, Python, PHP), model-view-controller framework experience is a plus - Be comfortable developing for and on Linux environments - Strong interpersonal and problem-solving skills, with excellent verbal and written communication skills - If you are applying for a front-end position, you should have experience of HTML, CSS, JavaScript and developing rich client-side applications. UX and UI design experience is a big plus. - If you are applying for a back-end position, experience with API design (REST) and relational databases is a plus.

* What's the next step? Sounds good? Email us at info@PlanForCloud.com and let's get talking. Feel free to include links to your LinkedIn, GitHub and any project websites.

More info here: http://www.planforcloud.com/pages/recruitment.html