Pave | https://www.pavefi.com | Data Scientist | Backend Engineer | Remote (US or Canada) | Full-time
I’m the Director of Engineering at Pave, a rapidly growing startup revolutionizing financial access for underserved consumers and small businesses through AI-powered Cashflow Analytics and Scores.
50+ risk teams use Pave to reduce defaults, provide the optimal loan amount/credit limit, and maximize collections success.
- We’re hiring Software Engineers in Backend, Full Stack, Data and ML to scale our data processing platform to 100M+ users: https://wellfound.com/l/2BmPpa
- We’re hiring Data Scientists to ship models that will redefine the US credit system, making it fair and inclusive: https://wellfound.com/l/2AqFf9
Shoot us an email at [email protected] and let us know you found us on HN!
Pave is backed by Better Tomorrow, Bessemer, 8VC, and other top funds and angels from Coinbase, Chime, SoFi, CashApp, and Plaid.
Pave | https://www.pavefi.com | Data Scientist | Backend Engineer | Remote (US or Canada) | Full-time
I’m the Director of Engineering at Pave, a rapidly growing startup revolutionizing financial access for underserved consumers and small businesses through AI-powered Cashflow Analytics and Scores.
50+ risk teams use Pave to reduce defaults, provide the optimal loan amount/credit limit, and maximize collections success.
Pave | https://www.pavefi.com | Data Scientist | Backend Engineer | Remote (US or Canada) | Full-time
I’m the Director of Engineering at Pave, a rapidly growing startup revolutionizing financial access for underserved consumers and small businesses through AI-powered Cashflow Analytics and Scores.
50+ risk teams use Pave to reduce defaults, provide the optimal loan amount/credit limit, and maximize collections success.
Pave | https://www.pavefi.com | Data Scientist | Backend Engineer | Remote (US or Canada) | Full-time
I’m the Director of Engineering at Pave, a rapidly growing startup revolutionizing financial access for underserved consumers and small businesses through AI-powered Cashflow Analytics and Scores.
50+ risk teams use Pave to reduce defaults, provide the optimal loan amount/credit limit, and maximize collections success.
Pave.dev | https://www.pave.dev/ | Full Stack Engineer | ML Engineer | Remote (US or Canada) | Full-time
I’m the Director of Engineering at Pave.dev, a rapidly growing startup revolutionizing financial access for 100M+ underserved consumers and small businesses through AI-powered Cashflow Analytics and Scores.
- If you’re a Full Stack Engineer passionate about building analytics products with a strong affinity for data and visualization, please see: https://wellfound.com/l/2AG7WF
- If you're an ML Engineer passionate about building end-to-end, scalable machine learning systems, please see: https://wellfound.com/l/2AtUvk
Shoot us an email at [email protected] and let us know you found us on HN!
Pave.dev is backed by Better Tomorrow, Bessemer, 8VC, and other top funds and angels from Coinbase, Chime, SoFi, CashApp, and Plaid.
Pave.dev | Data Scientist | Data Analyst | ML Engineer | Remote (US) | Full-time
I’m the Director of Engineering at Pave.dev, a rapidly growing startup revolutionizing financial access for 100M+ underserved consumers and small businesses through AI-powered Cashflow Analytics and Scores.
- If you're an ML Engineer passionate about building end-to-end, scalable machine learning systems, apply here: https://wellfound.com/l/2AtUvk
- If you’re a Data Scientist passionate about cutting-edge credit risk modeling, apply here: https://wellfound.com/l/2AqFf9
- If you’re a Data Analyst passionate about conducting analysis on massive and diverse datasets, apply here: https://wellfound.com/l/2zJxJp
Let us know you found us on HN when you apply!
Pave.dev is backed by Better Tomorrow, Bessemer, 8VC, and other top funds and angels from Coinbase, Chime, SoFi, CashApp, and Plaid.
We face a similar situation and we sometimes introduce API changes that break the monitors, which then requires to manually fix the testing script. The pain hasn’t been big enough yet to make us search for a different solution. Note that we are using Monitors mostly for end to end, user like tests, which represents a small fraction when compared to our unit test suite covering the API (where tests tend to be quite E2E as well).
We do use the one way Postman -> Github integration though. Every time a change is done, it is committed to a dedicated Github repo. We use it as a backup in case anybody messes up the scripts
My company’s product is an API and Postman has been a key tool to test it, collaborate internally on requests and share it to the external world. Our ecosystem is also very API intensive and we also use Postman to discover other companies APIs.
We use all those features:
- HTTP requests
- Mock servers (to test async requests which call back a webhook endpoint)
- Workspaces: private and public
- Monitors, alerts and integrations
I’m excited by the direction Postman has been taking over the years.
Most of commenters in the thread seem to think that Postman is still in the “lightweight cURL replacement GUI” market, like so many of the alternatives mentioned. I think this is wrong - Postman has now has moved to an upper market where requirements are more advanced and complex.
Thanks for sharing! We are a small company and right now we release (from our monorepo) on every PR merge to main. As the engineering team continues growing, we anticipate this approach will become unsustainable soon, and are looking for alternatives.
I wonder if the tag based release is a widespread industry pattern (especially for growing monorepos)? Would be curious to learn more about it
Glad to see all the innovation happening in the IaC space.
I like the multi-language premise of Pulumi but I have the feeling that over time one of the languages will gain a significant advantage over the others (better supported, more features, native...) and thus will become the primary language for Pulumi package authors and users (similar to HCL for Terraform and TypeScript for CDK).
Meaning that eventually all the "serious" Pulumi users will end up converging on one single language (similar to this comment of a CDK user migrating from Python to TypeScript). Feedback loops will only help amplify this effect (e.g. more Pulumi users on language A -> more examples online -> more package authors working in this language -> better established best practices -> more submitted issue tickets for language A -> language better supported by Pulumi -> more users...)
Curious about how Pulumi multi-language components [0] work under the hood. Isn't writing a "Pulumi schema" describing resources the same as writing declarative HCL at the end of the day?
I’m the Director of Engineering at Pave, a rapidly growing startup revolutionizing financial access for underserved consumers and small businesses through AI-powered Cashflow Analytics and Scores. 50+ risk teams use Pave to reduce defaults, provide the optimal loan amount/credit limit, and maximize collections success.
- We’re hiring Software Engineers in Backend, Full Stack, Data and ML to scale our data processing platform to 100M+ users: https://wellfound.com/l/2BmPpa
- We’re hiring Data Scientists to ship models that will redefine the US credit system, making it fair and inclusive: https://wellfound.com/l/2AqFf9
Shoot us an email at [email protected] and let us know you found us on HN!
Pave is backed by Better Tomorrow, Bessemer, 8VC, and other top funds and angels from Coinbase, Chime, SoFi, CashApp, and Plaid.