Hacker Newsnew | past | comments | ask | show | jobs | submit | maddalab's commentslogin

Accrue Savings | Full Stack Product Engineer | REMOTE (Any country +/- 6 hrs from NYC) | NYC

Accrue Savings [0] helps buyer purchase desirable product without taking on debt and helps merchant expand customer base by offering responsible payment options. Product Engineer / Full Stack ready to improve an amazing product. We recently raised Series A round [1] and are iterating rapidly on our product.

Our team is dedicated to supporting new members. We have a broad mix of experience levels, and we're building an environment that celebrates knowledge sharing. Our team cares about individual well being. We value caring for team member health and family first, then bringing our full selves to work.We are building a collaborative environment, where ideas and discussions are valued. However you will have autonomy in technical decision making and in return will be expected to have an owner mindset. We value fast iteration and rapid development, if you have a bias for action when faced with conflicting choices you will succeed at Accrue.

Accrue is only getting started, we value bold direction that inspires results. Accrue is working on a product that does social good, change is not easy and we will be misunderstood for long periods of time. We are willing to persist, measure, validate and iterate on our product. Our senior members enjoy one-on-one mentoring and thorough, but kind, code reviews. We care about your career growth and strive to assign projects based on what will help each team member develop into a better-rounded engineer and enable them to take on more complex tasks in the future.

* Programming experience with Typescript, Node and React * 1+ years Front end experience, familiar with CSS, HTML * Well-rounded engineering skills; full-stack development experience - web + services * Strong analytical abilities and design skills * Degree in computer science related fields OR 2+ years equivalent experience in software development

Additional roles in other departments are open [2]

To apply or to know more you can reach me directly bhaskar at accruesavings

[0] https://www.accruesavings.com/

[1] https://techcrunch.com/2022/01/13/tiger-global-accrue-saving...

[2] https://www.accruesavings.com/careers


At Reonomy, we have been in the midst of a transition between FE technologies. Our platform was initially built with a mix of AngularJS – and over the past few months, we have made a full transition to the more developer-friendly React.

In order to make this transition feasible, we created a reactive-hooks library for rendering RxJS observables using React Hooks.


Enigma | Multiple Positions | NYC, Manhattan | 120K-160K | ONSITE, FULL-TIME | https://enigma.com

At Enigma, you’ll be involved in designing, building, and scaling the behind-the-scenes software that powers Enigma's data products. Our platform is responsible for curating a variety of data sets in a plethora of formats, analyzing and normalizing before being used to create data ontologies, knowledge graphs and models that allow users to solve real world problems: investigate corruption, find interesting relationships between seemingly unrelated data sets, make and confirm hypotheses and much more.

Blog https://medium.com/enigma



You are correct in that one use case for Genesis is hardware inventory taking, however Genesis is intended for use with Collins and shares aspects of automation with Collins and Phil (internal tool not currently Open Sourced).

On the title itself, I think it is correct, tho requires more nuanced interpretation.


Looking through the bulleted list on Razor. One use case for Genesis that drove its development is "Auto-Discovered Real-Time Inventory Data".

Genesis tho is intended for much more. It is both a linux image, a framework implementing a DSL which you can use to write tasks utilizing all of ruby.

Ex: Genesis allows you to configure hardware raid based on asset policies/attributes in Collins. Would this fall into "Policy-Based Provisioning?"

On "Open APIs and Plug-in Architecture", it is correct to state that Genesis is built around utilizing functionality from Collins, however there aren't specific limitation in Genesis which cannot be addressed to support other asset management systems, tho, this isn't a priority.

On "Dynamic Image Selection", currently we have an additional internal system that in conjunction with Collins provides support for OS versions, some aspects of this may at a later time be introduced into Genesis.


On the modules, those included in the public repo by nature of not having specific to Tumblr's DC are unsophisticated.

Along side Genesis we use additional internal tools that "provision" physical hardware using Kickstart specification.

One of the challenges with provisioning machines is bringing visibility to the process of provisioning while the machine is being provisioned. Kickstart and Anaconda installer aren't ideal from a visibility stand point.

Genesis in addition to providing a means to discover hardware at the DC allows for some provisioning automation to be moved into ruby code instead of Kickstart. Internally we are experimenting with additional solutions other than using Kickstart.


You are correct in that Tumblr did not release Invisible Touch. Genesis is the outcome of lesson learned from IT.

Genesis does not use scripts embedded into the image. In fact this was the original design of IT and much of the reason IT was not released and Genesis was created.


I am going to guess, what you really mean, is that you have not met successful people who have been mean to you or someone you associate with, or your inference is driven by a sampling bias.

Some points I agree with (a) Increasingly you win not by fighting to get control of a scarce resource, but by having new ideas and building new things. (b) that being mean makes you fail (* increases the likelihood of you failing) (c) Start ups win by transcending

Some points I disagree with (a) Mean people fail (b) Successful startup founders, programmers, professors, aren't (all) mean (c) Startups are not just one random type of work in which meanness and success are inversely correlated -- This is just a sampling bias


Apologies if this is not of interest.

If you found this interesting please checkout the jobs page [1] at Tumblr, we are constantly looking for new folks. Specifically [2] for positions on the teams that implemented everything described in the article.

[1] https://www.tumblr.com/jobs [2] http://boards.greenhouse.io/tumblr/jobs/17886


Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: