knighthacker

Nope. You can easily refresh/retake the interview.

We've designed BetterLeap to simplify and enhance the most painful and complicated part of career development — job search. So whether you're just beginning your journey, or are actively looking to transition, I hope that you find your experience with BetterLeap to be refreshing.

Today we're launching One Interview, a tool that helps you unlock new opportunities with one comprehensive interview. Essentially, you can now interview once, apply everywhere.

Getting started is easy:

- You schedule a time with us.

- You go through an adaptive and personalized interview.

- You get matched with companies that are ready to hire you.

One interview allows you to connect to many companies at once and, ultimately, to put your job search on autopilot.

We currently only support frontend, backend, and full-stack engineering roles but we're onboarding new roles regularly. So if you're looking for other roles, stay tuned for more updates soon.

We're excited to help you with your job search. In the meantime, we hope you and your loved ones are staying safe.

NOTE If you're a company that's hiring and growing your team, apply to join our one interview program.

Amazing founder and a great company. I’ve worked for and with him before in prior ventures. One of the most intelligent and sincere people I’ve ever met.

Airbnb Payments | Engineers and Data Scientists | Full-time ONSITE (SF)

At Airbnb, we want to create a world where anyone can belong anywhere. And we’re just starting.

The Airbnb Payments team empowers people and communities to participate in our global marketplace. We transmit billions of dollars, in real-time, and in 70+ currencies in over 190 countries around the world. We want payments to be simple and transparent, yet invisible and comfortable. Less transactional, more human.

We’d love to grow our team with people who are excited by operating at a global scale, creating frictionless experiences, and empowering millions of entrepreneurs.

Check out the story behind Brian Chesky’s first Airbnb payment here: https://youtu.be/Mssx8PleeYc

Come innovate on the future of payments: https://www.airbnb.com/careers/departments/engineering/payme...

My advice is to realize that you are hired as a leader in the organization. Use your leadership to change what needs to change so that the company succeeds. An important factor for the success of the company (as long as you are still hired there) is that you are doing what you love doing and what helps the company, because it'll make a big impact. If you like writing code and write 2 lines of code, it'll raise the morale of the team and get them motivated to work more.

What I am trying to say is assume your leadership and do what you want to be done. If the company likes it, then great. It is a win-win situation. If not, then next steps are clear.

Thank you very much. The need is certainly there, and we are happy to address it.

1. The way I think about it is that you have a goal/vision for why you start the project. Having a co-founder is very important and necessary to achieve this goal because your business will run into a number of roadblocks that you need a partner to help you go through it. However, whether or not your co-founder works as hard as you is really irrelevant.

You said that you are doing well financially and aren't starting these projects because of money. Then who cares if you "only" get 50% of the company? Your goal and intention is to solve a big problem. Get focused on that. The world is gonna pay you back in so many other ways than your 50%.

The other piece of advice is try to be really picky with your co-founders. Find ones that you trust and have worked with before or can get amazing references about. That way you know that he'd do his job the best way possible regardless of how many hours he puts in.

I hope this helps.

I am glad to hear that you are using Perl at Semantics3. I like what you guys are doing :)

+1

Having a DevOps first was THE reason we were able to focus on building the product and not invest time figuring out infrastructure.

I completely disagree. Traditionally, Sysadmins are what you bring in once you've grown enough that operational issues detract from development. Not only this made sysadmins feel terrible over the years having to deal with nasty production environments, but also developers were always slowed down because "Ops" were the bottleneck. And they were the bottleneck because developers didn't think like sysadmins when they started. It keeps going back and forth.

I hope the audience is smart and intuitive enough to understand that if none of the co-founders is a coder, then obviously your first hire can't be a sys-admin. With that assumption, having a sysadmin early on will only improve the productivity of the development team as is the case at Crowdtilt.

I guess the better word than Sysadmin is DevOps. Because what the author did at Crowdtilt wasn't just deploying and maintaining servers, but actually impacting and streamlining the development process.

The post was changed by a moderator. Our blog post title is what we stand by

Using more than one payment processor is definitely a smart move. Not only to avoid unpredictable consequences such as this acquisition, but also because it will give you a negotiating advantage as payment processing becomes more and more of a commodity.

Here is the open spec to the current version of the API: https://github.com/Crowdtilt/crowdtilt-api-spec

I agree with you. Knowing what's the current status of the "odds" is a good piece of information to have in order to to know how to adapt/change the inputs.

But my main point from the post is I want people to be OK and accepting of "failures". Because in reality, it isn't a failure. It is a lesson that you learned for your next attempt.

One day someone asked Thomas Edison “Aren’t you ashamed that you have failed 99 times?” Edison replied “I have not failed, rather I’ve learnt 99 ways in which an electric bulb would not lit up”

^^ This is what I mean by not fearing "failures"

I should have read your comment before I posted mine, but I agree 100%

I appreciate the author taking the time to write the article, but my opinion is that the whole purpose of a daily standup is to open a line of communication between team members. Well, if you have this line of communication open 24 hours, emails, chat (xmpp, irc ..etc), phone, and so forth, why do I need to wait till tomorrow afternoon for the scheduled daily standup to talk about a blocker in my code?

Exactly. The author already said "10-15% larger than other similar ones we've seen inthe past". Doesn't that make a record-changing by definition? :)

I think as an entrepreneur, you are gonna need to do your homework and figure out how to get the attention to your project regardless of using Kickstarter or not.

Lockitron was a perfect example that used Selfstarter to fund their project and got a lot of attention from users without the help of any organization like Kickstarter.

Happy Birthday, Perl :). At Crowdtilt, we are proud to have the majority of our stack Perl based. w00t w00t CPAN :)

The Crowdtilt API can easily power something like Selfstarter and significantly improve its features by offering support to multiple payment processors instead of just Amazon Payments. It also provides collaboration tools for the supporting community as mentioned by my co-founder http://news.ycombinator.com/item?id=4911765

Selfstarter is really cool for a one-off type of project such as Lockitron, but with the Crowdtilt API, you can also build a "kickstarter-as-a-service" type of product, which I would really love to see built one day.

(disclosure: I'm one of the Crowdtilt founders)

Agreed. More than likely, it is in violation to the Computer Fraud and Abuse Act.

Agreed. Paypal is flat out painful. But they certainly have a huge advantage when it comes to international payment processing.

wow. At least they gave you the option to opt-out haha :)

I love it. Well executed. My only comment is to make the text on the button customizable.

I think bottom line, don't work at a place that cares more about the amount of hours you work as opposed to the results that you produce. Life is too short for this shit. There are a lot of job opportunities in companies and teams that understand results and care less about even showing up to the office as long as they are highly productive.

I agree with you. Those big names, for better or worse, became the identity store on the internet. Most websites tend to support at least one of them if not all of them.

Yeah, that's what I used it for. I've used it every day for about a week and it dropped maybe once or twice. At which, I created a new connection.

I should add that I did use a screen session to share vim though.

This is super cool. I used screenleap to try it out with my remote team members and I am very impressed personally. I wanna mess around with their APIs a bit.

Having a dedicated team is definitely important. I had a similar experience to yours and I am not entirely sure why.

I think a big part of it is that once you dig into complexity points and time estimates and all that other stuff, people tend to be on the safe side and add a lot of buffer. But when the whole team is in the hacking mentality and just wants to get sh*t done, you don't need to have everything in sprints. You just need a highly motivated and a dedicated team.