daily pastebin goal
37%
SHARE
TWEET

Untitled

a guest Jan 25th, 2016 152 Never
Not a member of Pastebin yet? Sign Up, it unlocks many cool features!
  1.                                                                                                                                                                                                                                                                
  2. Delivered-To: diana.chang.twn@gmail.com
  3. Received: by 10.37.122.2 with SMTP id v2csp1729987ybc;
  4.         Mon, 25 Jan 2016 18:08:50 -0800 (PST)
  5. X-Received: by 10.107.35.146 with SMTP id j140mr19544484ioj.197.1453774130464;
  6.         Mon, 25 Jan 2016 18:08:50 -0800 (PST)
  7. Return-Path: <mlondrav@gmail.com>
  8. Received: from mail-ig0-x236.google.com (mail-ig0-x236.google.com. [2607:f8b0:4001:c05::236])
  9.         by mx.google.com with ESMTPS id p4si51324igg.41.2016.01.25.18.08.50
  10.         for <diana.chang.twn@gmail.com>
  11.         (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128);
  12.         Mon, 25 Jan 2016 18:08:50 -0800 (PST)
  13. Received-SPF: pass (google.com: domain of mlondrav@gmail.com designates 2607:f8b0:4001:c05::236 as permitted sender) client-ip=2607:f8b0:4001:c05::236;
  14. Authentication-Results: mx.google.com;
  15.        spf=pass (google.com: domain of mlondrav@gmail.com designates 2607:f8b0:4001:c05::236 as permitted sender) smtp.mailfrom=mlondrav@gmail.com;
  16.        dkim=pass header.i=@gmail.com;
  17.        dmarc=pass (p=NONE dis=NONE) header.from=gmail.com
  18. Received: by mail-ig0-x236.google.com with SMTP id ik10so44611049igb.1
  19.         for <diana.chang.twn@gmail.com>; Mon, 25 Jan 2016 18:08:50 -0800 (PST)
  20. DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
  21.         d=gmail.com; s=20120113;
  22.         h=mime-version:in-reply-to:references:date:message-id:subject:from:to
  23.          :content-type;
  24.         bh=Hdb2CXQahNBd8IPBXwTHGwTX5q1+9HSfOnQHdFVy5Qw=;
  25.         b=OlDPNXdXYqDVVlS90sm8HW2qYgkAsXP8gqdcSmTWsUxZCG+ZYvP3xngxqrwvPIZWkG
  26.          uKj/xzI5tX5dYjLphzhxMiHs7pnOzm7+5TUAJELXnDt1qbR4x5zHMG5FfrVbxBcs+el6
  27.          i/y98QnhYNAklA1lwTBUdiDx9QqvqmvVoYtfQnbpm180QB1O8Be47sOQO63yHAwnNyzW
  28.          3yHDLFCYnyK22KoXGfNarwoVkucqBYAjKkNdOStD8kP7Sw6Y/E9XFHlxcS98xjydTF9X
  29.          AyjrprbVkqq8jlrDs5z2NaaS45MiCz6TLg8HloPwb5vF2JgJmhvq7+0TkrByp0Y6q4Lb
  30.          p8BQ==
  31. X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
  32.         d=1e100.net; s=20130820;
  33.         h=x-gm-message-state:mime-version:in-reply-to:references:date
  34.          :message-id:subject:from:to:content-type;
  35.         bh=Hdb2CXQahNBd8IPBXwTHGwTX5q1+9HSfOnQHdFVy5Qw=;
  36.         b=PRGboEsWx4Y5uPKVyF8JNK7sO5H3aF7p6S91PXsifhG91C81hzZDGzabGFG0SRi1WA
  37.          Jo3RaOQRfzfgBcTep7cOTXm56jSC/eynFlgZr19VfetndhJfhaM8llEcAnyki3ahkeyC
  38.          1xRt14S0gByXu6VqRkpC+7RreP0OS5/73GuDBN4V3gjUjEzE6BHuu3aVXN+LZONcshVf
  39.          BU8/memwdhNw4auAOqiV8IW2L7ran7D99EQ4UTbtbMcBfFz2Ii8Zo2+oKtCM1Y5q+B6E
  40.          x5WOmWGCG9SOiodFE7e7GcPoyP2RXUvd0n1INBFP/EQssDTvRgYhqQJudSz9XBBkvNA4
  41.          0rLg==
  42. X-Gm-Message-State: AG10YOT/l3JnSK1Irk4QjHX/d1OQC53kHBS0mLcGlU9sb9XCcm6HoUIMSZAEZXWaJhL1A031FIfpFHnCFf/XPQ==
  43. MIME-Version: 1.0
  44. X-Received: by 10.50.29.110 with SMTP id j14mr21319441igh.87.1453774130304;
  45.  Mon, 25 Jan 2016 18:08:50 -0800 (PST)
  46. Received: by 10.79.30.68 with HTTP; Mon, 25 Jan 2016 18:08:50 -0800 (PST)
  47. In-Reply-To: <CAC_9OcsbNx4HZ1746BS-A=TaHBXJU9wqL7Ex_7N8yeD5KWLPvA@mail.gmail.com>
  48. References: <CAKGf7-ZRB9TZKYYcVa7H3TWC1OepTExdAkKJ1HFT_JhUDbu-yg@mail.gmail.com>
  49.     <CAC_9Ocv1e66JCasUSGugfvX-CBu__U1s9Zuza7ZXs+ixe6VbGQ@mail.gmail.com>
  50.     <CAKGf7-aPVwmd4u_a1-+tD77HgsbZtjjgroHtv55eZh-PR7VDeA@mail.gmail.com>
  51.     <CAC_9OcsbNx4HZ1746BS-A=TaHBXJU9wqL7Ex_7N8yeD5KWLPvA@mail.gmail.com>
  52. Date: Mon, 25 Jan 2016 21:08:50 -0500
  53. Message-ID: <CAKGf7-bp6qTku3Axm=dvta7Es-R495ihidDwHjTiJx1d=Tsikg@mail.gmail.com>
  54. Subject: Re: Google Summer Internship
  55. From: Matt Londraville <mlondrav@gmail.com>
  56. To: Diana Chang <diana.chang.twn@gmail.com>
  57. Content-Type: multipart/alternative; boundary=047d7bd6bca89ede53052a332a96
  58.  
  59. --047d7bd6bca89ede53052a332a96
  60. Content-Type: text/plain; charset=UTF-8
  61.  
  62. As stated above, we can only send emails from google.com email addresses to
  63. other google.com emails.
  64.  
  65. If you wish to continue correspondence, I must ask that you respond in a
  66. more timely manner, without bringing up side distractions. Unfortunately,
  67. we have numerous applicants to consider and will not tolerate spam-like
  68. emails.
  69.  
  70. Matt.
  71.  
  72. On Monday, January 25, 2016, Diana Chang <diana.chang.twn@gmail.com> wrote:
  73.  
  74. > Hello Matt,
  75. >
  76. > Thank you for the speedy response!
  77. >
  78. > People who have been recruited in the past have suggested that recruited
  79. > usually use their Google addresses. Would it be possible to move our
  80. > communication to your @google.com address? If you would be able to do so
  81. > it would assure me greatly!
  82. >
  83. > Thank you for your understanding!
  84. >
  85. > Best,
  86. > Diana
  87. >
  88. >
  89. > On Mon, Jan 25, 2016 at 7:45 PM, Matt Londraville <mlondrav@gmail.com
  90. > <javascript:_e(%7B%7D,'cvml','mlondrav@gmail.com');>> wrote:
  91. >
  92. >> Gladly! Here at google, we usually use our @google.com/.ca/.cn/etc
  93. >> accounts for inter-Google communication. It is used normally for easy
  94. >> transfer of files between colleagues who work at google. For outside
  95. >> communication, we tend to use our .gmail accounts.
  96. >>
  97. >> Hope this clears things up,
  98. >> Matt.
  99. >>
  100. >> On Mon, Jan 25, 2016 at 5:35 PM, Diana Chang <diana.chang.twn@gmail.com
  101. >> <javascript:_e(%7B%7D,'cvml','diana.chang.twn@gmail.com');>> wrote:
  102. >>
  103. >>> Hello Matt,
  104. >>>
  105. >>> While I write up the descriptions for all the competitions, if you don't
  106. >>> mind, could I ask why this email is sent from a @gmail.com account,
  107. >>> instead of the typical @google.com account?
  108. >>>
  109. >>> Thanks,
  110. >>> Diana
  111. >>>
  112. >>> On Mon, Jan 25, 2016 at 4:30 PM, Matt Londraville <mlondrav@gmail.com
  113. >>> <javascript:_e(%7B%7D,'cvml','mlondrav@gmail.com');>> wrote:
  114. >>>
  115. >>>> Hello from Google, Diana!
  116. >>>>
  117. >>>> We saw your profile on LinkedIn and we have decided to consider you for
  118. >>>> the position of Software Engineer at Google. Before we proceed, we would
  119. >>>> like to learn more about you and your achievements. For each of the
  120. >>>> competitions you have listed in your profile (including non-CS ones) please
  121. >>>> describe what you did to prepare, as well as how you were able to achieve
  122. >>>> your goal (i.e. what skills you possess that made it possible for you to do
  123. >>>> well).
  124. >>>>
  125. >>>> Please reply to this email, sending the details we have requested. If
  126. >>>> you do not wish to work at Google, you may ignore this email.
  127. >>>>
  128. >>>> Looking forward to hearing from you,
  129. >>>>
  130. >>>> Matt Londraville
  131. >>>> Technical Recruiter
  132. >>>> Google (Mountain View, California)
  133. >>>>
  134. >>>
  135. >>>
  136. >>
  137. >
  138. >
  139.  
  140. --047d7bd6bca89ede53052a332a96
  141. Content-Type: text/html; charset=UTF-8
  142. Content-Transfer-Encoding: quoted-printable
  143.  
  144. As=C2=A0stated above, we can only send emails from <a href=3D"http://google=
  145. .com">google.com</a> email addresses to other <a href=3D"http://google.com"=
  146. >google.com</a> emails.=C2=A0<div><br></div>If you wish to continue corresp=
  147. ondence, I must ask that you respond in a more timely manner, without bring=
  148. ing up side distractions. Unfortunately, we have numerous applicants to con=
  149. sider and will not tolerate spam-like emails.<div><br></div>Matt.<br><div><=
  150. div><br>On Monday, January 25, 2016, Diana Chang &lt;<a href=3D"mailto:dian=
  151. a.chang.twn@gmail.com">diana.chang.twn@gmail.com</a>&gt; wrote:<br><blockqu=
  152. ote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc s=
  153. olid;padding-left:1ex"><div dir=3D"ltr"><div class=3D"gmail_default" style=
  154. =3D"font-family:&#39;trebuchet ms&#39;,sans-serif">Hello Matt,</div><div cl=
  155. ass=3D"gmail_default" style=3D"font-family:&#39;trebuchet ms&#39;,sans-seri=
  156. f"><br></div><div class=3D"gmail_default" style=3D"font-family:&#39;trebuch=
  157. et ms&#39;,sans-serif">Thank you for the speedy response!</div><div class=
  158. =3D"gmail_default" style=3D"font-family:&#39;trebuchet ms&#39;,sans-serif">=
  159. <br></div><div class=3D"gmail_default" style=3D"font-family:&#39;trebuchet =
  160. ms&#39;,sans-serif">People who have been recruited in the past have suggest=
  161. ed that recruited usually use their Google addresses. Would it be possible =
  162. to move our communication to your @<a href=3D"http://google.com" target=3D"=
  163. _blank">google.com</a> address? If you would be able to do so it would assu=
  164. re me greatly!</div><div class=3D"gmail_default" style=3D"font-family:&#39;=
  165. trebuchet ms&#39;,sans-serif"><br></div><div class=3D"gmail_default" style=
  166. =3D"font-family:&#39;trebuchet ms&#39;,sans-serif">Thank you for your under=
  167. standing!</div><div class=3D"gmail_default" style=3D"font-family:&#39;trebu=
  168. chet ms&#39;,sans-serif"><br></div><div class=3D"gmail_default" style=3D"fo=
  169. nt-family:&#39;trebuchet ms&#39;,sans-serif">Best,</div><div class=3D"gmail=
  170. _default" style=3D"font-family:&#39;trebuchet ms&#39;,sans-serif">Diana</di=
  171. v><div class=3D"gmail_default" style=3D"font-family:&#39;trebuchet ms&#39;,=
  172. sans-serif"><br></div><div class=3D"gmail_extra"><br><div class=3D"gmail_qu=
  173. ote">On Mon, Jan 25, 2016 at 7:45 PM, Matt Londraville <span dir=3D"ltr">&l=
  174. t;<a href=3D"javascript:_e(%7B%7D,&#39;cvml&#39;,&#39;mlondrav@gmail.com&#3=
  175. 9;);" target=3D"_blank">mlondrav@gmail.com</a>&gt;</span> wrote:<br><blockq=
  176. uote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc =
  177. solid;padding-left:1ex"><div dir=3D"ltr">Gladly! Here at google, we usually=
  178.  use our @<a href=3D"http://google.com/.ca/.cn/etc" target=3D"_blank">googl=
  179. e.com/.ca/.cn/etc</a> accounts for inter-Google communication. It is used n=
  180. ormally for easy transfer of files between colleagues who work at google. F=
  181. or outside communication, we tend to use our .gmail accounts.<div><br></div=
  182. ><div>Hope this clears things up,</div><div>Matt.</div></div><div><div><div=
  183. class=3D"gmail_extra"><br><div class=3D"gmail_quote">On Mon, Jan 25, 2016 =
  184. at 5:35 PM, Diana Chang <span dir=3D"ltr">&lt;<a href=3D"javascript:_e(%7B%=
  185. 7D,&#39;cvml&#39;,&#39;diana.chang.twn@gmail.com&#39;);" target=3D"_blank">=
  186. diana.chang.twn@gmail.com</a>&gt;</span> wrote:<br><blockquote class=3D"gma=
  187. il_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-lef=
  188. t:1ex"><div dir=3D"ltr"><div style=3D"font-family:trebuchet ms,sans-serif">=
  189. Hello Matt,</div><div style=3D"font-family:trebuchet ms,sans-serif"><br></d=
  190. iv><div style=3D"font-family:trebuchet ms,sans-serif">While I write up the =
  191. descriptions for all the competitions, if you don&#39;t mind, could I ask w=
  192. hy this email is sent from a @<a href=3D"http://gmail.com" target=3D"_blank=
  193. ">gmail.com</a> account, instead of the typical @<a href=3D"http://google.c=
  194. om" target=3D"_blank">google.com</a> account?</div><div style=3D"font-famil=
  195. y:trebuchet ms,sans-serif"><br></div><div style=3D"font-family:trebuchet ms=
  196. ,sans-serif">Thanks,</div><div style=3D"font-family:trebuchet ms,sans-serif=
  197. ">Diana</div><div><div><div class=3D"gmail_extra"><br><div class=3D"gmail_q=
  198. uote">On Mon, Jan 25, 2016 at 4:30 PM, Matt Londraville <span dir=3D"ltr">&=
  199. lt;<a href=3D"javascript:_e(%7B%7D,&#39;cvml&#39;,&#39;mlondrav@gmail.com&#=
  200. 39;);" target=3D"_blank">mlondrav@gmail.com</a>&gt;</span> wrote:<br><block=
  201. quote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc=
  202. solid;padding-left:1ex"><div dir=3D"ltr">Hello from Google, Diana!<div><br=
  203. ></div><div>We saw your profile on LinkedIn and we have decided to consider=
  204.  you for the position of Software Engineer at Google. Before we proceed, we=
  205.  would like to learn more about you and your achievements. For each of the =
  206. competitions you have listed in your profile (including non-CS ones) please=
  207.  describe what you did to prepare, as well as how you were able to achieve =
  208. your goal (i.e. what skills you possess that made it possible for you to do=
  209.  well).=C2=A0<br></div><div><br></div><div>Please reply to this email, send=
  210. ing the details we have requested. If you do not wish to work at Google, yo=
  211. u may ignore this email.</div><div><br></div><div>Looking forward to hearin=
  212. g from you,</div><div><br></div><div>Matt Londraville</div><div>Technical R=
  213. ecruiter</div><div>Google (Mountain View, California)</div></div>
  214. </blockquote></div><br>
  215. </div></div></div></div>
  216. </blockquote></div><br></div>
  217. </div></div></blockquote></div><br><div><br></div>
  218. </div></div>
  219. </blockquote></div></div>
  220.  
  221. --047d7bd6bca89ede53052a332a96--
RAW Paste Data
We use cookies for various purposes including analytics. By continuing to use Pastebin, you agree to our use of cookies as described in the Cookies Policy. OK, I Understand
 
Top